This is the mail archive of the
mailing list for the Cygwin project.
Re: Running a cygwin application on Windows
- From: Fernando Gont <fgont at si6networks dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 16 Aug 2014 08:57:54 -0400
- Subject: Re: Running a cygwin application on Windows
- Authentication-results: sourceware.org; auth=none
- References: <53ED67D3 dot 2020405 at si6networks dot com> <877g28enhq dot fsf at Rainer dot invalid> <20140816104904 dot GV28562 at calimero dot vinschen dot de>
On 08/16/2014 06:49 AM, Corinna Vinschen wrote:
> On Aug 16 12:29, Achim Gratz wrote:
>> Fernando Gont writes:
>>> My idea was to use cygwin, since I'm not much of a Windows programmer.
>>> Is there any way to produce and ship an exe with the relevant libraries?
>> If I understand correctly what you're trying to do, you need to obtain a
>> commercial license from RedHat for doing so. Otherwise, if you ship
>> binaries linked against cygwin1.dll you need to also include all sources
>> (for Cygwin and your own application) with each such shipment.
> You only need the buyout license if you want to provide binaries only.
> But this is a GPL'ed project, so I assume there's no desire to create
> binary-only packages.
To be as honest and straightforward as possible :-): My goal is to
provide as may options as possible. I will be producing a Cygwin package
since that seems to be a fair way to contribute to this project. But I
also want to address the user that just knows how to run commands from
the windows command line and wants to quickly download & install my
toolkit to try it. -- hence my goal of also producing some sort of
"binary" distribution (even if the binary package also includes the source).
I'm in the process of reading the online information to produce the
Cygwin package. Are there any pointers to get the other stuff done?
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple