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 14:50:11 -0400
no T means that your symbol does exist in your binary
that symbol is resolved and could be used
On Mar 16, 2008, at 1:50 PM, Alfred Van Hoek wrote:
On Mar 16, 2008, at 12:37 PM, Dmitry Markman wrote:
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
Thank you.
First, all_load does not make a difference.
Second, the existence of symbols in <path_to_my_library> provides a
capital T to _MyFirstFunction, and based on the man page for nm it
is a text section symbol.
Third, it probably means that this lib is not correctly build, which
means that the problem is not a true linking problem, but a problem
I hope I can handle in "libMycarboncocoa.a" and the associated Xcode
project.
Appreciate the help from all of you, and if there are additional
suggestions, please fire it up.
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