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 Date: Wed, 16 Jul 2003 16:39:13 +0100 From: Elfyn McBratney X-X-Sender: elfyn AT ellixia Reply-To: cygwin AT cygwin DOT com To: Cary Lewis cc: cygwin AT cygwin DOT com Subject: Re: License question about Cygwin In-Reply-To: <3E2D8043936AD611AF7D00508B5E9F4B48B482@server3.mobilecom.com> Message-ID: References: <3E2D8043936AD611AF7D00508B5E9F4B48B482 AT server3 DOT mobilecom DOT com> Mail-Followup-To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 16 Jul 2003, Cary Lewis wrote: > As the Cygwin.dll is licensed under GPL, any "Program" that links to it must > be released under GPL as well. Under section 10 of the GPL, if the "program" is OSD compatible then the "program" is not auto-GPL'd. > My question is, what if the "Program" also links to proprietary .dlls that > are authored by someone else. That source can not be published (I don't even > have access to it). Furthermore these .dlls are not freely available. Are these DLL's Cygwin DLL's ? i.e. not native Windows DLL's. > Does that mean that even if I publish all of my source code, I would still > be violating the GPL because I couldn't publish the source code to the > proprietary libraries. Yes. Elfyn -- Elfyn McBratney, EMCB | http://www.nongnu.org/wwwauth/ http://www.emcb.co.uk | http://www.emcb.co.uk/webauth/ elfyn AT emcb DOT co DOT uk | wwwauth-users AT nongnu DOT org -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/