X-Recipient: archive-cygwin@delorie.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:to:from:subject:date:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=WQNU
	sjiQrw1MRlmXUVXKf1sPEnGmhA5064xl6hWBv2pQRXwwmhLo1K6QOA6pm4XiJcoS
	CLLs1Sz0H/ZwD3A9vnZ/erAJGc+8Sk2nkVuboDoDe9mCmL/MKYT8ugASevr/9q3O
	IE1LUNF2z3Z5qdnbezM9OsbdI0nf15JdwElWLTQ=
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:to:from:subject:date:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=UyYSFrHEa7
	DQH3pB4HgQdiS7Ayg=; b=LzacWY1z4JTAsW5ofLwOYyOYcJuvLp2YuclyWgCIV7
	5FUZA6MvC1+C1adnO+ZRP8S7uqVES6wuahsGIcpezl+ybPAH7Khj3voof/G3yzvG
	T0L/UHn9bUj1/Oz1y+mLhNleOlhpG3Yblzz4TOQBtVbq6n2Ci//MQSHQKjY6qBEU
	U=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=1.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA,FREEMAIL_FROM,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*UA:x64, H*UA:Win64, H*u:x64, H*u:Win64
X-HELO: blaine.gmane.org
To: cygwin@cygwin.com
From: Franz Fehringer <fehrin2@gmail.com>
Subject: Re: antrun versus wsl versus cygwin
Date: Mon, 18 Feb 2019 10:14:14 +0100
Message-ID: <q4dt14$3ct7$1@blaine.gmane.org>
References: <q4bfgv$2i9q$1@blaine.gmane.org> <6bc8cc1f-0535-9a41-0d6a-4c121e6d7955@gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nAZjjMLK63CDmt1TwJ5GVtbkQAL4s5Y3a"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
Openpgp: preference=signencrypt
In-Reply-To: <6bc8cc1f-0535-9a41-0d6a-4c121e6d7955@gmail.com>
X-IsSubscribed: yes

--nAZjjMLK63CDmt1TwJ5GVtbkQAL4s5Y3a
Content-Type: multipart/mixed; boundary="4LlY632OqJ3bo5uCt2hR5fqn9hd0Q78ps";
 protected-headers="v1"
From: Franz Fehringer <fehrin2@gmail.com>
Newsgroups: gmane.os.cygwin
Subject: Re: antrun versus wsl versus cygwin
References: <q4bfgv$2i9q$1@blaine.gmane.org>
 <6bc8cc1f-0535-9a41-0d6a-4c121e6d7955@gmail.com>
In-Reply-To: <6bc8cc1f-0535-9a41-0d6a-4c121e6d7955@gmail.com>


--4LlY632OqJ3bo5uCt2hR5fqn9hd0Q78ps
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Am 17.02.2019 um 15:14 schrieb LRN:
> On 17.02.2019 14:11, Franz Fehringer wrote:
>> Hi all (half off topic),
>>
>> I have installed (on a Windows 10 1809 system) both Cygwin and WSL (only
>> the Windows component, no real Linux distribution yet).
>> This scenario gives me a strange problem with antrun: With <exec
>> executable=3D"bash"> i always get the WSL bash instead of the Cygwin one,
>> although Cygwin is first in PATH (both Cygwin PATH and Windows PATH),
>> even so if C:/Windows/System32 (location of WSL bash) is not in the
>> (Cygwin) PATH at all.
>=20
> Tried looking in
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths"
> ,
> "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\App Paths"
> and
> "HKEY_CLASSES_ROOT\Applications\"
> ? They might have bash.exe in them. Also, what happens if you create a sy=
mlink
> mybash.exe, that points to cygwin bash.exe? Would mybash.exe invoke the r=
ight bash?
>=20

There are no bash matches at the registry locations given. antrun can
execute Cygwin bash without problems (i temporally moved wsl bash.exe to
wslbash.exe), but it finds wsl bash before Cyhwin bash regardless of
PATH settings.



--4LlY632OqJ3bo5uCt2hR5fqn9hd0Q78ps--

--nAZjjMLK63CDmt1TwJ5GVtbkQAL4s5Y3a
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJcandmAAoJECvloiiFUsQ+W1wP/38S6dw0S0dZkdo3DYndY1/w
lJMIySCfKvf3cRC6ak4R5k1aPw4Cpj9Jy4UF52N9KniBYF/VZHU2xYN+Aa+ymKYh
Pz8MX/4UniNDJ6Gn6K0BoMotL1r8vOv503bpFO+i4+geMg48N6r8iBDEwqajhv6N
gYIrX9u/8XtdBGirYJn+WW34tYMBXFC7k2FgoL9QOMhhCVdnCw+mOkfb1iCvr7Pt
6zjfkGd08Q6xZicHDCnKiDxp1PUvjnfYgdn6A8HV9+DefRMz9d7UMwUb4WuBokVZ
BKjT/ZXe5l274eNwCA9ymGh4DoCyqjdIdljAdEIY2t7zBPdnotflUfcJDiGBIzXv
7KMBlwPdzUq3vFimtYYLopDb59YsG+tZshhlmts+XHU8GihmS3W7UfCTTie2+Z3+
+8qhrAunPU9PZ0Hp09TdKLalih+Rk3Nbbv91hR7qmZ4bIhM53qBmMmxfgOG4i9L3
lfTMqwOoWtVKtWQT4To1A5sicNafrM84cMvPjc9dzaI8Co7U74EbbNzTQDkxGcV7
9YNYCdGlvkcjMMGdnXrqL4GXElXg3L4kYDgQVBQn6dwAxMUxXAgj6h4rJmf1di9l
BWasblVDwHK1jxxM0e1guLZd4/okkPVFNWCa1wx95YBM/F765uZoHk9XSx64UB+h
9ED8Ynbgj8Dk53gsbm3Z
=l93A
-----END PGP SIGNATURE-----

--nAZjjMLK63CDmt1TwJ5GVtbkQAL4s5Y3a--