This is the mail archive of the
mailing list for the Cygwin project.
Re: Executing Windows commands from Cygwin with or without cmd: what are the pros and cons?
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Kenneth Wolcott <kennethwolcott at gmail dot com>, cygwin at cygwin dot com
- Date: Tue, 5 Nov 2013 04:19:33 +0400
- Subject: Re: Executing Windows commands from Cygwin with or without cmd: what are the pros and cons?
- Authentication-results: sourceware.org; auth=none
- References: <CADex0xyCNo4QmZ=gDC0hz2o4if-TKuYFE-cN=HbBTRp0arMM_g at mail dot gmail dot com> <2310234468 dot 20131105023748 at mtu-net dot ru> <CADex0xwzYP0oHQ6q8x4uu9QDnrFYeh8Un7Udr50j56vpmavzSQ at mail dot gmail dot com>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Kenneth Wolcott!
> I was going to execute a MS-VC++ compiler command, not a DOS/Windows command.
> I want to do as much as I could for capturing the stdout/stderr
> output and for capturing the exit status like I would as if I were on
> a Linux system, or the best that I can under these circumstances.
You can execute it from Windows batch file. With all the same benefits -
errorlevels, redirections and stuff.
Without having all the side-effects of path translation between Cygwin and
That aside, I don't see any apparent technical issues.
Andrey Repin (email@example.com) 05.11.2013, <04:17>
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple