Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Fri, 19 Mar 1999 11:34:48 -0500
Message-Id: <199903191634.LAA01549@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: m DOT foster AT mcc DOT ac DOT uk
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <Pine.LNX.4.04.9903191602140.1827-100000@felicity.mvc.mcc.ac.uk>
	(message from Martyn Foster on Fri, 19 Mar 1999 16:25:40 +0000 (GMT))
Subject: Re: licensing NOT clear for me
References:  <Pine DOT LNX DOT 4 DOT 04 DOT 9903191602140 DOT 1827-100000 AT felicity DOT mvc DOT mcc DOT ac DOT uk>


> For clarification on this, one can sell non-GPL source code that
> cannot be used without cygwin under any license?  But I cannot sell
> a linked version without it being under GPL. I can make a wrapper
> DLL around my calls to cygwin functions and distribute it for free 
> (GPL) and sell my own code that links to the DLL but is a seperate
> package and contains no code from either cygwin.dll or the wrapper 
> - however at the current time there is no way to generate a dll 
> that does such a thing. But I can alter cygwin myself to
> generate such a beast and that is also OK.

If you generated such a wrapper and distributed it under the GPL,
you're right back where you belong - even if it's your source
originally.  Once the user has that GPL'd dll, you have certain
obligations to them that include giving them the source to the rest of
the program.

However, if you're building such a chain of dlls just to subvert the
GPL, it won't work.  Cygwin is still part of your program, and you
still have to provide the sources to everything.

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