Re: [Boost-build] Very slow Visual Studio 2012 builds

Subject: Re: [Boost-build] Very slow Visual Studio 2012 builds
From: Juraj Ivanèiæ (juraj.ivancic_at_[hidden])
Date: 2013-11-04 17:13:19

On 4.11.2013. 22:01, Nogradi, Chris wrote:
>
> Well I had originally implemented this wrong as well and Steve
> corrected me. I think you REALLY want to create a batch file with
> the environment variables set to deal with command line size
> limits and make it a dependency of all the compile/assembly/link/...
> targets.

I don't see why I would want to create that batch file. What command 
line size limits? Jam action is like a script, not a (single) command.

 > This also makes incrementals a bit faster since the batch
> file is created once and then used on every subsequent build. I
> originally did this but have not had time to fix it to do what
> Steve suggested (also it is going to take me a while to figure it
> out since I am not an expert):

With my current approach, setup scripts are executed only once, and any 
environment side-effects they produce are saved by boost build. 
Consequently, I call a bunch of SETs directly instead of calling a batch 
file containing exactly those SETs. This can only be faster.