|Jun 30, 2010, 10:07 AM||#1|
Is it OK to use DYLD_LIBRARY_PATH on Mac OS X? And, what’s the dynamic library search
I read some articles discouraging of the use of DYLD_LIBRARY_PATH, as the the path of dynamic library should be fixed using -install_name, @rpath, and @loader_path.
In terms of making a program that runs both on Linux and Mac OS X, DYLD_LIBRARY_PATH of Mac OS X does exactly what LD_LIBRARY_PATH of Linux. And, we can share (almost) the same make file that doesn't have the -install_name and @rpath.
* Is this OK to use DYLD_LIBRARY_PATH on Mac OS X?
* What's the dynamic library search algorithm with Mac OS X when the binary can't find the dynamic library? current directory -> DYLD_LIBRARY_PATH directories ... ?
|Jul 3, 2010, 08:51 AM||#2|
Try this on your Mac: echo $DYLD_LIBRARY_PATH
It's an undefined variable.
So far as I'm aware, OS X does NOT have a dynamic library search algorithm. 'otool -L' on a binary shows you where it expects its libraries to be. If they aren't there, the binary fails to load.
[blackie:/Applications/VLC.app/Contents/MacOS] (0) whschultz% otool -L VLC VLC: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 476.19.0) @loader_path/lib/libvlc.5.dylib (compatibility version 6.0.0, current version 6.0.0) @loader_path/lib/libvlccore.4.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.4) @loader_path/lib/libintl.8.dylib (compatibility version 9.0.0, current version 9.2.0) /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
You can still use the same Makefile on Mac and Linux. You'll just need to make sure that the install name of your libraries is correct and that it matches where the libraries are installed.
This is where the .app bundles come in handy. You can put all of your libraries inside the .app bundle, and they'll never move--relative to the launching binary. Additionally, you'll never have to worry about the wrong version of a library being installed.
Last edited by Detrius; Jul 3, 2010 at 08:57 AM.
|Jul 3, 2010, 01:09 PM||#3|
If you need help changing the makefile, post it here and ask for help.
Reliance on DYLD_LIBRARY_PATH is a security risk. It can be used to inject libraries into the runtime of other code, without altering the targeted code.
Consequently, there are situations when DYLD_LIBRARY_PATH (and other DYLD* values) are not used by the dyloader, in order to maintain security. If you require DYLD_LIBRARY_PATH, and the context of the execution forbids it, then your code won't run.
Knowing nothing else about your program, it's impossible to guess if these scenarios are OK or not.
Last edited by chown33; Jul 3, 2010 at 01:38 PM. Reason: expand
|Thread Tools||Search this Thread|
|thread||Thread Starter||Forum||Replies||Last Post|
|'PayPal Here' for iOS Updated with Revamped User Interface, Dynamic Search||MacRumors||iOS Blog Discussion||11||Apr 10, 2014 10:35 PM|
|Library search paths||prello23||iPhone/iPad Programming||2||Apr 8, 2014 12:17 AM|
|No way to search iTunes library?||elfy||Apple TV and Home Theater||6||Sep 8, 2013 11:31 AM|
|Leopard not able to search user library||sfphoto||OS X||2||Nov 28, 2012 06:39 PM|
|how do you sort/search through your itunes library?||aliensarecool||iPhone||0||Oct 19, 2012 05:55 PM|
All times are GMT -5. The time now is 12:43 AM.