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 20:33:42

On 4.11.2013. 23:28, Steven Watanabe wrote:

> A few more:
> - If a user explicitly specifies a setup script,
>    it should be honored.

Just tried it and it works, to the extent it works for MSVC setup 
scripts. It will fail, though, if user setup script is doing
something 'smarter' than merely setting up environment variables,
i.e. if user expects it to be called from every action.

I cannot think of a reason why anyone would do that, but for them
this would be a breaking change.

> - Please use set.difference instead of a raw loop.

Check.

> - Make sure that this works with a cygwin built b2
>    (That's what the if ! [ os.name] in NT section
>    that you deleted is supposed to be handling.
>    I say "supposed to", because although the batch
>    script will run without errors, the environment
>    changes will be discarded.)

I played for a while with cygwin built b2. This 'supposed'
part seems to work OK, quotes around '>nul' and '&&' make
cmd.exe process the rest of the command, so environment
is not discarded.

I am not sure how to make this 'batch file caching' work on
cygwin though. AFAICS it boils down to generating a
simpler (faster) batch file, like Chris is doing. I don't
think its worth the hassle. Not to me, anyway.

How about just leaving cygwin to work as it did, and speed up
msvc?