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: Mon, 7 Jun 2004 17:13:25 +0100 (GMT Daylight Time) From: Alastair Growcott Subject: Re[2]: Visual Studio linking To: cygwin AT cygwin DOT com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE References: <001801c4487e$dca77e20$78d96f83 AT robinson DOT cam DOT ac DOT uk> <20040607145637 DOT GB15068 AT coe DOT casa DOT cgf DOT cx> In-Reply-To: <20040607145637.GB15068@coe.casa.cgf.cx> Organization: BakBone Software X-IsSubscribed: yes > A .def file is generated for cygwin when the DLL is built, actually. I'm not building the Cygwin dll, so I need this step. > 5a) Modify the license of your program to the GNU General Public > License, since your binary has now become GPLed, meaning that you must > now offer the source code to your sources under the terms of the GPL. My program is non-distributable. I am using it to run unit tests internally. I thought that, under the terms of the GPL, if my binary links dynamically to the Cygwin DLL, I do NOT have to offer my source code up, I only need to ensure that people can use my software against future (or past) versions of Cygwin by rebuilding the DLL themselves. This includes either distributing the Cygwin DLL source code or ditributing a link to somewhere they can obtain it. Or is that the lesser GPL? Surely the source code will not be GPL'ed if I do not make it or the binary publically available! Alastair. -- 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/