Subject: Re: [IMP-dev] Request to simplify IMP config
From: Ben Webb <>
Date: Wed, 26 Nov 2008 13:38:30 -0800
Reply-to: List for IMP development <>
Daniel Russel wrote:
> I agree that it is a bit controversial, but everything I have read
> prefers it to using LD_LIBRARY_PATH (since that, among other ill
> effects, changes the behavior of 3rd party libraries).
I will look at the patch. But rpath will probably have to be optional -
defaulting to true on OS X. The Modeller binary packages on OS X and
Linux are built with rpath for precisely the reason you mention - to
avoid the bundled copies of Fortran runtime libraries, HDF5, libpython
etc. from conflicting with system copies. But the Unix and Windows
builds do not use rpath.
> I don't know
> how dynamic link paths are handled on Windows and no one seems to use
> it around here. There used to be some equivalent of rpath, I seem to
> recall, but that was years ago that I last did windows programming.
> How do things currently work on windows anyway (since we can't count
> on csh being around)?
Windows looks for dynamic libraries in the same directory as the parent
binary (executable, or Python extension) and then falls back to looking
in PATH. DLL and their paths can also be registered in some random place
in the registry, IIRC.
"It is a capital mistake to theorize before one has data."
- Sir Arthur Conan Doyle