Boost logo

Boost :

Subject: Re: [boost] [release] Boost 1.64.0 Beta 1
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2017-03-27 11:44:08

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Oliver Kowalke via Boost
> Sent: 27 March 2017 11:39
> To: boost
> Cc: Oliver Kowalke
> Subject: Re: [boost] [release] Boost 1.64.0 Beta 1
> 2017-03-27 11:03 GMT+02:00 Deniz Bahadir via Boost <boost_at_[hidden]>:
> did you run b2 with option --reconfigure? otherwise you use the cached
> values of the feature check

You probably also need to delete the cached values

Eventually, after some loss of hair and nearing monitorial defenestration, I realised that to
get a completely clean build after changing the compiler features installed, usually from an update,

using –a –clean –reconfigure do not suffice.

One must also remove the several cached versions of vcvarsall.bat at


You can delete these at any time and they will be recreated automatically.

Proof of generating a clean copy of these files look something like this:
I:\modular-boost\libs\hello_boost\example>b2 -a toolset=msvc-14.0
CRT_IncludePath_x64 = C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt using msvc
...found 1 target...
...updating 1 target...
msvc.write-setup-script C:\Users\paula\AppData\Local\Temp\b2_msvc_14.0_vcvarsall_x86.cmd
...updated 1 target...
...found 1 target...
...updating 1 target...
msvc.write-setup-script C:\Users\paula\AppData\Local\Temp\b2_msvc_14.0_vcvarsall_amd64.cmd
...updated 1 target...
...found 1 target...
...updating 1 target...
msvc.write-setup-script C:\Users\paula\AppData\Local\Temp\b2_msvc_14.0_vcvarsall_x86_arm.cmd
...updated 1 target...

If you do not have a clean copy, the 'cached' version of vsvarsall.bat will be used, with undesirable results.



Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
+44 (0) 1539 561830

Boost list run by bdawes at, gregod at, cpdaniel at, john at