On Fri, Sep 15, 2000 at 08:22:21PM +0100, Gary V. Vaughan wrote:
>>      But my original patch (hm, below) would allow to save sensibility
>> for something more useful. Don't provide excess configurability when
>> it's hardly needed.
>
>But it is.  Chris Faylor has specifically denounced the cygfoo.dll
>convention, but Chuck Wilson (and presumably yourself) would like an
>option to use it for your own ports.  It is also more general, rather
>than adding a bunch more special cases to libtool, porters can add
>'-soname cygfoo.dll' to foo_LDFLAGS if they wish.

That, I like.  I have no problem with people who contribute DLLs for
cygwin establishing a "cyg*.dll" standard but I'd rather not make it
the default for libtool.

>> (Automake won't generate that option specially for
>> gnu-win32, will it?
>
>Nope.  Nor should it.

I hate to mention this but since cygwin used to be called "gnu-win32"
aren't we going to end up confusing things by adding this to scripts?

Also, I believe that the FSF actually asked us to call it something
besides gnu-win32 specifically because RMS didn't like the name 'win32'
(which is another separate problem).

Before adding a name like this to libtool, or autoconf, or whatever,
it might be a good idea to get his ruling on this.

cgf

Reply via email to