8b0aeafce2
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> |
||
---|---|---|
.. | ||
0001-Only-fix-RPATH-if-install_rpath-is-not-empty.patch | ||
0002-Prefer-ext-static-libs-when-default-library-static.patch | ||
0003-envconfig-add-pkg_config_libdir-property.patch | ||
0004-gobject-introspection-determine-g-ir-scanner-and-g-i.patch | ||
0005-mesonbuild-modules-gnome.py-Fix-giscanner-and-gicomp.patch | ||
cross-compilation.conf.in | ||
meson.hash | ||
meson.mk |