Static linking issue
Static linking issue
- Subject: Static linking issue
- From: Gideon King <email@hidden>
- Date: Sat, 11 Mar 2006 01:21:30 +1000
I am building an application that needs to run under 10.3 and 10.4
PPC and 10.4 Intel. I have got just about everything working except
that I need to get rid of references to libbz.dylib.
I have created a static library and have added that to my project,
but it still seems to be linking to the dynamic library during a
deployment build.
Then I found that the OmniFoundation framework I link against links
with the dynamic libbz, so I put the libbz2.a file in that project
and recompiled it. If I run otool -L on the OmniFoundation
executable, it doesn't include libbz.
So I rebuilt my project with the static version of the library
included, but if I otool -L it, it still shows /usr/lib/libbz2.dylib
So I thought that there may be a priority in the linker that would
choose to link against a dynamic library rather than a static one, so
I renamed /usr/lib/libbz*
Then when that made no difference I thought it must be in the
universal SDK, so I renamed all of them too.
Now when I run otool on my executable it still says that it is linked
against /usr/lib/llibbz2.1.0.dylib
So what am I missing? How do I force my entire project and all its
frameworks and libraries to only use the static version of libbz2 so
that I can run it on 10.3.9?
Thanks
Gideon King
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