Re: antrun versus wsl versus cygwin

[Franz Fehringer <fehrin2 at gmail dot com>]

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