Re: libc UNIX2003 mystery
Re: libc UNIX2003 mystery
- Subject: Re: libc UNIX2003 mystery
- From: Andy O'Meara <email@hidden>
- Date: Tue, 7 Dec 2010 12:05:16 -0600
Hi Scott, thanks for writing.
The name of the static lib is 'sspython' (binary is libsspython.a), and the method I've used to add it to our project is dragging it into our main xcode project's "External Frameworks and Libraries" group. Since removing that project item causes the hundreds of symbols in the static lib to not be found, it seems like it's pulling in the right lib. I also tried renaming the lib to something even more unique and there's no change in behavior.
On Dec 7, 2010, at 11:35 AM, Scott Ribe wrote:
> On Dec 7, 2010, at 10:28 AM, Andy O'Meara wrote:
>>
>> So, how do I get the static lib project to stop emitting the $UNIX2003 symbols and emit the proper ones? In case it's not clear above, in each of the tests, both projects were cleaned and set to matching SDK options (most posts out there on this issue seem to result from people using a different SDK in their static lib projects).
>
> Yes, usually. After you built the static lib, are you 100% sure you actually got it linked into your executable? The linker has a very strong preference for dynamic libs, if you add a static lib to your project, and the linker finds the corresponding dynamic lib in its search path, it will ignore the static lib.
>
> --
> Scott Ribe
> email@hidden
> http://www.elevated-dev.com/
> (303) 722-0567 voice
>
>
>
>
_______________________________________________
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