From: Franz Fehringer <fehrin2@gmail.com>
To: cygwin@cygwin.com
Subject: Re: antrun versus wsl versus cygwin
Date: Mon, 18 Feb 2019 12:59:00 -0000 [thread overview]
Message-ID: <q4e7k5$5mhm$1@blaine.gmane.org> (raw)
In-Reply-To: <dcaadf0982c8bbdf27cb7f1301889c9f@smtp-cloud8.xs4all.net>
Am 18.02.2019 um 11:42 schrieb Houder:
> On Mon, 18 Feb 2019 10:25:42, Franz Fehringer wrote:
>
> <echo message="XXX: ${env.PATH}"/> in the antrun block gives
>
> 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
>
> Now show us the output of an antrun script, where the executable
> is C:\Tools\Cygwin\bin\which and its argument: bash
>
> Henri
>
>
<exec executable="C:\Tools\Cygwin\bin\which" failonerror="true">
<arg line="bash" />
</exec>
<exec executable="bash" failonerror="true">
<arg line="-c src/main/resources/build" />
</exec>
gives
[exec] /usr/bin/bash
[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 ti 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
It is as if C:\Windows\System32 were hardcoded somewhere
The ant exec documentation says
"The <exec> task delegates to Runtime.exec which in turn apparently
calls ::CreateProcess. It is the latter Win32 function that defines the
exact semantics of the call. "
--
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
next prev parent reply other threads:[~2019-02-18 12:15 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
2019-02-18 10:58 ` Houder
2019-02-18 12:59 ` Franz Fehringer [this message]
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='q4e7k5$5mhm$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).