X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4F3299A6.7090105@arlut.utexas.edu>
Date: Wed, 08 Feb 2012 09:49:58 -0600
From: Jesse Ziser <ziser AT arlut DOT utexas DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Documentation on -mno-cygwin Accuracy
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> <20120208055848 DOT GC7184 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20120208055848.GC7184@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 2/7/2012 11:58 PM, Christopher Faylor wrote:
> 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.

Oh?  Then I got the wrong impression from the documentation and the 
mailing list when I was trying to work all that out a few years ago.  I 
can't find it now, but I could swear there was something about it being 
"deprecated" or "partially supported" or something.

-- 
+---------------------------+
| Jesse Ziser, Code Warrior |
| Applied Research Labs: UT |
+---------------------------+

--
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