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/
