X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Ak
	wF35I1A2r15Lk1xGkq2lcOMX1fYMzGpug7xU+v2JbDjvm0fMwQwVApSKY0IhhgtP
	hw6mb6n4SsCH+4OYjWPtGi6Wv/BSAsc9RfW1JRNW1xMk9h9FjDNc1OYTeouSQJBS
	Tqf8WyajKjGKI0gTmAW9vbh4kBBRg8W0R8S1Kl3+Q=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=8BDGQ4Fd
	qGc47YRPKnVBGhtWheM=; b=LMgigk9LNH/DsMLFKWi/UEeD3FwBZsiqit4SG/rp
	9+7G6fY/ntDjmAESDGvTNwFPFP6BHSnrq3QtNy3h6PpaibsvXyFEM7OCwGmqqltG
	4hWn9xv+ViOj57jjcRwJwZiZgHwlyJXFJo+GZhh5SAW7pJrEdooE80IMwmfdXMhU
	XUc=
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.1 required=5.0 tests=AWL,BAYES_20,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-wg0-f50.google.com
MIME-Version:	1.0
X-Received:	by 10.194.8.35 with SMTP id o3mr29634235wja.3.1408216513687; Sat, 16 Aug 2014 12:15:13 -0700 (PDT)
In-Reply-To:	<53EF5552.4070807@si6networks.com>
References:	<53ED67D3 DOT 2020405 AT si6networks DOT com> <877g28enhq DOT fsf AT Rainer DOT invalid> <20140816104904 DOT GV28562 AT calimero DOT vinschen DOT de> <53EF5552 DOT 4070807 AT si6networks DOT com>
Date:	Sat, 16 Aug 2014 15:15:13 -0400
Message-ID:	<CAMKht8iBt85OEmCaNGUw_rY6Ye82PaPzEJdwe6S2dssR3PYBZw@mail.gmail.com>
Subject:	Re: Running a cygwin application on Windows
From:	Michael DePaulo <mikedep333 AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

On Sat, Aug 16, 2014 at 8:57 AM, Fernando Gont <fgont AT si6networks DOT com> wrote:
> 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?
>
> Thanks!
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont AT si6networks DOT com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
[...]

Hi Fernando,

I'm a volunteer contributor to the open source project X2Go.

In addition to producing a Cygwin package, you might want to do what
we currently do for the Windows builds of X2Go Client.

We provide 5 binaries linked against cygwin .DLL files. They are
nxproxy.exe (part "nx-libs", maintained by our project), and 4 patched
OpenSSH binaries: sftp.exe sftp-server.exe ssh-keygen.exe sshd.exe
(We of course provide the source code.)

Our build process needs improvement. But for now, after building those
binaries, our solution is to manually copy all of the following into
one single directory:
1. Those 5 binaries
2. All their cygwin .DLL dependencies
3. sh.exe
We then call the cygwin-built binaries from our native win32 app,
x2goclient.exe, like any other command-line binary. We can also call
them from cmd.exe.

We include the files (in one directory) as part of our NSIS installer

That's all there is to it if you only care about a small number of our
binaries working, and their dependencies don't require any directory
structure.

----

More info:

1. Our entire Windows build process is documented here. :
http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient

2. How we handle Cygwin updates is a larger discussion. Basically,
whenever we update cygwin, we rebuild our .binaries.  And I monitor
cygwin-announce for any security updates. Usually when there is a
security update (e.g., to openssl), we update the vulnerable.DLL files
individually and refer to it as a new "build" of x2goclient at version
X.

3. We do not package nx-libs for Cygwin because it is useless without
X2Go Client for Windows, which is only available for native win32, and
which in turn has native win32 dependencies.

4. We do not try to upstream our SSH patch because it is specific to
X2Go's needs.

5. You can determine what source package a file is from by running
"cygcheck". For example:
$ cygcheck -f /usr/bin/cygcrypto-1.0.0.dll
libopenssl100-1.0.1i-1
I do not know of an easy way to determine what binary package it is
from. However, the cygwin mirrors keep all the binary packages (and
the 1 source package) under a directory named after the source
package. For example:
ftp://mirrors.kernel.org/sourceware/cygwin/x86/release/openssl/
So after looking at the contents of the tarballs, I found it in this
binary package
ftp://mirrors.kernel.org/sourceware/cygwin/x86/release/openssl/libopenssl100/libopenssl100-1.0.1i-1.tar.xz

-Mike DePaulo

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

- Raw text -