Date: Wed, 8 Feb 2012 00:58:48 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Documentation on -mno-cygwin Accuracy
Message-ID: <20120208055848.GC7184@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAGJFqDVGy9pMbpYizQhX3qZCRzALS9r9N=RbL6FQbHwrAdkR7A AT mail DOT gmail DOT com> <1328569526 DOT 8848 DOT 3 DOT camel AT YAAKOV04> <jgrik0$6k3$1 AT dough DOT gmane DOT org> <4F315473 DOT 8070106 AT gmail DOT com> <jgrtto$7g5$1 AT dough DOT gmane DOT org> <4F3180B1 DOT 7090007 AT aol DOT com> <jgs0ff$t8j$1 AT dough DOT gmane DOT org> <20120207211251 DOT GF32219 AT calimero DOT vinschen DOT de> <jgs7nl$l1k$1 AT dough DOT gmane DOT org> <4F31B073 DOT 9010501 AT arlut DOT utexas DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F31B073.9010501@arlut.utexas.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Tue, Feb 07, 2012 at 05:14:59PM -0600, Jesse Ziser wrote:
>On 2/7/2012 4:14 PM, carolus wrote:
>> On 2/7/2012 3:12 PM, Corinna Vinschen wrote:
>>>
>>> There's the usual misconception about the GPL. If you create an
>>> application which is linked against the Cygwin DLL (or any other GPLed
>>> library), but you only use the application in-house, there's no reason
>>> at all to distribute the source code to your collegues. If one of them
>>> really wants it, he can always ask you, right? Only if you provide the
>>> binaries to customers or to the world in some way, you are supposed to
>>> provide the sources codes as well in a GPL-compatible way.
>>>
>>
>> In a publication I have offered to furnish on request the source code
>> and windows executable for a program that I personally run under cygwin.
>> Don't I have to use mingw for the publicly distributed version, or else
>> bundle the executable with cygwin source code? As I understand, simply
>> providing a link to the cygwin web site does not satisfy the license.
>
>Well, if you don't want them to have to install Cygwin, then that's a 
>bigger issue than just licensing.  Think of Cygwin like an OS.  If you 
>want to create something that can run under Windows, not Cygwin, then 
>you have to build it for Windows, not Cygwin.  I don't know that it is 
>even possible to simply "bundle" Cygwin with your application.  Cygwin 
>isn't just some little collection of libraries or something.  It's a 
>whole system that must be correctly installed on someone's computer.

Actually, you can easily bundle a program with the Cygwin DLL and have
it work fine.  You don't need to install the whole system.  That doesn't
mean it's a good idea, however, since your soon-to-be-out-of-date DLL
could cause confusion with an existing Cygwin application.

>If you really want Mingw (a free compiler and development environment 
>for Windows), maybe what you should do is just download and install 
>Mingw, and use that, instead of doing it through the Cygwin compiler 
>using a barely-supported option.  (Then you should get help with any 
>problems you have over at Mingw's website instead of here.)

The MinGW cross-compiles are not "barely supported".  They are included
in the distribution precisely so that people can build pure-windows
programs under Cygwin.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple