From: Michael Orlitzky <michael@orlitzky.com>
Date: Sat, 5 Aug 2023 16:10:11 +0000 (-0400)
Subject: configure.ac: hack around "make distcheck" failure.
X-Git-Tag: 0.0.1~27
X-Git-Url: https://gitweb.michael.orlitzky.com/?a=commitdiff_plain;h=8344b5875279c0b4b829f077ecab6fc5f005e7b7;p=libsvgtiny-pixbuf.git

configure.ac: hack around "make distcheck" failure.
---

diff --git a/configure.ac b/configure.ac
index d2e4f93..0e6978d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -12,7 +12,17 @@ PKG_CHECK_MODULES([GTK4], [gtk4])
 PKG_CHECK_MODULES([LIBSVGTINY], [libsvgtiny])
 
 AC_MSG_CHECKING([for gdk-pixbuf module location])
-gdk_pixbuf_moduledir=$($PKG_CONFIG --variable gdk_pixbuf_moduledir gdk-pixbuf-2.0)
+# Hack alert: we need to install our module into this specific
+# location... BUT, we also want to respect --prefix, at least to the
+# extent that we won't try to install something to, say, /usr when
+# we've passed --prefix=/tmp. This little libdir trick prevents
+# pkg-config from substituting for ${libdir} where it appears in the
+# *.pc file. When we go to actually use gdk_pixbuf_moduledir, the
+# variable ${libdir} will be valid in our own build system, and will
+# respect the prefix. This means that if you configure this package
+# with a different prefix than gdk-pixbuf was, it won't install
+# correctly. But hey, make distcheck works?
+gdk_pixbuf_moduledir=$($PKG_CONFIG --define-variable=libdir="\${libdir}" --variable gdk_pixbuf_moduledir gdk-pixbuf-2.0)
 AC_MSG_RESULT([$gdk_pixbuf_moduledir])
 AC_SUBST([gdk_pixbuf_moduledir])