> On 09/27/2013 07:30 AM, Nogradi, Chris wrote:

> > The issue we are seeing is that a build that normally takes 2 minutes

> > with VS 2005, now takes twice as long with VS 2012.  I plan to attempt

> > to address this problem but wanted some advice from experts to ensure that

> > I approach it the right way


On 09/29/2013 07:04 PM, Watanabe, Steve wrote:

>Like this?

>local original-vars = [ SHELL "set" ] ;

>local new-vars = [ SHELL "$(setup) && set" ] ;

># Parse and diff the variable lists


Yes.  Thanks for the suggestion, I have implemented this using config-cache.jam as an example on how to create the batch setup files.  I have it working except for the following issues:

-          I would like the setup batch files to be rooted in the build directory for the jamroot regardless of where the command is executed.  The example in build-system.jam (line 689) on how to do this looks ‘scary’ per the comment and in the msvc.init I would presume these things are not even available yet.  Any suggestion on how to get this directory?

-          I am also writing the batch file creation action to a log file and was hoping that the actions performed (one batch file per cpu) would all be logged to the file specified in the UPDATE_NOW rule but apparently this rule overwrites rather than appending.  The only way around this that I can think of is to generate all the cpu specific batch files in one action (if I can figure out how to do this) and have a log file per compiler version. Is this the only option?





CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.