From: Carlo Marcelo Arenas Belon <carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [RFC] modular dependencies for kvm's qemu
Date: Tue, 16 Oct 2007 04:22:14 -0500 [thread overview]
Message-ID: <20071016092214.GA13850@tapir> (raw)
Greetings,
kvm's configure calls qemu's configure with --enable-alsa, making the
existence and use of alsa a dependency; with the import of the latest CVS
qemu, a similar implicit dependency has been added for gnutls (required for
TLS support for qemu's vnc server).
the following proposed patch (which is a combined patch from a 2 patch series)
allows kvm's configure to enable alsa or disable vnc tls conditionally.
I am curious if the approach taken for alsa (which is the one that fits what
qemu's configure allows for this case) is acceptable or not, as it will change
the dependency on alsa from being required by default to optional and unless
--enable-alsa is used.
Carlo
---
--- kvm-46/configure 2007-10-09 11:43:12.000000000 -0700
+++ kvm-46/configure 2007-10-16 01:40:32.000000000 -0700
@@ -16,6 +16,8 @@
--with-patched-kernel don't use external module
--kerneldir=DIR kernel build directory ($kerneldir)
--qemu-cc="$qemu_cc" compiler for qemu (needs gcc3.x) ($qemu_cc)
+ --enable-alsa enable alsa support for qemu
+ --disable-vnc-tls disable vnc tls support for qemu
--disable-gcc-check don't insist on gcc-3.x
- this will break running without kvm
EOF
@@ -50,6 +52,12 @@
--qemu-cc)
qemu_cc="$arg"
;;
+ --enable-alsa)
+ enable_alsa=1
+ ;;
+ --disable-vnc-tls)
+ disable_vnc_tls=1
+ ;;
--disable-gcc-check)
disable_gcc_check=1
;;
@@ -85,7 +93,8 @@
--disable-kqemu --extra-cflags="-I $PWD/../user" \
--extra-ldflags="-L $PWD/../user" \
--enable-kvm --kernel-path="$libkvm_kerneldir" \
- --enable-alsa \
+ ${enable_alsa:+"--enable-alsa"} \
+ ${disable_vnc_tls:+"--disable-vnc-tls"} \
${disable_gcc_check:+"--disable-gcc-check"} \
--prefix="$prefix"
)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-10-16 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 9:22 Carlo Marcelo Arenas Belon [this message]
2007-10-16 10:38 ` [RFC] modular dependencies for kvm's qemu Avi Kivity
2007-10-16 13:39 ` Daniel P. Berrange
[not found] ` <20071016133930.GB2107-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-10-16 14:21 ` Carlo Marcelo Arenas Belon
2007-10-16 14:20 ` Avi Kivity
[not found] ` <4714C8B5.60104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-16 14:54 ` Anthony Liguori
2007-10-16 15:36 ` Carlo Marcelo Arenas Belon
2007-10-16 15:34 ` Avi Kivity
2007-10-16 15:48 ` Anthony Liguori
2007-10-17 14:43 ` Carlo Marcelo Arenas Belon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071016092214.GA13850@tapir \
--to=carenas-kledwsohozojb6fo7hg9ng@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox