From: Franz Fehringer <fehrin2@gmail.com>
To: cygwin@cygwin.com
Subject: Re: antrun versus wsl versus cygwin
Date: Mon, 18 Feb 2019 09:40:00 -0000 [thread overview]
Message-ID: <q4dtmk$5gpb$1@blaine.gmane.org> (raw)
In-Reply-To: <1968849310.20190218020001@yandex.ru>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2584 bytes --]
Am 18.02.2019 um 00:00 schrieb Andrey Repin:
> Greetings, Franz Fehringer!
>
>> Am 17.02.2019 um 20:09 schrieb Csaba Ráduly:
>>> On 17/02/2019 12: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.
>>>
>>> Is this a Cygwin ant or a Windows ant ?
>>>
>>> Csaba
>
>> Windows ant via Windows maven (antrun plugin) in a Cygwin shell.
>
> Check what Maven sets the environment to.
>
>
<echo message="XXX: ${env.PATH}"/> in the antrun block gives
[echo] XXX:
C:\Projekte\dev\bin\gmake41;C:\Tools\VisualStudio\2017\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64;C:\Tools\VisualStudio\2017\VC\VCPackages;C:\Tools\VisualStudio\2017\MSBuild\15.0\bin\Roslyn;C:\Tools\VisualStudio\SDK\10\bin\10.0.17763.0\x64;C:\Tools\VisualStudio\SDK\10\bin\x64;C:\Tools\VisualStudio\2017\MSBuild\15.0\bin;C:\Tools\VisualStudio\2017\Common7\IDE;C:\Tools\VisualStudio\2017\Common7\Tools;C:\Windows\Microsoft.NET\Framework64\v4.0.30319;C:\Tools\Perl\site\bin;C:\Tools\Perl\bin;C:\Tools\Cygwin\usr\local\bin;C:\Tools\Cygwin\bin;C:\Tools\apache-maven-3.6.0\bin;C:\Tools\apache-ant-1.10.5\bin;C:\winapp\openjdk\java-1.8.0-openjdk-1.8.0.191.x86_64\bin;C:\Tools\Depends64;C:\Tools\IBM\DB2\BIN;C:\Tools\IBM\DB2\FUNCTION;C:\Programs\ibm\gsk8\lib64;C:\Windows\System32\wbem;C:\Windows\System32;C:\Windows;.;C:\Projekte\dev\bin;C:\Projekte\dev\bin\userscripts;C:\Projekte\dev\LF4\LF19.1.0\utils;C:\dev\LF4\LF19.1.0\src\lfjee\lf-lc\ipl-core-lc\ipl-core-lc-sc\ipl-core-lc-sc-server\target\tbfserver\lib\cpp
[exec] W i n d o w s S u b s y s t e m f o r L i n u x h a
s n o i n s t a l l e d d i s t r i b u t i o n s .
[exec] D i s t r i b u t i o n s c a n b e i n s t a l l e
d b y v i s i t i n g t h e M i c r o s o f t S t o r e :
[exec] h t t p s : / / a k a . m s / w s l s t o r e
i.e. Cygwin bin before Windows system32
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒ÷\a&ö&ÆV×2æFÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöf\x17\x12ðФFö7VÖVçF\x17Föã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöFö72æFÖÀÐ¥Vç7V'67&&R\x06æfó¢\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöÖÂò7Vç7V'67&&R×6×\x06ÆPÐ Ð
next prev parent reply other threads:[~2019-02-18 9:25 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
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 [this message]
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='q4dtmk$5gpb$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).