|
Boost : |
From: Marshall Clow (mclow.lists_at_[hidden])
Date: 2024-04-06 01:52:40
> On Apr 5, 2024, at 6:54â¯PM, Nigel Stewart via Boost <boost_at_[hidden]> wrote:
>
> Hello Marshall,
>
> I'm not sure if this is the right place to mention a minor 1.85.0 issue, if
> not apologies.
This is exactly the right place to mention this.
Thanks!
â Marshall
>
> There is a deprecation of an error_code alias in boost::json that breaks
> our builds.
> The migration is doable for us, but perhaps worth mentioning as a change in
> the
> release notes.
>
> https://github.com/boostorg/json/pull/980
>
> Aside from that our builds and tests are looking fine with the 1.85.0 beta.
> Thanks!
>
> Best regards,
>
> Nigel Stewartt
>
> On Sat, Apr 6, 2024 at 2:35â¯AM Mohammad Nejati [ashtum] via Boost <
> boost_at_[hidden]> wrote:
>
>>> Beast appears to have some documentation that is far too long for windows
>> to support working with. The maximum path length for anything on windows is
>> 260 chars. This file name is already 231 chars
>>
>> Thanks for reporting this. It seems that Beast CI doesn't build
>> documentation on Windows platforms, and we hadn't noticed the issue.
>> I'm already working on a fix.
>>
>> On Fri, Apr 5, 2024 at 7:10â¯PM Tom Kent via Boost <boost_at_[hidden]>
>> wrote:
>>>
>>> On Fri, Apr 5, 2024 at 1:31â¯PM Marshall Clow via Boost <
>>> boost_at_[hidden]> wrote:
>>>
>>>> The first 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:
>>>>
>>>> de84c538aaadf2388362e006d73d0be783541288d87a9ef68e906995efc2148d
>>>> boost_1_85_0_rc1.tar.gz
>>>> dd8baccd0b5ca534ad3717a07b426391fe6d49b6b84bf07d10e72792a5d1ba10
>>>> boost_1_85_0_rc1.7z
>>>> 289ab7784b9297e13938876f698ced91f734f9a80f91099d35803b78d15c0210
>>>> boost_1_85_0_rc1.tar.bz2
>>>> 84c35ef72efde30725de7bca8ccf399cd8d205a0d5b249465cf86c818291b7b7
>>>> boost_1_85_0_rc1.zip
>>>>
>>>>
>>>> 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
>>>>
>>>
>>> This contains a serious failure on windows that wasn't present in the
>> beta.
>>>
>>> Beast appears to have some documentation that is far too long for windows
>>> to support working with. The maximum path length for anything on windows
>> is
>>> 260 chars. This file name is already 231 chars:
>>>
>> boost__asio__traits__query_static_constexpr_member_lt__beast__test__immediate_executor_comma__Property_comma__typename_enable_if_lt__std__is_convertible_lt__Property_comma__execution__blocking_t__gt___value__gt___type__gt_.html
>>>
>>> With the minimum possible length to the boost directory (drive letter
>> plus
>>> a single character where it would be more reasonable to have something
>> like
>>> D:\boost_1_85_0), we're already at 263 characters.
>>>
>> D:\b/libs\beast\doc\html\beast\ref\boost__asio__traits__query_static_constexpr_member_lt__beast__test__immediate_executor_comma__Property_comma__typename_enable_if_lt__std__is_convertible_lt__Property_comma__execution__blocking_t__gt___value__gt___type__gt_.html
>>>
>>> It is true that for some programs, the windows path length limit can be
>>> disabled, but there are many tools that this doesn't work for, so it
>> needs
>>> to be fixed before this release can go out.
>>>
>>> Tom
>>>
>>> _______________________________________________
>>> Unsubscribe & other changes:
>> http://lists.boost.org/mailman/listinfo.cgi/boost
>>
>> _______________________________________________
>> Unsubscribe & other changes:
>> http://lists.boost.org/mailman/listinfo.cgi/boost
>>
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk