Capturing Build Output on Win32

Mo DeJong
Mon Aug 28 11:06:00 GMT 2000

On Mon, 28 Aug 2000, Thomas Heller wrote:

> Stan wrote:
> > 
> > Yes, dealing with Win32 console windows is sometimes daunting.
> > I've had some luck at coming up with a solution for Win2k/WinNT.
> > Instead of directly spawning a build tool, I launch an intermediate
> > process, which I've tentatively named sncapture.exe. Using the example
> > I gave earlier, the Build dialog would have this command line:
> > 
> >      ../snav/bin/sncapture.exe c:/bin/premake.exe -?
> > 
> > sncapture spawns premake.exe using the inherited handles for
> > stdin/stderr/stdout
> > and it explicitly hides the new console window. It then does a
> > WaitForMultipleObjects on the process handle for premake.exe.
> > Using this approach all stderr and stdout goes into the browser window.
> > This is a general solution, it works equally well with other front-end
> > programs.
> > 
> IMHO it would be usefull to allow your sncapture program to setup/extend
> an environment for the spawned process. This would allow to use
> VC6 on one project, Borland in another and so on.
> The enviroment could come from an ini-file, given as (optional)
> argument.
> What do you think?
> Thomas

You can already set a per build target toolchain. You need to
actually create the toolchain spec, but it is not hard
(see online docs for the details).

Mo DeJong
Red Hat Inc

More information about the Sourcenav mailing list