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 12:37:07 -0400
BTW
in order to check existence of the symbol in your binary (bundle,
framework, executable e.t.c.)
you can use nm tool (sorry you must do that from terminal :-) )
nm <path_to_your_liubrary> | grep <name_of_the_symbol_you_like_to_check>
please see man page of the nm to understand nm's output
On Mar 16, 2008, at 12:29 PM, Alfred Van Hoek wrote:
On Mar 16, 2008, at 11:50 AM, Dmitry Markman wrote:
I hope solution for the
discussion for CFBundleGetFunctionPointerForName will help you
namely use -all_load flag, when you link your final binary
Forgive my ignorance, but where would you set this flag in the Xcode
project?
see also man page for the linker ld
OK, I am a lay when it comes to man page and everything that comes
with Terminal,
Alfred
Dmitry Markman
_______________________________________________
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