Linking in CW shared lib vs. Xcode framework
Linking in CW shared lib vs. Xcode framework
- Subject: Linking in CW shared lib vs. Xcode framework
- From: Jo Meder <email@hidden>
- Date: Tue, 1 Aug 2006 15:49:39 +1200
Hi,
I'm having a slightly mysterious problem. I'm updating an app built
with CW to build with Xcode 2.3. The part I'm working on right now is
a CFM shared library, and I've made it a framework in Xcode. I have
it building fine in Xcode but not linking. The problem is just a
couple of functions. I've been looking at the CW project and I cannot
see the source file these functions are defined in the project. It
just isn't there. The header is included. However, that source file
is in the app which hosts the shared library.
It doesn't make much sense to me, but I was wondering if somehow in
the CFM app the symbols in the shared library are not being resolved
until it's loaded into the app ? Something like that anyway.
Xcode seems to expect the source file to be part of the project
before it will link. To me that seems fair enough, although it's
unfortunate because that particular file pulls in a whole bunch of
stuff I don't want to have to deal with in the framework. I'm just
kind of surprised that the CW project worked fine, and has for years
and years. I'd be interested in understanding what the difference is
here, if anyone has any insight.
Is there a way to get similar behaviour with Xcode ? I can
restructure the source a bit to solve the problem, but I'd prefer not
to.
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