DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=eH7m
	Aaq1/G1b5uT3Dox63LPBCzdLRi+EhMhJo9vcniJcRMlhuixgLpYRlMOqNJRhSK/9
	g0Cd42Z1vvWr9egAZWKKOkxtMK8rXcLb9pRpzvrkJQQglymN2G5e6C+LJ65P5Mop
	sCRpgfBL5DHKvDr/fW2CO4a0uwMB6x0TBv148gQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: antrun versus wsl versus cygwin
To: cygwin AT cygwin DOT com
References: <q4bfgv$2i9q$1 AT blaine DOT gmane DOT org>
From: LRN <lrn1986 AT gmail DOT com>
Message-ID: <6bc8cc1f-0535-9a41-0d6a-4c121e6d7955@gmail.com>
Date: Sun, 17 Feb 2019 17:14:16 +0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <q4bfgv$2i9q$1@blaine.gmane.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yRU2wnK0ZNxEHr6ApM8huUXDwxQ50kVMC"

--yRU2wnK0ZNxEHr6ApM8huUXDwxQ50kVMC
Content-Type: multipart/mixed; boundary="2roeWOeu5f4jNmdm2HjkOJWwLem9COq6n";
 protected-headers="v1"
From: LRN <lrn1986 AT gmail DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <6bc8cc1f-0535-9a41-0d6a-4c121e6d7955 AT gmail DOT com>
Subject: Re: antrun versus wsl versus cygwin


--2roeWOeu5f4jNmdm2HjkOJWwLem9COq6n
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 17.02.2019 14:11, Franz Fehringer wrote:
> Hi all (half off topic),
>=20
> 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.

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 syml=
ink
mybash.exe, that points to cygwin bash.exe? Would mybash.exe invoke the rig=
ht bash?


--2roeWOeu5f4jNmdm2HjkOJWwLem9COq6n--

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

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE4MWzR43wYaAzEA49ja3pJ2dZunQFAlxpbEAACgkQja3pJ2dZ
unSS4Q/8CfLjMcVLMungCbKb6/Lfu6GssRFzvUG1zSvzgHrvsJbcLwzF5Z1XOWF/
3EqrtZgXtbBLK6OaEwHBUP+UTEMpy9MhqN0uC6ejOfZmy85Ul7htzlHRA+v6ebXI
iTgUC6deArcTywP0Js150mC+/91rgAA5vvTHuMKxQk6V8PMNCXycgRoh8gtFkdvE
xlsk8UosmmDgr5mgw/wKTErDJ3DMiNg+9GrG4gk2N3GFi4EXvHXWKdYcLW2QP0cU
UzHr/yBkJguBTrPaDtHEngDWBh5tSWI0ALC7ZajrAkIY6QfXMf9uqXckUNXgzsg3
onrlIdN9Tij08iAgV38gQkd5yE+Z46mFhqhO5hYI+8Rm+qgWi+A/c2oCfZpvNgks
EDFacE2n5a6hOjLyHLscnaQNk8PPlAtEJMgTk0rtfqsqVJwXP+FOD4DvfwuRhahq
AsTHyvDDBzElQHDeb08c99r/NnM36YyDFt+9cY7Iabi4zaLOtORgDofMdNDZeoD2
XhF2H6C+OchjxPqadjFELLuZMUXgNwDBTGknp40pauj1aRMsJkt/QIo/ASgW2265
iAl0IacQYtnCcu1sKIdCG8atYKUsznOhS/kuFDTuYiRNTeoMWR/dRvxi//o8bd2S
lJPOahtjB1/PDO5mv1Bh1P3iQX+OIrMDF/tFBkeLl9KefhJ6uAA=
=WYqc
-----END PGP SIGNATURE-----

--yRU2wnK0ZNxEHr6ApM8huUXDwxQ50kVMC--