Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Chris Faylor Date: Thu, 31 Aug 2000 14:12:01 -0400 To: Chris Faylor Subject: Re: DLL naming conventions Message-ID: <20000831141201.A7062@cygnus.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: Chris Faylor References: <20000831133952 DOT 21477 DOT qmail AT web123 DOT yahoomail DOT com> <39AE7E06 DOT CEFB0BC8 AT ece DOT gatech DOT edu> <20000831115556 DOT F5412 AT cygnus DOT com> <128287744755 DOT 20000831204417 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <128287744755.20000831204417@logos-m.ru>; from deo@logos-m.ru on Thu, Aug 31, 2000 at 08:44:17PM +0400 On Thu, Aug 31, 2000 at 08:44:17PM +0400, Egor Duda wrote: >Hi! > >Thursday, 31 August, 2000 Chris Faylor cgf AT cygnus DOT com wrote: > >>>(This argument is based on the supposition that dll's with the same >>>name will always conflict. If I'm wrong about that supposition, >>>please correct me...as I stated above, I'm a bit confused as to when >>>dll's will conflict and when they will not) > >CF> Can someone write a simple test to verify Windows behavior? It's pointless >CF> to argue about what Windows does with DLLs if we don't know for sure. > >with ease. all you need is two different builds of cygwin1.dll, sh.exe >and strace.exe i've used my yesterday's build and current one. >1. create 2 directories -- say c:\test\1 and c:\test\2 >2. copy first cygwin1.dll to c:\test\1 and other build to c:\test\2 >3. copy sh.exe and strace.exe into both c:\test\1 and c:\test\2 >4. start cmd.exe, cd c:\test\1, strace -o sh.log sh >5. start cmd.exe, cd c:\test\2, strace -o sh.log sh >6. look at the string containing "DLL build" in c:\test\1\sh.log and >c:\test\2\sh.log > >voila Duh. Of course I know that it is possible to load conflicting versions of the Cygwin DLL. I guess that means that Windows doesn't just blindly use DLLs of the same name (unless specially instructed to do so). That means that the (so far hypothetical) DLL problems should be solvable by keeping the DLLs in the same directory as the executables. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com