Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 31 Aug 2000 20:44:17 +0400
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <deo AT logos-m DOT ru>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <128287744755.20000831204417@logos-m.ru>
To: Chris Faylor <cygwin AT sources DOT redhat DOT com>
CC: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
Subject: Re: DLL naming conventions
In-reply-To: <20000831115556.F5412@cygnus.com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com