Re: icu update to 77.1

[Greg Troxel <gdt%lexort.com@localhost>]

Thomas Klausner <wiz%NetBSD.org@localhost> writes:

> On Fri, Apr 04, 2025 at 07:28:57AM +0200, Martin Husemann wrote:
>> On Thu, Apr 03, 2025 at 09:44:33PM +0200, Thomas Klausner wrote:
>> > The previous version was already marked as needing C++17, so no
>> > change.
>> 
>> Yes, but the compile errors you quoted come from g++ invocations using
>> older standards.
>> 
>> And one *could* make a distinction between the library needing C++$something
>> to build and the API in the public headers requiring C++$somethingelse.
>
> I tried two things:
>
> - Setting USE_CXX_FEATURES+=c++17 in icu/buildlink3.mk - with the same
>   bulk build result, since qt5-qtwebkit uses -std=c++11
>
> - Setting USE_CXX_FEATURES+=c++17 and FORCE_CXX_STD=c++17 directly in
>   qt5-qtwebkit, which lead to it failing differently.

So that means

  icu (newly?) requires --std=c++17 (perhaps implicitly) to process
  headers?

  qt5-qtwebkit requires -std=c++11 to build

and

  nobody is going to think it reasonable to fix icu to permit using the
  headers with only c++11 (even though as a library they should!)

  nobody is doing any kind of maintenance on qt5-qtwebkit

Is that how it is?


What if in icu bl3, instead of USE_CXX_FEATURES+=c++17, it is c++11?
Or does icu document and truly require c++17 for header use (martin's
2nd question)?