RE: Question about dynamic and static libraries
RE: Question about dynamic and static libraries
- Subject: RE: Question about dynamic and static libraries
- From: "Brant Sears" <email@hidden>
- Date: Wed, 28 Dec 2005 09:49:26 -0500
- Thread-topic: Question about dynamic and static libraries
Title: RE: Question about dynamic and static libraries
>If you're successfully linking against the .a and not pulling in the
>.dylib, your application can't be pulling in the .dylib on a system on
>which it exists unless you're dynamically loading the .dylib at runtime
>via dlopen or a similar API.
That's what I *would* think. However, when I remove all of the libraries from /usr/local/lib and then add the .a to the project and build, I get an application that is supposedly not linking to the .dylib. When I use otool -L to examine my app, I no longer see the .dylib listed in the libraries and frameworks it loads. Yet, when I take the app binary to another machine if the .dylib is present in /usr/local/lib, it loads that version of the library.
This is the part that has me totally confused.
_______________________________________________
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