RE: [ANNOUNCEMENT]: Important change to symbolic link functionality

["Robert Collins" <robert dot collins at itdomain dot com dot au>]

There's nothing wrong with it. In fact I expect that Chris et al. will
change the filename in accordance with the dll naming conventions
painfully hammered out here about 6 months ago.

The issue being that windows doesn't support symlinked .dll's, so the
filename cannot change like it does on unix.

The results were (from memory):
Change the library major version number on ABI changes.
Change the library minor version number on internal changes/header files
changes with the same ABI.
The library name is library<major version>.

So when the cygwin ABI changes in a non backwards compatible way, I
expect that the library will become version 2.x.x, and the filename
cygwin2.dll


Rob




> -----Original Message-----
> From: Warren Young [mailto:warren@etr-usa.com]
> Sent: Thursday, February 22, 2001 5:19 PM
> To: cygwin@cygwin.com
> Subject: Re: [ANNOUNCEMENT]: Important change to symbolic link
> functionality
> 
> 
> Christopher Faylor wrote:
> > 
> > There is no "binary compatibility change".  Cygwin still 
> recognizes the
> > old symlinks.  It just doesn't create them.
> 
> I know, but this message reminded me of the issue.  It seems 
> to me that
> the DLL filename should change every time the ABI changes.  
> What's wrong
> with that proposal?
> --                                                   _
> = 'Net Address: http://www.cyberport.com/~tangent | / \  ASCII Ribbon
> = ICBM Address: 36.82740N, 108.02040W, alt. 1714m | \ /  Campaign
> =                                                 |  X   Against
> = Chance favors the prepared mind.                | / \  HTML Mail
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
> 
> 

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple