Re: [Boost-build] MSVC toolset versions on VS2017

Subject: Re: [Boost-build] MSVC toolset versions on VS2017
From: Daniel James (dnljms_at_[hidden])
Date: 2017-11-20 13:08:49

On 20 November 2017 at 02:54, Tom Kent via Boost-build
<boost-build_at_[hidden]> wrote:>
>
> The interesting part about version numbers is three-quarters of the way down
> the post, under the "MSVC toolset version number increases to 14.12".
>
> The table that they have there is also illuminating:
>
> Visual Studio Version   |   MSVC Toolset Version  |  _MSC_VER
> ---------------------------------------------------------------
> VS2015 and updates 1, 2, & 3 | v140 in VS; version 14.00 | 1900
> VS2017, Version 15.1 & 15.2  | v141 in VS; version 14.10 | 1910
> VS2017, Version 15.3 & 15.4  | v141 in VS; version 14.11 | 1911
> VS2017, Version 15.5         | v141 in VS; version 14.12 | 1912
> ---------------------------------------------------------------

IIUC as 14.12 is still v141, which we call 14.1 in build, boost build
will treat 14.10-14.12 as the same version. I think that's what most
people would expect, but it's apparently going to be possible to
install minor versions side-by-side now, is that something we should
support? It's not supposed to be something that most people use, but
testers might want to. There's a 'vcvars_ver' parameter to
vcvarsall.bat to specify the version. Details are in this blog post:

https://blogs.msdn.microsoft.com/vcblog/2017/11/15/side-by-side-minor-version-msvc-toolsets-in-visual-studio-2017/