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: David Goldsmith <email@hidden>
- Date: Fri, 05 Oct 2007 20:32:56 -0700
OK, I've posted the first build transcript at:
http://home.comcast.net/~dgoldsmith/buildxscript.txt
Thanks!
DG
Greg Guerin wrote:
David Goldsmith wrote:
In light of that, and the quasi-independence of the two targets (caveats
discussed below), would you recommend: A) continuing to try to work with
the project which contains only the updated target; or B) reverting back to
the old jam-based project, re-doing the update, and then proceed, being
very careful to only build the updated target? Thanks again!
I have no specific recommendation other than posting the build transcript.
Without seeing exactly what the errors are, I can't begin to guess which
approach would work.
In my experience, a converted-to-native target is already completely
independent of the jam-based target it originated from. I've done the
conversion at least a dozen different times and never had anything weird
happen with multiply defined symbols or "quasi" independence (better stated
as "quasi-dependence", IMO).
If the original jam target built correctly, and the converted one didn't,
then simple logical debugging procedures suggest going back to the last
thing that worked and proceeding from there.
If the original jam target didn't build correctly, then converting it
before it builds could introduce additional reasons for instability. It's
hard to say because if the original doesn't work, I don't know in what way
it doesn't work. Your original post here:
<http://lists.apple.com/archives/xcode-users/2007/Oct/msg00028.html>
says that Jam is failing, but I don't recall ever seeing any of the build
transcript from that particular failure. Based on that, I'd say that going
back to the jam target will just bring you back to the state of that
original post, and my response to that would be the same as I wrote before:
<http://lists.apple.com/archives/xcode-users/2007/Oct/msg00032.html>
If you can't post the complete build transcript, at least post the portion
of it where the failure is occurring. I've also suggested a way to upload
a large file to idisk.mac.com, so if the transcript is too big to post, you
can still put it in a public place, perhaps even zipped.
Essentially you're asking how to debug a process of which we have very few
details. The only debuggable output I've seen was the CpResource steps,
where a missing directory seemed to be the cause. There are no details
about the multiply defined symbols failure (apparently after the
convert-to-native), nor any details about the original jam-based failure.
That just isn't enough to go on.
-- 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
_______________________________________________
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