Re: Compilation leads to Undefined symbols of a nested static lib
Re: Compilation leads to Undefined symbols of a nested static lib
- Subject: Re: Compilation leads to Undefined symbols of a nested static lib
- From: Dmitry Markman <email@hidden>
- Date: Sun, 16 Mar 2008 11:50:28 -0400
I hope solution for the
discussion for CFBundleGetFunctionPointerForName will help you
namely use -all_load flag, when you link your final binary
see also man page for the linker ld
dm
On Mar 16, 2008, at 11:38 AM, Alfred Van Hoek wrote:
Have created a static lib (Carbon) that wraps calls into Cocoa,
"libMycarboncocoa.a". This static lib is used by a carbon static
lib, which is called "libMylib.a". When "MyFramework.bundle" is
compiled, Xcode complains that there are undefined symbols when
libMylib.a calls into libMycarboncocoa.a. Previously, when we did
not use libMycarboncocoa.a, MyFramework.bundle compiled fine with
libMylib.a.
Any suggestions?
Alfred
_______________________________________________
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