Building Static Libraries Linked To Frameworks
Building Static Libraries Linked To Frameworks
- Subject: Building Static Libraries Linked To Frameworks
- From: OL&L Dev 2 <email@hidden>
- Date: Tue, 11 May 2004 19:41:16 -0700
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?
I need to make a "wrapper" dylib project that links in my static lib
so that my app can then call the dylib. I need to do this because the
static lib has Mac-specific data types, but my app (in pure Java)
can't include any references to the Mac types in its code. Hence my
dylib acts as a platform-independent wrapper layer insulating the
Java app from the Mac data types.
Is it possible to do this or is there some express prohibition
against linking static and dylibs together? And if it's not possible
to do this, then how does one link multiple dylibs together for use
by an application?
Thanks,
Mike
_______________________________________________
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.