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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=dzEvn73Qd/vGcqjz
	asZyggmkFl0D0LG4b0lgrtHs9mV4QWjeMxzX2PC77dOzomPmHyQMJFN5zO2pAq7X
	9B+rs5ogO8qjx9GXboVHiw+/6HGAIvndVT243X8d28swFb8KlJVLJPeeJA0P3O8d
	8Hcyly3Re6orjneDKLF0JxDg1Fo=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=DA8LvcXO9UVZlDcQigSTVD
	mnyE8=; b=SP2tLKivbclIGDMbEEhTPeuLEUlRZhPvX7ISY/7biFAPFhjqi3iICd
	QBGKY3hOwGnKA84TltiUVE8Q2emPVIrT/kplwurkgb/FekpEeSKIfJOVhBrDtVVt
	gUxDtwwVSHcKhrHbdfwnR6eLk3qZ4oR+/iYEfLLnYCxNMZWFwpGig=
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-Spam-SWARE-Status:	No, score=-1.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=fex.belwue.de, UD:belwue.de, UD:cygwin.html, cygwinhtml
X-HELO:	smtp-out-so.shaw.ca
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: running self compiled 32 bit binary on 64 bit Windows?
To:	cygwin AT cygwin DOT com
References:	<20180606115005 DOT GA15015 AT rus DOT uni-stuttgart DOT de> <0F7D3B1B3C4B894D824F5B822E3E5A17787FB4BB AT IRSMSX102 DOT ger DOT corp DOT intel DOT com> <3110356010 DOT 20180606204945 AT yandex DOT ru> <540c62ab-2519-9f57-6565-d536d8b74ef2 AT gmail DOT com> <944481618 DOT 20180607010455 AT yandex DOT ru> <20180608133017 DOT GB20898 AT rus DOT uni-stuttgart DOT de> <0F7D3B1B3C4B894D824F5B822E3E5A17787FD684 AT IRSMSX102 DOT ger DOT corp DOT intel DOT com> <20180608135221 DOT GF20898 AT rus DOT uni-stuttgart DOT de> <49498971 DOT 20180608194124 AT yandex DOT ru> <20180709002131 DOT GA3525 AT rus DOT uni-stuttgart DOT de> <1124060518 DOT 20180709051834 AT yandex DOT ru>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp:	preference=signencrypt
Message-ID:	<47172619-d88a-6e62-bb01-df3de0ea9f4a@SystematicSw.ab.ca>
Date:	Mon, 9 Jul 2018 00:22:14 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0
MIME-Version:	1.0
In-Reply-To:	<1124060518.20180709051834@yandex.ru>
X-IsSubscribed:	yes

On 2018-07-08 20:18, Andrey Repin wrote:
>> On Fri 2018-06-08 (19:41), Andrey Repin wrote:
>>>>> 2.) Do a Cygwin build and copy cygwin1.dll

>>>> I already have a /usr/bin/cygwin1.dll on the Windows 8 target system.

>>> It's a wrong architecture. You need a 32-bit one for your 32-bit program.

>>>> Do I have to replace it?

>>> No.
>>> Just build a 64-bit version of your program.

>> SIGH. I was hoping a 32 bit cygwin with 32 bit self compiled programs will
>> run on 64 bit Windows, too. But I was wrong.

He just means that you must provide matching Cygwin DLLs and exes which are
either all built as x86 (32 bit), or all as x86_64. Cygwin x86 programs will run
on Windows x64 or x86 desktops as they support x86 programs.
From Windows Server 2008 R2, all *servers* are x64 only, and x86 support is an
optional installable feature on *servers*, except it is still required for AD
support, which MS has still not rewritten for x64.

>> Meanwhile I have 4 VMs:
>> Windows 32 bit with 32 bit cygwin
>> Windows 32 bit with 32 bit cygwin for compiling
>> Windows 64 bit with 64 bit cygwin
>> Windows 64 bit with 64 bit cygwin for compiling

> You can install both 32 and 64-bit Cygwin on the same machine.
> So you don't really need 4, while I see how having a build system separate is
> a good idea.

>>>> This is what I first did:
>>>> Transfered the 32 bit cygwin with my self compiled binaries

>>> You have to install Cygwin, not "transfer".

>> I have several 100 users, none of them is able to install cygwin

> *You* have to do it.
> Cygwin offers tools to automate process.

More explanation would be helpful.
He could setup a package download structure, including setup-x86[_64].exe and
setup.ini, zip that for transfer, unzip that in a known location, then run the
included setup in unattended mode with fixed arguments, to setup the Cygwin
environment, install the base and other packages.
Have you other suggestions?

>> and the packages they need the official way, they are way to *CENSORED* for
>> this job :-} 
>> I give them my preconfigured cygwin.zip (or cygwin64.zip) and tell them to
>> unpack it in C:\
>> http://fex.belwue.de/usecases/cygwin.html
>> (This is what I call "transfer cygwin")
>> This works so far without problems.

> Only by accident and promise.

More explanation would be helpful.
What problems do you see with his process?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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