Re: [boost] [build] VC++ 2017 version number?

Subject: Re: [boost] [build] VC++ 2017 version number?
From: Vic Luo (vicluo96_at_[hidden])
Date: 2017-03-24 01:45:19

I submitted a patch to CMake to treat 19.10 as '-vc150' in
FindBoost.CMake months ago, see:
https://gitlab.kitware.com/cmake/cmake/merge_requests/314

Now I think additional patch might be required due to recent change in
Boost.build.

On Fri, Mar 17, 2017 at 6:09 AM, Mateusz Loskot via Boost
<boost_at_[hidden]> wrote:
> On 14 March 2017 at 22:26, Stephan T. Lavavej via Boost
> <boost_at_[hidden]> wrote:
>> [Olaf van der Spek]
>>
>>> Can't MS use a single version number for the compiler *and* the toolset?
>>
>> The compiler is part of the toolset (which includes the linker and the libraries). The IDE is distinct from the toolset.
>>
>> At the moment, the compiler and the libraries march in lockstep - you can't use an older compiler with newer libraries (that will never work, ever) and we don't support using a newer compiler with older libraries. The toolset is versioned (according to the IDE) as v141 while the compiler is versioned at 19.1, but we consider them to be the same thing, really.
>
> Digression:
> After day spent on updating fairly large build configuration to
> VS2017, what a dance of versions:
>
> MSBuild:    PlatformToolset=v141
> Boost:   bootstrap.bat vc1410
> Boost:   b2 toolset=msvc-14.10
> IncrediBuild:   BuildConsole.exe /vsversion="vc15" (notice, "vs" in
> switch vs "vc" in value)
> CMake:   Visual Studio 15 2017
>
>
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost