Run ./configure --with-spice-common to use spice-common sources from spice-common package, instead of source in spice/common/ directory.
This is usefull when building the spice client or spice server out of a "distribution" tarball, when ../common directory does not exist. --- configure.ac.shared | 15 +++++++++++++++ 1 files changed, 15 insertions(+), 0 deletions(-) diff --git a/configure.ac.shared b/configure.ac.shared index 0cb9859..52b7167 100644 --- a/configure.ac.shared +++ b/configure.ac.shared @@ -165,6 +165,21 @@ AC_ARG_ENABLE(static-linkage, AC_SUBST([SPICEC_STATIC_LINKAGE_BSTATIC]) AC_SUBST([SPICEC_STATIC_LINKAGE_BDYNAMIC]) +# +# Upon user request (./configure --with-spice-common) to use spice-common package +# Then check for spice-common package, and overwrite SPICE_COMMON_SRCDIR +# (with a directory specified in spice-common.pc). +# +AC_ARG_WITH(spice-common, + [AS_HELP_STRING([--with-spice-common], + [use sources found by spice-common.pc (default is no)])], + [use_spice_common=$withval], + [use_spice_common=no]) + +if test "x$use_spice_common" != "xno"; then + PKG_CHECK_MODULES(SPICE_COMMON, spice-common = 0.4.1) + SPICE_COMMON_SRCDIR=$(pkg-config --variable=common_src_dir spice-common) +fi dnl =========================================================================== dnl check compiler flags -- 1.6.5.2 ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Spice-space-devel mailing list Spice-space-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spice-space-devel
