Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <414156C2.4CC8BFDB@dessent.net> Date: Fri, 10 Sep 2004 00:24:50 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Is it free to use References: <414007D6 DOT 7DB36622 AT dessent DOT net> <20040909135502 DOT GC27325 AT trixie DOT casa DOT cgf DOT cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Andrew DeFaria wrote: > Christopher Faylor wrote: > > > This means that if you are developing software for eventual release, > > you must also make the source code available when you make binaries > > available. > > If I develop an app and do not wish to have a requirement to install > Cygwin I would use MingW, right? In that case is my app still under GPL > just because I used Cygwin's gcc to compile and link the resulting > executable that will have no more dependencies on Cygwin? (Just curious). The part that causes it to become GPL'd is the linking to cygwin1.dll, not the fact that Cygwin's gcc is used. If you use Cygwin's gcc in mingw mode then your program does not need cygwin1.dll and the program may be released under any license you choose, assuming there are no other GPL libraries to which you link. cgf meant that by default (with no command line options to the contrary) Cygwin's gcc creates a binary linked against the Cygwin dll. Brian -- 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/