On Wed, Oct 29, 2008 at 10:49 PM, Bryan Blackburn <[EMAIL PROTECTED]> wrote: > On Wed, Oct 29, 2008 at 10:30:17PM +0100, C. Florian Ebeling said: >> I recently came across the statement that one needs to set the >> DYLD_LIBRARY_PATH >> variable if you want to run an executable linked against a dynamic >> library which is not to be found >> in any of the standard locations (~/lib:/usr/lib:/usr/local/lib). That >> is the case for all mp installed >> libraries, I'd say. My immediate reaction was that this is not true, >> and that everything is fine >> without the variable as long as `otool -L' points to the right >> location. So the "install name" counts. > > You might be commingling two different, but similar, ideas: an item > can be linked directly against a dylib (eg, what you see with 'otool -L') > and you can load a dylib (or bundle) at runtime using dlopen().
True, actually. I mixed those two up, even though I kind of know the difference. I think the dyld(1) documentation could be made a bit clearer on this matter, because it didn't reduce my confusion. I do realize that this is not the right place to complain about apple documentation, though. :) So, for usual operation of something linked against mp libs, no DYLD_* environment variables have to be set. This might be different if you deal with plugin-like objects opened by dlopen, which is probably an exceptional case, but in general the rule holds. Right? Florian -- Florian Ebeling Twitter: febeling [EMAIL PROTECTED] _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
