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 10:34:01 -0500
- Thread-topic: Question about dynamic and static libraries
Title: RE: Question about dynamic and static libraries
>How are you confirming that it pulls in the /usr/local/lib version of
>the library? Can you confirm that none of the libraries it *does*
>link to are linking directly to the /usr/local/lib library?
That's an excellent question and could be where the mistake lies.
I'm confirming that it pulls in the version from /usr/local/lib by having specific versions of those libraries that produce unique output that are built only on a separate machine.
The only way I know to determine what libraries an app is using is by use of otool -L on the app. In my case, when I add the .a version of the library to my project and remove all versions of the library from /usr/local/lib, the resulting app reports linking only to the Cocoa framework and libSystem.B, etc. whereas if I leave the copies of the library in /usr/local/lib, otool reports that I'm linking to those libraries.
So, perhaps otool -L is not the correct way to determine this?
_______________________________________________
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