package/meson: determine g-ir-scanner and g-ir-compiler paths from pkgconfig
authorAdam Duskett <Aduskett@gmail.com>
Sun, 15 Mar 2020 15:33:21 +0000 (16:33 +0100)
committerYann E. MORIN <yann.morin.1998@free.fr>
Sun, 15 Mar 2020 16:37:32 +0000 (17:37 +0100)
commit8b0aeafce2a22913e6a44818227f6a39e3225157
tree9527569c7a7c5fb1be55b000e0c4816fa6d9be9b
parent3ff152386a857de9baf55eaccb1afdb0d81484bf
package/meson: determine g-ir-scanner and g-ir-compiler paths from pkgconfig

Currently, meson hard codes the paths of these binaries which results in
cross-compiled environments to run the host versions of these tools.
However, GObject-introspection provides the appropriate paths to these
utilities via pkg-config

find_program is needed in the case g-i is built as a subproject. If
g-ir-scanner or g-ir-compiler are in the build or source directory use those.
If they aren't found in the source directory, use the results from pkg-config.

Backport two upstream commits to fix the issue.

Signed-off-by: Adam Duskett <Aduskett@gmail.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Tested-by: Adam Duskett <aduskett@gmail.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
package/meson/0004-gobject-introspection-determine-g-ir-scanner-and-g-i.patch [new file with mode: 0644]
package/meson/0005-mesonbuild-modules-gnome.py-Fix-giscanner-and-gicomp.patch [new file with mode: 0644]