I have a current develop branch and a new installation of VS2015 update 3 enterprise (on trial)

I have re-run bootstrap to rebuild bjam/b2 and do get a new version from the file datetime.

I have the compiler in my path.

I’ve built one library, chrono, as a test asking for 64-bit versions.

And to check that I don’t use cached properties, I’ve done a –reconfigure too.

I:\modular-boost>b2 --with-chrono -j8 --reconfigure --debug-configuration toolset=msvc address-model=64 architecture=x86 --build-type=complete link=static,shared threading=multi --libdir=./lib/X64 install > ../build_msvc_14.0_64_libs.log 2>&1

From the log file I note that I only have

Performing configuration checks

    - 32-bit                   : yes

But not  a 64-bit : yes

(nor even a ’64-bit : no’)

I seem to be building 64 and 32 bit libraries, as I hope and expect, judging by different file sizes for 32 and 64-bit versions.

This “32-bit : yes” suggests to me, perhaps wrongly, that I can only build 32-bit libraries.

Toolset=GCC-6.1.0 by contrast reports as I expect:

Performing configuration checks

    - 32-bit                   : no

    - 64-bit                   : yes

Am I deluded by this?

(Or does it really mean that the VS compiler is only a 32-bit compiler, even though it is emitting 64-bit code when requested?)

Paul

PS Full log file attached.

PPS Attentive and astute readers of the log file may note my Windows username is shown here as “Paula”.

But DO NOT PANIC or be worried for me, I have not had a sex-change operation, it is just that Windows 10 installer in its infinite wisdom decided that my username Paul A. Bristow merited “Paula” as my windows username ;-)