Imported from the Apple Support Forums via the Wayback Machine 🔗
Dr. T wrote:
What replaces the functionality of LD LIBRARYPATH in Leopard?
A modern operating system.
Do I have to type -L <path> everywhere now?
No. You shouldn't have to type -L anywhere. If you need a library that isn't included by the system, you should package that library up with your application.
0
Doug Reeder·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Dr. T
The Apple faithful aren't fond of it but DYLD LIBRARYPATH provides the functionality that you get from LD LIBRARYPATH in other unix/linux os's.
Doug Reeder
0
Dr. T·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks for your reply. To clarify, I am not talking about LD LIBRARYPATH as it behaves on Linux, but how it behaves in pre-10.5 Mac OS X.
E.g. on Mac OS 10.4, the following might all have the effect of ld linking to /some/dir/libxx.a: