Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <39B4209A.6B5BBEC1@home.com> Date: Mon, 04 Sep 2000 18:22:18 -0400 From: "David A. Cobb" Organization: @home user X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en,ru,pdf MIME-Version: 1.0 To: cygwin@sources.redhat.com CC: gvv@techie.com Subject: Current Directory? [Branch from Re: DLL naming conventions] 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> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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. -- David A. Cobb, Software Engineer, Public Access Advocate "Don't buy or use crappy software" "By the grace of God I am a Christian man, by my actions a great sinner" -- The Way of a Pilgrim [R. M. French, tr.] -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com