Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3B681387.8090807@ece.gatech.edu> Date: Wed, 01 Aug 2001 10:34:47 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713 X-Accept-Language: en-us MIME-Version: 1.0 To: Corinna Vinschen CC: "Clark, Matthew C (FL51)" Subject: Re: Licensing terms References: <20010801151653 DOT B18101 AT cygbert DOT vinschen DOT de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Corinna Vinschen wrote: > On Wed, Aug 01, 2001 at 08:52:31AM -0400, Clark, Matthew C (FL51) wrote: > > Basically you'll have to release the sources of applications linked > against Cygwin. Except when > > - you never release the application since you're using it only > internally in your office or so. That's the trivial case. > > - you purchase a special Cygwin license from Red Hat. For a > one time fee per project you may distribute also proprietary > software linked against Cygwin. > Visit http://www.redhat.com/products/support/cygwin/ for more > information. The key here is that this is not a gcc thing -- it's a cygwin thing. "sources of applications *linked against Cygwin*" This does not mean "merely built using cygwin tools" -- however, the cygwin tools (gcc) default to linking against Cygwin. To build apps that are not thusly linked, you have to use 'gcc -mno-cygwin" -- but then you lose the POSIX emulation that Cygwin provides, and you can really only build code that has been ported to "pure" native Windows. For the "why" behind all this, see the links provided in other messages in this thread. --Chuck -- 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/