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: Fri, 21 Oct 2005 02:39:45 +0200
- Organization: http://freemail.web.de/
"Peter O'Gorman" <email@hidden> schrieb am 21.10.05 01:43:28:
> Stefan Werner wrote:
> | 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.
>
> Name those binary formats!
>
> Windows searches a set of default paths. Other unixes search their default
> paths (including ld.so.conf defaults) and the encoded rpath (or equivalent).
OK, maybe I did not make myself very clear: What I meant was that a .so, .dll or .shlb on non-MachO doesn't have an install_name_path - I can move a .dll from one path in the search path list to another without having to change anything about the library or the programs using them. When, on OS X, I link a program against /sw/lib/libtiff.dylib it won't run with libtiff.dylib installed in /usr/lib - on other platforms, it would.
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