X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 25 Nov 2008 12:47:46 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: LD_LIBRARY_PATH Message-ID: <20081125114746.GV30831@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <00ec01c94ee7$9166dfe0$4001a8c0 AT mycomputer> <20081125104337 DOT GU30831 AT calimero DOT vinschen DOT de> <011701c94eee$c8e4f180$4001a8c0 AT mycomputer> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <011701c94eee$c8e4f180$4001a8c0@mycomputer> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Nov 25 11:13, John Emmas wrote: > ----- 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. I don't think so. The installation of shared libs into /usr/bin is a long standing and expected behaviour on Cygwin. By installing into /usr/lib and requiring to set $PATH you're adding confusion, IMHO. In the long run you will be better off by investing some time into tweaking your development environment, rather than installing in a non-standard location. But that's just me, of course... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/