Re: Now, help plz w/ mult. defs. of sym. errs.
Re: Now, help plz w/ mult. defs. of sym. errs.
- Subject: Re: Now, help plz w/ mult. defs. of sym. errs.
- From: Greg Guerin <email@hidden>
- Date: Thu, 4 Oct 2007 17:44:48 -0700
David Goldsmith wrote:
>I just tried to post the build transcript, but it's awaiting moderator
>approval 'cause it's too big (one of the main reasons I didn't post it
>before).
If it doesn't get approved, you could:
1) Sign up for a free trial .Mac account.
2) Put the transcript on your site as a web-page.
3) Post the URL to the list.
Alternatively, you could use the iDisk feature of your trial .Mac account to:
1) Put the file in the Public folder of your idisk.
2) Enable read-only password-free access to the Public folder.
3) Post the URL of your Public folder.
#2 is accomplished in the .Mac pane of System Preferences, under the iDisk tab.
A trial account gets 100 MB of storage, of which 70 MB can be assigned to
iDisk.
>But before you dive in: might it have something to do with both the
>upgraded target and the jam-based target both still "residing" in the
>project?
Only if you're building both of them.
When the error occurs, what is your current build target?
If it's the converted target, then under normal circumstances the jam-based
target won't be built. "Normal circumstances" being that you only did a
conversion to native, and did not add the old target as a dependency of the
new target.
Also, if you have an umbrella target, or some other target with
dependencies on the Jam-based target, then it's conceivable they're both
being built. Since you haven't said anything about how many targets, what
templates they were made from, etc., we can only guess.
>I thought to delete the old target from the project, but when I went to
>look for the upgraded target's search path settings (for example), there
>were none to be found, but they're still set in the old target, so I
>assumed the upgraded target was using the jam targets settings and was
>thus reluctant to delete it.
Targets don't normally refer to the settings of another target. IIRC, it's
not even possible for them to do so.
Establishing a dependency between targets doesn't make targets use each
other's settings. It just establishes a dependency in the build order:
target X must be built before target Y that depends on it.
About halfway through your posted transcript you have several of these:
- - -
/Users/dg/Documents/NOAA/Projects/CATS/code/wxCats/trunk/Source/build/wxCATS.bui
ld/Development/xcodeCATS.build:
No such file or directory
- - -
These are telling you that directory doesn't exist. Since the directory is
used as a source pathname, i.e. the origin of a file being copied to
..../xcodeCATS.app/Contents/Resources, I suspect something is wrong with the
Copy Resources phase or phases of the target.
Normally, a clean build should create this directory, I would think, so try
a Clean or Clean All, then a Build. If the error still occurs, i.e. the
build still fails, look for "No such file or directory" in the transcript.
It may not be directly above where the error is reported. I found the "No
such file or directory" errors in the middle of the CpResource steps, not
at the end.
It's possible these CpResource steps are leftovers from the older target
and should be eliminated or modified in the new target. You may have to
edit any Copy Resources build phases, which is where the failing CpResource
commands in the transcript appear to be coming from.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden