Re: Question about dynamic and static libraries
Re: Question about dynamic and static libraries
- Subject: Re: Question about dynamic and static libraries
- From: Daniel Jalkut <email@hidden>
- Date: Wed, 28 Dec 2005 10:55:13 -0500
| If you are confirming with otool -L that only Cocoa and libSystem are pulled in by the application, then I'm truly perplexed by how you would be getting anything from /usr/local/lib. What is the "etc" in your otool output? :)
One thing you might try doing is examine file system usage while your program launches. E.g.:
sudo fs_usage -w | grep MyProgram
You might jog some clue by looking for the file system call that opens the /usr/local/lib library. Is it possible that your application (or the library .a code itself) is manually looking for and opening a library in /usr/local/lib?
Daniel On Dec 28, 2005, at 10:34 AM, Brant Sears wrote: 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