Re: Building Static Libraries Linked To Frameworks
Re: Building Static Libraries Linked To Frameworks
- Subject: Re: Building Static Libraries Linked To Frameworks
- From: Fritz Anderson <email@hidden>
- Date: Wed, 12 May 2004 10:07:14 -0500
The dylib project has to include the framework in the link. As this is
a development-system detail, this should not break the platform
independence of the application itself.
-- F
On 11 May 2004, at 9:41 PM, OL&L Dev 2 wrote:
When I build a static library using Xcode 1.2 (Cocoa, Carbon), and
then I try to link against that static lib from a separate dylib
project, I get dozens of errors saying "illegal reference to symbol:
_AESend defined in indirectly referenced dynamic library......." with
the offending system framework. Then a list of other system API calls
that have illegal references.
So my question is: how does one build a static lib that needs to call
Cocoa or Carbon frameworks and then link that static lib to another
dylib project?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.