Subject: Re: [boost] Boost 1.61.0 Beta 1 Release Candidate 1
From: Tom Kent (lists_at_[hidden])
Date: 2016-03-20 08:35:06
On Sat, Mar 19, 2016 at 2:38 PM, Vladimir Prus <vladimir.prus_at_[hidden]>
> Release candidates for 1.61.0 beta 1 are now available:
> 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.
> These packages were generated by the CI system that Rene has put together,
> and one user-visible change is that the directory inside archive is
> named after git commit hash. This will be changed for the final release.
> Otherwise, these were smoke-tested on Windows and Linux, and should be
> functionally identical to usual packages.
I'd like to request that we roll a 1_61_0_b2 without this change. The
directory structure is a big part of what we need to verify and this throws
off the build system that I've had running.
Other than that, everything seems to work correctly:
toolset arch compile Link Execute
msvc-8.0 32 X X X
msvc-8.0 64 X X X
msvc-9.0 32 X X X
msvc-9.0 64 X X X
msvc-10.0 32 X X X
msvc-10.0 64 X X X
msvc-11.0 32 X X X
msvc-11.0 64 X X X
msvc-12.0 32 X X X
msvc-12.0 64 X X X
msvc-14.0 32 X X X
msvc-14.0 64 X X X
Compile means that the b2 command completed without errors
Install means that the installers for the respective version were generated
Link means that visual studio was able to link a sample executable to a
library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated
Execute means that the linked program executed without errors.