public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Franz Fehringer <fehrin2@gmail.com>
To: cygwin@cygwin.com
Subject: Re: antrun versus wsl versus cygwin
Date: Mon, 18 Feb 2019 09:25:00 -0000	[thread overview]
Message-ID: <q4dt14$3ct7$1@blaine.gmane.org> (raw)
In-Reply-To: <6bc8cc1f-0535-9a41-0d6a-4c121e6d7955@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]

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="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 symlink
> mybash.exe, that points to cygwin bash.exe? Would mybash.exe invoke the right bash?
> 

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.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2019-02-18  9:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 12:53 Franz Fehringer
2019-02-17 13:39 ` Thomas Wolff
2019-02-17 14:14   ` Franz Fehringer
2019-02-18 20:54     ` Thomas Wolff
2019-02-17 14:46 ` LRN
2019-02-18  9:25   ` Franz Fehringer [this message]
2019-02-17 15:35 ` Houder
2019-02-18  8:28   ` Franz Fehringer
2019-02-17 22:10 ` Csaba Ráduly
2019-02-17 23:05   ` Franz Fehringer
2019-02-18  3:08     ` Andrey Repin
2019-02-18  7:20       ` Franz Fehringer
2019-02-18  9:40       ` Franz Fehringer
2019-02-18 10:58         ` Houder
2019-02-18 12:59           ` Franz Fehringer
2019-02-18 13:16             ` Houder
2019-02-18 14:11               ` Franz Fehringer
2019-02-18 17:06                 ` Houder
2019-02-18 17:10                   ` Franz Fehringer
2019-02-18 20:52                   ` Franz Fehringer
2019-02-19 10:31             ` Houder
2019-02-19 19:15               ` Franz Fehringer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='q4dt14$3ct7$1@blaine.gmane.org' \
    --to=fehrin2@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).