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 From: "Pete Nordquist" To: Subject: License question Date: Sun, 9 Mar 2003 18:47:44 -0800 Message-ID: <000f01c2e6af$70c5ed40$8201a8c0@prndelllaptop> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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. 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/