Re: dyld issues with library not in standard location
Re: dyld issues with library not in standard location
- Subject: Re: dyld issues with library not in standard location
- From: Stefan Werner <email@hidden>
- Date: Thu, 20 Oct 2005 12:32:05 -0700
On Oct 20, 2005, at 12:14 PM, email@hidden wrote:
Date: Thu, 20 Oct 2005 18:07:13 +0200
From: Andrea -XFox- Govoni <email@hidden>
Subject: Re: dyld issues with library not in standard location
Graham Hemingway ha scritto:
Peter,
Is using install_name_tool something I have to run after I have
compiled everything or is it something I can set up in XCode?
You can build your library with the -install_name option.
To do this add to your OTHER_CFLAGS library's build setting the option
-install_name @executable_path/../relative/path/to/lib.dylib
This should build the library with the given install name and when you
build the app it should record the given path and use it to find the
library at launch time.
Whom do I need to bribe to make this whole thing go away in 10.5? I
tried, but I couldn't think of any reason how the presence of the
install name path is anything but a big bother. Is there any
advantage of having this "feature" in dylibs? It would be so much
easier if dylibs were position independent just like shared libraries
in any other binary format.
Stefan
_______________________________________________
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