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
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Thu, 31 Aug 2000 17:13:39 -0400
To: cygwin AT sources DOT redhat DOT com
Subject: Re: DLL naming conventions
Message-ID: <20000831171339.A15393@cygnus.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: cygwin AT sources DOT redhat DOT com
References: <20000831194146 DOT 867 DOT qmail AT web120 DOT yahoomail DOT com> <20000831154242 DOT B7880 AT cygnus DOT com> <39AEC3AD DOT 42FE1CB9 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <39AEC3AD.42FE1CB9@ece.gatech.edu>; from cwilson@ece.gatech.edu on Thu, Aug 31, 2000 at 04:44:29PM -0400

On Thu, Aug 31, 2000 at 04:44:29PM -0400, Charles Wilson wrote:
>1) experimental proof that clever dll placement in the filesystem can
>get us out of 'DLL hell'

Haven't you seen people complaining about the "Shared region version
mismatch" error with cygwin?  I really should have remembered this.

>2) should new libraries version their dll's when API/ABI changes?

Well, cygwin will when/if the API changes.  That's why it's called
cygwin1.dll.

I went through my own private DLL hell to make this change.  Cygnus
used to rename the DLL with every release so that executables built
with last years DLL wouldn't work with this year's DLL even if there
were only minimal changes in this year's DLL.

We used to name the net release DLLs based on the beta version, e.g.,
cygwinb18.dll and cygwinb19.dll.  We stopped doing that with B20 since,
for the most part, there have been no API changes since B18.

In your case, though, I don't see that there will be a problem until
there actually is an API change.  When that happens you can add a
'1' to whatever DLL changed.

cgf

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