On Mon, 03 Aug 2020 at 13:09:55 +0100, Simon McVittie wrote:
> I've confirmed that this succeeds in a pure bullseye chroot and fails if
> I upgrade meson (only) to the version from unstable. I'm not completely
> sure whether this is a straightforward regression in meson, or whether
> libpeas is holding it wrong.
>
> It seems that what is meant to happen here is that the libpeas build
> system builds tests/libpeas/introspection/*.[ch] into a shared library,
> introspects them, and uses the generated introspection data during the
> build-time tests.
>
> With meson 0.54.3-1, I get:
>
> obj-x86_64-linux-gnu/tests/libpeas/introspection/Introspection-1.0.typelib
> obj-x86_64-linux-gnu/tests/libpeas/introspection/Introspection-1.0.gir
>
> With 0.55.0-2, the introspection data (typelib and GIR XML) isn't generated.
Bisection says this regressed in b1e3440e "ninjabackend: Treat GNOME
gir/typelib as libraries" - or maybe it's a pre-existing bug in libpeas
exposed by that commit, it isn't clear to me which.
smcv
