Trouble with new lo-build

Christian Lohmaier lohmaier at googlemail.com
Wed Jul 2 11:14:54 UTC 2025


Hi Jürgen, *,

On Tue, Jul 1, 2025 at 4:10 PM Juergen Funk <j-funk at outlook.de> wrote:
>
> Thanks for the hint, my next question is,
> why the pkgconf of cygwin doesn't work (compiler error) even though it's the same version number, I've added in the LibreOffice build documentation for the hard way that.

answered that in the other mail. pkgconf on windows is only used for
meson, and meson needs windows paths, hence the need for a windows
version of pkg-config/pkgconf - and from the two pkgconf doesn't have
external dependencies/is easy to build also for mac, where pkgconf is
also only used for meson.
If meson would also accept values FOO_CFLAGS and similar to bypass
running pkgconfig, then this wouldn't be a problem. But meson insists
on running pkgconfig but also insists on windows-style-paths/cannot
deal with unix-style paths on windows.

> But I did not install the meson 1.7.2, but it compile/link, this confuses me, why install LODE, this library although it goes without, is it necessary for the hard way docu?

Also touched on that in the other mail. The idea was for users to
install meson and use that, but people just cannot follow
instructions, ignored configure's error messages and warnings.
There's the additional complication about meson calls other python
scripts as build-commands and how enable-python=fully-internal should
behave (from my POV) - some distros install meson in a way that it
cannot be run with "python3.x /path/to/meson" and that did further
complicate things, lead to adding pointless workarounds.
To get rid of all that meson was added as an external and is used if
the user doesn't override it by specifying MESON=/path/to/mesontouse

ciao
Christian


More information about the LibreOffice mailing list