Subject: Re: [boost] [release] Boost 1.69.0 Beta 1 Release Candidate 2
From: degski (degski_at_[hidden])
Date: 2018-11-16 06:05:19
On Thu, 15 Nov 2018 at 20:48, Marshall Clow <mclow.lists_at_[hidden]> wrote:
> On Wed, Nov 14, 2018 at 11:12 PM degski <degski_at_[hidden]> wrote:
>> On Thu, 15 Nov 2018 at 00:50, Marshall Clow via Boost <
>> boost_at_[hidden]> wrote:
>>> The release candidates for the second 1.69.0 beta release are now
>>> The release notes are not yet final.
>>> The SHA256 checksums are as follows:
>>> As always, the release managers would appreciate it if you download
>>> the candidate of your choice and give building it a try. Please report
>>> both success and failure, and anything else that is noteworthy.
>> I have tried to build with VC-15.9 (yesterday's update) and I hit the
>> don't know how to make <p/C:/boost>C:\Program Files (x86)\Microsoft
>> <pc:\boost-build\boost\bin.v2\standalone\msvc\msvc-15.9>msvc-setup.read for
>> lack of <p/C:/boost>C:\Program Files (x86)\Microsoft Visual
>> common.mkdir c:\boost-build\boost
>> after which everything fails of course, which is unsurprising as
>> vcvarsall.bat is now located at "C:\Program Files (x86)\Microsoft Visual
>> I don't know why, how or what, but that's what I see. b2 builds, but
>> that's because I'm building from a dev-prompt.
> Short answer - I don't care about this for the beta. (since the MSVC
> update happened yesterday), but it ought to be fixed for the 1.69.0 release.
I understand [that you don't care about something that happened the day
before]. Would indeed be nice to have it fixed, 15.9 is quite an update and
from what I understood from STL on reddit, the base for VC-16 (VS2019).
-- *âIf something cannot go on forever, it will stop" - Herbert Stein*