Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <3EB69792.3090005@cotagesoft.com>
Date: Mon, 05 May 2003 09:55:46 -0700
From: Shankar Unni <shankar@cotagesoft.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Commercial corporate usage of cygwin.
References: <20030505095823.22760.qmail@flock1.newmail.ru> <20030505162430.GD1433@redhat.com>
In-Reply-To: <20030505162430.GD1433@redhat.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:

> If you are going to be using cygwin to produce commercial applications
> you must include the source code to your application and possibly to the
> cygwin DLL when you distribute the product.  

I2ANAL, but..

Let me expand on that above statement: if you ship software that is 
compiled and linked against cygwin1.dll (or any other component of 
Cygwin) such that you need those DLLs at runtime to load and run your 
product, _then_ the above applies.

If you're simply using Cygwin tools in your build and/or engineering 
process, but compiling with native compilers (Visual C++, or the Mingw 
GCC that only links against standard Windows libraries, or, like we are, 
pure Java products compiled with the Sun JDK, etc.; i.e. not shipping 
any part of Cygwin with your product), then you are not affected by this 
particular clause.

(Or, of course, if your products are never distributed outside your 
company, that's fine, too, but *any* distribution, free or commercial, 
of code linked against Cygwin libraries, will require you to follow the 
GPL instructions).
--
Shankar.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/