Sorry all, I meant to send this to the list but only replied to Daniel. This adds an option 4 and 5. On Sun, Mar 19, 2017 at 3:58 PM, Tom Kent wrote:

On Sun, Mar 19, 2017 at 10:17 AM, Daniel James wrote:

...

On 19 March 2017 at 13:10, Tom Kent via Boost wrote:

...

Option 1 - 14.10 Use microsoft toolset version based on cl.exe version

...

This is the official version of the c++ toolset that microsoft has been pushing (somewhere). The new $(VCToolsVersion) macro is "14.10.25017",

-5. this

...

macro is not available in previous versions of visual studio.

build bootstrap would use bootstrap.bat vc1410

[snip]

...

Option 2 - 14.1 Use the abbreviated toolset version that microsoft uses for their toolset version. The $(PlatformToolsetVersion) macro is "141". In VS2015 this was "140".

[snip]

...

I *think* that is all the reasonable options. Let the consensus form!

I disagree, I think we should limit ourselves to values that Microsoft actually uses. As far as I'm aware, they don't use 1410, and they don't use 14.1. There are already too many ways of writing the version number, adding more will just add to the confusion.

So 2-a would meet these requirements. However, I did overlook the mixed options:

Option 4 (141 and 14.10) - build bootstrap would use bootstrap.bat vc141 build of source would use b2 toolset=msvc-14.10 build would generat libraries of the format libboost_NAME_vc141-OPTIONS-1_ 64.lib config would auto-link libraries of the same format (4-a is the same as 2-a)

Option 5 (1410 and 14.1) - build bootstrap would use bootstrap.bat vc1410 build of source would use b2 toolset=msvc-14.1 build would generat libraries of the format libboost_NAME_vc1410-OPTIONS- 1_64.lib config would auto-link libraries of the same format (5-a is the same as 1-a)

Tom