This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
License question
- From: "Pete Nordquist" <pnordquist at charter dot net>
- To: <cygwin at cygwin dot com>
- Date: Sun, 9 Mar 2003 18:47:44 -0800
- Subject: License question
I read the following on
http://sources.redhat.com/cygwin/faq/faq_1.html#SEC4
In particular, if you intend to port a proprietary (non-GPL'd)
application using Cygwin, you will need the proprietary-use license for
the Cygwin library. This is available for purchase; please visit
http://www.redhat.com/software/tools/cygwin/ for more information. All
other questions should be sent to the project mailing list
cygwin at cygwin dot com dot
I don't understand how Redhat can release libcygwin.a under a
proprietary license for customers to use to produce proprietary code.
Isn't customer code produced using the proprietary version of
libcygwin.a also statically linked with gcclib, which is licensed under
the GPL?
The description given in http://www.redhat.com/software/tools/cygwin/
sounds to me like it is possible to link GPL'ed libraries with
proprietary customer code. My understanding is that such linking is not
legally possible.
Could someone explain this seeming contradiction to me?
Thank you,
Pete Nordquist
Assistant Professor of Computer Science
Southern Oregon University
nordquip at sou dot edu
541/552-6148
--
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/