This is the mail archive of the email@example.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Using Cygnus tools to deliver closed software.
- To: firstname.lastname@example.org
- Subject: Re: Using Cygnus tools to deliver closed software.
- From: DJ Delorie <email@example.com>
- Date: Wed, 17 Mar 1999 13:36:18 -0500
- CC: firstname.lastname@example.org
- Delivered-To: email@example.com
- Delivered-To: mailing list firstname.lastname@example.org
- In-reply-to: <199903171830.NAA29075@delorie.com> (email@example.com)
- Mailing-List: contact firstname.lastname@example.org; run by ezmlm
- References: <199903171830.NAA29075@delorie.com>
- Sender: email@example.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 firstname.lastname@example.org