Re: Linking in CW shared lib vs. Xcode framework
Re: Linking in CW shared lib vs. Xcode framework
- Subject: Re: Linking in CW shared lib vs. Xcode framework
- From: Jo Meder <email@hidden>
- Date: Mon, 7 Aug 2006 19:29:55 +1200
Hi Syd,
On 2/08/2006, at 2:12 PM, Syd Polk wrote:
Of course. I could have been clearer I guess, but I assumed most
people would assume that the Xcode side of things was Mach-O. Too
many assumptions, I apologise for that. I mentioned CFM because
the app built with Codewarrior is CFM and not Mach-O ( which it
could have been ), and I'm interested in the difference between
what is happening with the CW/CFM shared lib and the Xcode/Mach-O
framework. The reason the app is still CW/CFM after all this time
is that we still support OS 9 for it. I'm now looking into
building a Universal version for those with Intel machines,
because our next product, which is already Universal, has been
delayed.
What symbols exactly are coming up missing? Without the build log,
this is incredibly difficult to diagnose.
All the symbols were ones from my own code, nothing from frameworks
or system libraries etc. It turned out I could just remove the files
calling the problematic symbols without problems. Although they were
part of the CW project there wasn't any problem linking it, so I
guess it's just something different in the way the CW linker works. I
still don't understand what exactly was going on, but the Xcode
project is linking now and right now that's most important thing.
Thanks anyway.
Regards,
Jo
--
Jo Meder
Planetside Software
email@hidden
Terragen for Macintosh
Photorealistic landscapes on your Mac
<http://www.planetside.co.uk/terragen/mac/>
_______________________________________________
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