summaryrefslogtreecommitdiff
path: root/gio-2.0.pc.in
diff options
context:
space:
mode:
authorKalev Lember <kalevlember@gmail.com>2012-04-11 16:41:48 +0300
committerKalev Lember <kalevlember@gmail.com>2012-04-11 20:01:44 +0300
commit47692845c0a062a76f99b5de125c5eafa4556847 (patch)
treed0d6ba4dadca5e17df41676c4b0d4f50d504175f /gio-2.0.pc.in
parent5739d896f8d3bf9883d4f5e4b7553a617a1c751a (diff)
gio-2.0.pc: Avoid full path to executables
Instead of using full path in glib_compile_schemas and glib_compile_resources variables, rely on having the executables in PATH. This fixes the cross-compiling case where we cannot execute the binaries for target system. Instead of executing the target system's binaries, we need to use the native versions installed on the build host. The easiest way to find the native executables is to just pick them up from PATH. In addition, this brings gio-2.0.pc in line with glib-2.0.pc -- the latter has historically only listed the executable name and not the full path. https://bugzilla.gnome.org/show_bug.cgi?id=673911
Diffstat (limited to 'gio-2.0.pc.in')
-rw-r--r--gio-2.0.pc.in6
1 files changed, 3 insertions, 3 deletions
diff --git a/gio-2.0.pc.in b/gio-2.0.pc.in
index 8dac83838..9f7123f93 100644
--- a/gio-2.0.pc.in
+++ b/gio-2.0.pc.in
@@ -4,9 +4,9 @@ libdir=@libdir@
includedir=@includedir@
giomoduledir=@GIO_MODULE_DIR@
-glib_compile_schemas=@bindir@/glib-compile-schemas@EXEEXT@
-glib_compile_resources=@bindir@/glib-compile-resources@EXEEXT@
-gdbus_codegen=@bindir@/gdbus-codegen
+glib_compile_schemas=glib-compile-schemas
+glib_compile_resources=glib-compile-resources
+gdbus_codegen=gdbus-codegen
Name: GIO
Description: glib I/O library