Subject: Re: [boost] [build] VC++ 2017 version number?
From: Stephan T. Lavavej (stl_at_[hidden])
Date: 2017-03-14 21:26:02
[Olaf van der Spek]
> In the past IDE and toolset version numbers were equal weren't they?
Yes (the IDE gained multitargeting powers a while back, but it involved having an older IDE installed).
> 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.
The libraries themselves don't have a distinct version macro, yet. They'll gain one in the future when our binary-incompatible branch is available.
The compiler's version number has the most seniority and is the most readily available to C++ programs via _MSC_VER, so it makes a lot of sense to test.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk