summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPavel Grunt <pgrunt@redhat.com>2015-06-29 10:58:40 +0200
committerPavel Grunt <pgrunt@redhat.com>2015-07-29 17:10:41 +0200
commitf33c49f72de45c7143fcb80415e0d33be4843e89 (patch)
tree11c5e27bdef6b80aa3499892661100c518ab3ddb
parent0d81ec2ef8a69fbe93de15d6125ae40d3b2bd7be (diff)
downloadvirt-viewer-f33c49f72de45c7143fcb80415e0d33be4843e89.tar.gz
virt-viewer-f33c49f72de45c7143fcb80415e0d33be4843e89.tar.xz
virt-viewer-f33c49f72de45c7143fcb80415e0d33be4843e89.zip
configure: Enable spice-gtk when have all necessary spice packages
When neither --with-spice-gtk=yes nor --with-spice-gtk=no is used, spice-gtk is supposed to be automatically enabled/disabled depending on its availability. However, this is not perfectly working as once spice-gtk has been detected as available, configure will fail if spice-protocol or spice-controller are too old. In this case, spice-gtk support should just be disabled rather than configure failing
-rw-r--r--configure.ac3
1 files changed, 2 insertions, 1 deletions
diff --git a/configure.ac b/configure.ac
index 3399129..df0053d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -180,7 +180,8 @@ AC_ARG_WITH([spice-gtk],
AS_IF([test "x$with_spice_gtk" != "xno"],
[PKG_CHECK_MODULES(SPICE_GTK,
- [spice-client-gtk-$SPICE_GTK_API_VERSION >= $SPICE_GTK_REQUIRED],
+ [spice-client-gtk-$SPICE_GTK_API_VERSION >= $SPICE_GTK_REQUIRED
+ spice-controller spice-protocol >= $SPICE_PROTOCOL_REQUIRED],
[have_spice_gtk=yes], [have_spice_gtk=no])],
[have_spice_gtk=no])