dlopen doesn't use LD_LIBRARY_PATH ( was dlopen and cygcheck inconsistency)
Christopher Faylor
cgf-no-personal-reply-please@cygwin.com
Mon May 30 18:17:00 GMT 2005
On Sun, May 29, 2005 at 07:09:50PM -0700, Sunil wrote:
>So, this issue is still un-resolved. Contrary to what
>cgf say, dlopen doesn't care about LD_LIBRARY_PATH
>while opening dependent DLLs of its argument. It opens
>the DLL if the depedent DLLs are found in the $PATH.
dlopen is a cygwin invention. It honors LD_LIBRARY_PATH. Windows does
not know about LD_LIBRARY_PATH. If you have a DLL which is statically
linked to other DLLs, the other DLLs will not be found on
LD_LIBRARY_PATH. Standard Windows search rules for finding DLLs will be
used instead.
*Only* the dlopen call honors LD_LIBRARY_PATH.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list