Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 30 May 2005 14:14:47 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: dlopen doesn't use LD_LIBRARY_PATH ( was dlopen and cygcheck inconsistency)
Message-ID:	<20050530181447.GB13315@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<20050530020950 DOT 65014 DOT qmail AT web31711 DOT mail DOT mud DOT yahoo DOT com>
Mime-Version:	1.0
In-Reply-To:	<20050530020950.65014.qmail@web31711.mail.mud.yahoo.com>
User-Agent:	Mutt/1.5.8i

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/

- Raw text -