Message-ID: <011701c94eee$c8e4f180$4001a8c0@mycomputer>
From: "John Emmas" <johne53@tiscali.co.uk>
To: <cygwin@cygwin.com>
References: <00ec01c94ee7$9166dfe0$4001a8c0@mycomputer> <20081125104337.GU30831@calimero.vinschen.de>
Subject: Re: LD_LIBRARY_PATH
Date: Tue, 25 Nov 2008 11:13:02 -0000
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

----- Original Message ----- 
From: "Corinna Vinschen"
Sent: 25 November 2008 10:43
Subject: Re: LD_LIBRARY_PATH
>
> $PATH is what you want and if you examine /bin resp. /usr/bin, you see
> that Cygwin puts all shared libs there for the above reason.  /lib resp.
> /usr/lib only contain the static libs and the shared link stubs
> necessary for the linker at build time.
>
> LD_LIBRARY_PATH only has a meaning in Cygwin's dlopen() implementation,
> when loading shared libs at runtime.
>
Thanks Corinna.  AFAIK my development IDE won't allow me to direct the link
stubs to a different folder from the shared objects (unless I copy them, of
course).  So I've just added cygwin's /usr/lib to my path.  This makes it
 work the same way as my 2 x Linux distros which will probably avoid
confusion in the long run.

John

--
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/