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
Reply-To:	<nhv AT cape DOT com>
From:	"Norman Vine" <nhv AT cape DOT com>
To:	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	RE: Things you can do with Cygwin
Date:	Tue, 2 May 2000 15:21:04 -0400
Message-ID:	<000801bfb46c$bdd231c0$2137ba8c@nhv>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook 8.5, Build 4.71.2232.26
In-Reply-To:	<200005021819.OAA21633@envy.delorie.com>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2014.211
Importance:	Normal

>> Actually, I think it's even a bit less restrictive than that.  I
>> believe that you can sell an application that depends on CygWin,
>> even as a closed-source proprietary program.
>
>No, this is just plain wrong.  When you build an application with
>cygwin, part of cygwin itself is statically linked into the
>application.  The application is GPL at that point.
>

I find this discussion very interesting and I hope others do not 
find it a waste of bandwidth.

I would venture that legally you could link against a propriatary
DLL that you distributed separately ( and perhaps sold )
and still use Cygwin for the rest of the application.

Norman Vine

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

- Raw text -