Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Wed, 17 Mar 1999 13:36:18 -0500
Message-Id: <199903171836.NAA23015@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: hcobb AT telegenisys DOT com
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <199903171830.NAA29075@delorie.com> (hcobb@telegenisys.com)
Subject: Re: Using Cygnus tools to deliver closed software.
References:  <199903171830 DOT NAA29075 AT delorie DOT com>


> If you really want to use the Cygnus compiler and Gnu POSIX
> libraries to produce closed software, why not simply use the Cygnus
> compiler on Linux?

Because that won't result in programs that run under Windows, which is
often (sadly) a key marketing point.

It's not the *use* of gnu tools that causes the problems.  It's the
fact that a program built *for* cygwin *includes* GPL'd cygwin sources
(see other debate for more info :).  Programs built for Linux don't
include any gnu code (libc is a shared library), and they made it very
clear that they don't intend that the LGPL on libc.a infect binaries
using it as a shared library.  If you link a Linux program statically,
then you'll have the same problem with Linux as you do with Cygwin.

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