> There is nothing in the Xcode 2.2 manual about exit codes, and "man
> jam" is missing. A search of developer.apple.com was fruitless.
> "jamtool" and "jam tool" both give zero hits.
Jam is an open source attempt at replacing make(1), hosted at
perforce.com - see e.g. http://maillist.perforce.com/pipermail/jamming
hauke

Signature
Eine Linux User Group, um soziale Blockaden gegenüber Frauen
abzubauen? Da wäre ja ein Schwulengesangsverein noch produktiver.
{David Kastrup @ d.t.r}
C.R. Osterwald - 21 Dec 2005 22:07 GMT
>> There is nothing in the Xcode 2.2 manual about exit codes, and "man
>> jam" is missing. A search of developer.apple.com was fruitless.
[quoted text clipped - 4 lines]
>
> hauke
The main link seems to be here: <http://www.perforce.com/jam/jam.html>
Unfortunately there doesn't seem to be any documentation about the exit
codes.
> I'm trying to link a very simple code interface node for LabVIEW 7.1,
> and Xcode 2.2 generates a rather cryptic error that I have no clue
[quoted text clipped - 33 lines]
> Does anyone know what this means? Is this a fancy way of obscuring a
> path or permissions error?
You didn't post enough of the detailed build log. When you're using the
older Jam-based targets (as opposed to native targets, which you really
should upgrade to), Xcode uses jam to drive the whole build process.
The error message tells you that something in your build failed, so
you'll want to find the error in the detailed build log and find the
line which corresponds to that, not the line which invokes jam.
-Eric

Signature
Eric Albert ejalbert@cs.stanford.edu
http://outofcheese.org/
C.R. Osterwald - 22 Dec 2005 20:08 GMT
>> I'm trying to link a very simple code interface node for LabVIEW 7.1,
>> and Xcode 2.2 generates a rather cryptic error that I have no clue
[quoted text clipped - 40 lines]
>you'll want to find the error in the detailed build log and find the
>line which corresponds to that, not the line which invokes jam.
As you might have assumed, Xcode is still quite alien to me. Too many
years of using CodeWarrior, I guess. I did try upgrading the project,
which also failed to build, but differently. It generated a
"FTextToPath error: 7" while trying to process one of the LabVIEW
libraries: "lvsbutilx: error building resource file: 7". I still
haven't figured out where they list these errors.