From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Faylor To: cygwin@sources.redhat.com Subject: Re: Current Directory? [Branch from Re: DLL naming conventions] Date: Mon, 04 Sep 2000 19:53:00 -0000 Message-id: <20000904225307.B1081@cygnus.com> References: <200009011148.OAA23769@urkki.tellabs.fi> <39AFB333.69CE5F95@ece.gatech.edu> <20000902140958.F7695@demon.co.uk> <39B14893.A86AF3F9@ece.gatech.edu> <20000902231925.Q7695@demon.co.uk> <20000902221915.B13854@cygnus.com> <39B4209A.6B5BBEC1@home.com> X-SW-Source: 2000-09/msg00118.html On Mon, Sep 04, 2000 at 06:22:18PM -0400, David A. Cobb wrote: >Chris Faylor wrote: > >> On Sat, Sep 02, 2000 at 11:19:25PM +0100, Gary V. Vaughan wrote: >> >> Since windows-dll >> >> loading is based on the executable path, and not 'LD_LIBRARY_PATH' or >> >> similar, you've got a problem. >> > >> >Most definitely. >> >> It is *not* strictly based on the executable path. It first searches >> the current directory, then searches the directory containing the executable. > >With the possibility of several processes active and several partitions, etc., >just like the big boys; what does "current directory" mean? I only see it when >defining a PIF for a DOS program. I actually got the order wrong. It searches the directory containing the executable and then the current directory. As far as what the "current directory" means, it means the directory you're cd'ed to. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com