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

Subject: Re: [boost] [release] 1.64.0 Delayed because of Microsoft (version numbers)
From: Tom Kent (lists_at_[hidden])
Date: 2017-03-19 12:55:49

On Fri, Mar 17, 2017 at 1:08 PM, John Maddock via Boost <
boost_at_[hidden]> wrote:

>
>
> On 17/03/2017 15:12, Rene Rivera via Boost wrote:
>
>> Sorry to say the beta release of 1.64.0 is hereby going to be delayed for
>> at least another week. The confusion of VS2017 version numbers and the
>> communities inability to address this issue after the beta is to blame.
>>
>> To address the situation the beta release will be published when one of
>> the
>> two tasks below are completed:
>>
>> (A) Boost Config changes to use 1410 as the autolink version to match what
>> the currently working generated libs are taggeg with.
>>
>
> I've cherry picked the relevant commits to master and pushed those - so
> Config and Build are consistent now.
>

I don't think this happened...it looks like master auto_link.hpp is using
vc141 not vc1410. Develop looks like it matches what build is doing.

https://github.com/boostorg/config/blob/master/include/boost/config/auto_link.hpp#L172

IMO this is still blocking beta.

>
> However, IMO the name used is just plain wrong - note that both Peter
> Dimov and myself have both typed in the "wrong" name by mistake *even when
> we know what the "right" name is*.  Worse, if you do type in
> toolset=msvc-14.1 by mistake, something (not sure what) still happens and
> libraries with a "141" suffix are generated, IMO we need to fix that before
> release, though not necessarily before beta.
>

I agree. Most users won't even know to try 14.?? to use VS 2017, because MS
clearly labels it everwhere as "15", but it is definitely more correct for
us to match MS's c++ tools than the visual studio version. Anyway, once
users figure that out, they'll be much more likely to use 14.1 vs.
14.10...there was no 14.2, 14.3, 14.9 etc!