Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 11 Nov 2002 11:40:29 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Strip Cygwin Message-ID: <20021111114029.I10395@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i On Mon, Nov 11, 2002 at 11:21:54AM +0100, ralf.truijen@philips.com wrote: > Hi, > > Is it allowed that we strip the Cygwin installation and distribute only the files (make environment related) that are needed to compile our sources? Yes and no. Yes, you can take just the binary stuff you need. No, because you must provide the *sources* of all GPL'd applications you distribute to your target audience due to licensing restrictions. This includes especially the sources of the Cygwin DLL itself. There is an option to buy a special Cygwin license which gets you around this slightly. That's typically only useful if you're planning to distribute a proprietary application but that's not what you want, apparently. Other than that, you can only circumvent this licensing problem by not distributing the build environment at all. Just point your customers to the cygwin web page in that case. In theory that should suffice most needs. HTH, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/