Capturing Build Output on Win32
Mon Aug 28 07:56:00 GMT 2000
Setting up and extending the environment of a spawned process
is something that I have found to be very useful too. I wrote
a separate tool (premake.exe) that does what you describe. It
takes a "config" file that defines an environment for a particular
target. Custom targets can be named (vc6, vc5, etc.) and a
specific environment loaded for them by referencing a section of
the config file.
I worked on preMake in '99 but haven't done much with it recently.
Sources are available at www.sourcequest.com\software.html. I
believe it is now "hardcoded" to work only with nmake.exe but it
could be modified to support other make programs too.
If there is interest in premake, I could put together some
documentation, and add a binary only download.
> -----Original Message-----
> From: Thomas Heller [ mailto:email@example.com ]
> Sent: Monday, August 28, 2000 12:50 AM
> To: Stan Mitchell; Reinhard. Griech@Pcm. Endress. Com; Source Navigator
> Mail-List; Syd Polk
> Subject: Re: Capturing Build Output on Win32
> 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)
> What do you think?
More information about the Sourcenav