X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:message-id:from:reply-to:to:subject :references:in-reply-to:content-type; q=dns; s=default; b=sEbq8C R7x4K1LWLcg+U+AHrx0nEe2X7zW6SNK0FvA2NLTaV0qPL9omT7DPUUzf3zK1B4mp M+CgZybEBSutpPTrcP6qzE7V0zx+JxRq5Nn2C7Q0t9gbDhLRREU+EZLmEdbxNjbA Tuxahacf3Z4CV5okT0y+g3rP6GWxJmxVDmdZc= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:message-id:from:reply-to:to:subject :references:in-reply-to:content-type; s=default; bh=/Ac5zjnJGIGS WP78rNex4Xlx8xo=; b=jnC9wnzj3i2EA8O1mrrDq5B84dxrYCRoMSTYIyL5wovM RLhTO5fxpry4uUd5t2PHn+9qVOrwbmIw/Y2Nsq89cqqgguLPZ7FOI+P+Qbl6cyzk MbtmyGr+JY2a+sSRHDazASo95k068U1lQWLL/YSxFZO+p811lTJSHmamwHWC8M0= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=executables, delegates, H*F:D*nl, somewhere X-HELO: lb2-smtp-cloud7.xs4all.net Date: Mon, 18 Feb 2019 14:07:01 +0100 Message-ID: From: Houder Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: antrun versus wsl versus cygwin References: <0f26a1aa-7c70-5201-5212-5f3df54a50fa AT gmail DOT com> <1968849310 DOT 20190218020001 AT yandex DOT ru> In-Reply-to: Content-Type: text/plain; charset=UTF-8; format=fixed User-Agent: mua.awk 0.99 On Mon, 18 Feb 2019 13:15:02, Franz Fehringer wrote: > Am 18.02.2019 um 11:42 schrieb Houder: [snip] > > Now show us the output of an antrun script, where the executable > > is C:\Tools\Cygwin\bin\which and its argument: bash > > > > Henri > > > > > > > > > > > > > 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 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. " This tells me that "Cygwin" is in C:\Tools\Cygwin\bin; it also tells me that cygwin1.dll is that directory, as "which" can be invoked ... And bash is also found in C:\Tools\Cygwin\bin, I believe. (which can be verified by "where bash"). Consequenly Cygwin's bash can be invoked (even from a Windows JVM). It does not matter that Runtime.exec calls ::CreateProcess. I have no idea what "build" is or does ... Apparently, it refers in some way to the WSL executables ... As Windows JVM is not installed at my place (and I am using W7, where WSL cannot be installed), I cannot help you forward beyond this point. Henri -- 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