Re: library path in framework product
Re: library path in framework product
- Subject: Re: library path in framework product
- From: Eric Albert <email@hidden>
- Date: Sun, 11 Dec 2005 13:37:47 -0800
SDKs shouldn't change the search results for anything in /usr/local.
SDKs are intended to give you a replacement for Apple's libraries, and
Apple never ships anything in /usr/local.
That said, it sounds like the problem is that the install name of the
second library is wrong. William, rather than opening the binary in
vi, you can find the install name of a library by using 'otool -D
/path/to/library'. You can change the install name of a library either
while building it or by using install_name_tool after it's built.
Hope this helps,
Eric
On Dec 11, 2005, at 1:09 PM, Daniel Jalkut wrote:
William - is it possible that your project is linking against a
particular SDK on your machine, not the root volume itself.
This seems likely, and that the library you're trying to link against
is not in that particular SDK. This is exactly why it's a good idea
to use an SDK! If you need to support the system you're targeting,
then you might need to come up with an alternative to dynamically
linking against that library.
Daniel
On Dec 11, 2005, at 4:02 PM, William Turner wrote:
I have a couple of libraries that are included by a Framework I'm
building. Both of these libraries are in /usr/local/lib. The path
type for both is Absolute. When I link again the framework, I get a
compile warning that it is unable to find one of the libraries. When
I open the framework executable file with vi, I see that one library
is referenced by its complete path, the other - the one I am warned
about - has no path, just its binary.
Help?
_______________________________________________
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