This is the mail archive of the
mailing list for the Cygwin project.
Re: Why can't run.exe execute a shebang script directly?
- From: John Wiersba <jrw32982 at yahoo dot com>
- To: Eric Blake <eblake at redhat dot com>, "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Fri, 24 Oct 2014 09:40:52 -0700
- Subject: Re: Why can't run.exe execute a shebang script directly?
- Authentication-results: sourceware.org; auth=none
- References: <1414155946 dot 62587 dot YahooMailNeo at web162803 dot mail dot bf1 dot yahoo dot com> <20141024135339 dot GM20607 at calimero dot vinschen dot de> <1414163944 dot 58941 dot YahooMailNeo at web162803 dot mail dot bf1 dot yahoo dot com> <544A6FB4 dot 5070004 at redhat dot com>
- Reply-to: John Wiersba <jrw32982 at yahoo dot com>
> From: Eric Blake <firstname.lastname@example.org>
> On 10/24/2014 09:19 AM, John Wiersba wrote:
>> I thought that all (or virtually all) cygwin-supplied programs that start
>> other programs use the cygwin1.dll execve(2) emulation to start them,
>> the execve emulation can be used to start *both* cygwin programs and
>> native programs. Or at least it seems that way to me.
>> Is there be in drawback to having run.exe start its target program using
>> the execve emulation in cygwin1.dll, rather than using a Windows call to
>> start the target executable?
> run.exe is special. In order to hide consoles, it MUST use native
> windows API instead of cygwin1.dll calls.
OK -- I guess that settles it, then! Thanks!
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple