I am trying to set up an automated build system on Windows using Cygwin. Among other things, it needs to be able to build several Visual C++ solutions. I have a script which sets up the environment variables needed for devenv, and if I type ‘devenv’ in bash it brings up the Visual Studio IDE. No problems so far.
I am also able to build a solution from cygwin’s bash prompt by typing
$ devenv mysolution.sln /build Debug
The problem is that it is not showing me the build output. In fact, it does not even tell me whether or not the build succeeded. The command simply finishes, and I get back the prompt. Then I can go into the output directory, and check whether or not the executable was created, but for a build system I want to be able to grep for errors.
What am I doing wrong? I can see the debug output when I run devenv in the windows shell, but not in cygwin. Where is it being sent, and how do I get it back?
Will cygwin find and run .com files?
There are 2
devenvexecutables, one isdevenv.comwhich is a console mode application that handles stdin, stdout and stderr proxying for the other executable,devenv.exe, which is a GUI mode application. Ifdevenv.exeis what cygwin is loading then there will be no stdin/stdout stuff. Ifdevenv.comis being loaded, it should launchdevenv.exewhile proxying the stdout stuff to the console.Maybe if you explicitly specify that
devenv.comshould be run?