Re: [Boost-build] [boost] [release] 1.64.0 Delayed because of Microsoft (version numbers)

Subject: Re: [Boost-build] [boost] [release] 1.64.0 Delayed because of Microsoft (version numbers)
From: Marcel Raad (raad_at_[hidden])
Date: 2017-03-20 13:18:01

Boost - Build mailing list wrote
> Option 1 - 14.10 Use microsoft toolset version based on cl.exe version -5.
> This is the official version of the c++ toolset that microsoft has been
> pushing (somewhere). The new $(VCToolsVersion) macro is "14.10.25017",
> this
> macro is not available in previous versions of visual studio.
> 
> build bootstrap would use bootstrap.bat vc1410
> build of source would use b2 toolset=msvc-14.10
> build would generat libraries of the format
> libboost_NAME_vc1410-OPTIONS-1_64.lib
> config would auto-link libraries of the same format
> 
> 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".
> 
> build bootstrap would use bootstrap.bat vc141
> build of source would use b2 toolset=msvc-14.1
> build would generat libraries of the format
> libboost_NAME_vc141-OPTIONS-1_64.lib
> config would auto-link libraries of the same format
> 
> Option 3 - 15.0 Use the visual studio version. The $(VisualStudioVersion)
> macro is "15.0". In VS2015 this was "14.0".
> 
> build bootstrap would use bootstrap.bat vc15
> build of source would use b2 toolset=msvc-15.0
> build would generat libraries of the format
> libboost_NAME_vc150-OPTIONS-1_64.lib
> config would auto-link libraries of the same format

I don't care about the command-line option name, but I'm somewhat relying on
the library name containing $(PlatformToolsetVersion). So of those three
options, I would vote for option 2.

--
View this message in context: http://boost.2283326.n4.nabble.com/Re-boost-release-1-64-0-Delayed-because-of-Microsoft-version-numbers-tp4692570p4692634.html
Sent from the Boost - Build mailing list archive at Nabble.com.