Re: [release] Boost 1.85.0 Release Candidate 3 is available

From: Tom Kent (lists_at_[hidden])
Date: 2024-04-12 00:28:21

On Thu, Apr 11, 2024 at 4:31 PM Marshall Clow via Boost <
boost_at_[hidden]> wrote:

> The third release candidates for the 1.85.0 release are now available at:
> <https://boostorg.jfrog.io/artifactory/main/release/1.85.0/source/>
>
> The SHA256 checksums are as follows:
>
> e712fe7eb1b9ec37ac25102525412fb4d74e638996443944025791f48f29408a
> boost_1_85_0_rc3.zip
> 7009fe1faa1697476bdc7027703a2badb84e849b7b0baad5086b087b971f8617
> boost_1_85_0_rc3.tar.bz2
> 16d16b9658753117c1434e5450c5eac194957f4b6d0b390b9d07900d37c115a4
> boost_1_85_0_rc3.7z
> be0d91732d5b0cc6fbb275c7939974457e79b54d6f07ce2e3dfdd68bef883b0b
> boost_1_85_0_rc3.tar.gz
>
> The changes from RC1 are:
>
> * Boost.ASIO docs generate very long file names that are not usable on
> Windows.
> * Boost.Program options does not build in C++23 mode on clang truck (to be
> clang 19 before boost 1.86.0 is released)
>         Note: It is possible that this is a bug in clang, and it’s in a
> clang that is not released yet.
> * Boost.Log has some broken links in its documentation.
> * A meaningless change to Boost.Array (add a space to a test file)
>
> Apparently the RC2 tarballs were mis-buiilt; some of them were missing the
> required changes.
> I believe that RC3 resolves that problem.
>
> 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.
>
> -- The Release managers
>

Third time's the charm! Looks good on windows/visual studio.

toolset     arch    compile Link    Execute
msvc-14.0   32      X       X       X
msvc-14.0   64      X       X       X
msvc-14.1   32      X       X       X
msvc-14.1   64      X       X       X
msvc-14.2   32      X       X       X
msvc-14.2   64      X       X       X
msvc-14.3   32      X       X       X
msvc-14.3   64      X       X       X

Compile means that the b2 command completed without errors
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.

Full build logs here:
https://gist.github.com/teeks99/2cd4744cdff04ae73a4d611ad9972d30

Tom