Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Wed, 3 May 2000 08:05:18 -0400
Message-Id: <200005031205.IAA08198@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: Dautrevaux AT microprocess DOT com
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <17B78BDF120BD411B70100500422FC6309E02A@IIS000> (message from
	Bernard Dautrevaux on Wed, 3 May 2000 10:56:54 +0200)
Subject: Re: Things you can do with Cygwin
References:  <17B78BDF120BD411B70100500422FC6309E02A AT IIS000>


> Yes, but I think there is different works as soon as these can be
> used independently; obviously a proprietary work that can be used on
> CYGWIN, Linux, HPux, Solaris, etc is NOT a derived work of CYGWIN
> but a separate work (especially if it was FIRST available on other
> OSes, then ported on CYGWIN).

Once it's compiled with Cygwin, it's a derived work, because the
binaries are not independent.  If you could run the same *binary* on
Linux, Solaris, HPUX, and Cygwin, that would be different.  Or, if you
had a binary that would run just fine without cygwin1.dll but happened
to use it if it was there, that might be independent.  But a binary
that relies on cygwin1 is not independent.

Plus, don't forget that part of cygwin is statically linked into your
program - even if you don't use cygwin1.dll (somehow), you still use
libcygwin.a, and that alone makes it GPL'd.

> In fact CYGWIN on WIN32 may be seen as yet another POSIX-compatible
> OS and it seems difficult to argue that some work that can be used
> on it is not a different work.

No, because *windows* isn't a POSIX-compatible OS, so cygwin is
clearly an added feature on such an OS, especially since you have to
obtain it from a third party, make special provisions for it (relative
to win32 programs), and link it into your program.

The POSIX subsystem doesn't count, because cygwin runs in the win32
subsystem, so cygwin programs have more functionality than posix
subsystem programs.

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