Skip to content

Use absolute paths in pkg-config files

Jonas Witschel requested to merge diabonas/glib:fix-pkg-config-autotools into master

As discussed in #1521 (closed), the pkg-config files differ between the Autotools and the Meson build: the latter uses absolute paths in variables (e.g. gdbus_codegen=${bindir}/gdbus-codegen), while the former only provides the executable name (e.g. gdbus_codegen=gdbus-codegen). This merge request fixes the Autotools build to use absolute paths as well.

Note that this is a minimal merge request that only consolidates the variables between the two build systems. The pkg-config also specify different dependencies, e.g. gio-2.0.pc on Autotools has

Requires.private: gmodule-no-export-2.0
Libs.private: -lz  -lresolv  -lselinux   -lmount
Cflags:

while on Meson it is

Requires.private: gmodule-no-export-2.0, zlib, mount >= 2.23, libselinux
Libs.private: -pthread -L${libdir} -lxdgmime -linotify -ldl -pthread -lresolv
Cflags: -I${includedir}

Similar differences exist for the other .pc files. I am not sure whether it is possible to just take the values from Meson without breaking something, so I left the dependencies alone for now. If I get confirmation that this is not a problem, I can merge the changes from Meson to Autotools as well so that the pkg-config files are identical.

Merge request reports