> On Nov 4, 2026, at 11:51 PM, petko.apache.org via dev
> <[email protected]> wrote:
>
>
> Am 05.11.2026 um 05:16 schrieb Pedro F. Giffuni via dev:
>> Hi;
>> Ah well ... I started a small update to our jpeg
>> support:https://github.com/pgiffuni/openoffice/tree/libjpeg-turbo
>> Unfortunately with those patches I now get a complaint that sinc_pi, which
>> we use from boost requires C++14. Why it doesn't complain now? Who knows, we
>> have a mess mixing very old language features and Boost doesn't help.
>> So I am working on a patch that fixes all the deprecated C++ warning issues
>> reported by clang/libc++; the patch is currently 2.7M and growing. I will
>> create a new branch as soon as I get something that compiles. After that I
>> will try to reduce a bit the Boost footprint as well. This is not meant for
>> 5.0.
>> Concerning future roadmap: we need color
>> management.https://littlecms.com/tags/lcms2/
>> Oh and I installed CLion (free for Apache devs) with bazel support but I
>> can't figure out how to build AOO.
>
> The bazel-migration is still ongoing and not complete. rhino and beanshell
> are not migrated. it builds only en-US at this point and installers are not
> ready yet. Still windows only.
>
What is the overall impact of the bazel migration? Is it required for all other
platforms as well? Does it increase the floor for Linux, FreeBSD, macOS, etc.
How solid and reliable is the migration? Does it require major updates of other
dependencies? Is it intended to replace the entire build system?
--
Jim
"This is an outrage!"
Tony Harrison
