From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Danilo C. L. de Paula" <ddepaula@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: [Qemu-devel] [PATCH] configure: Support --enable-capstone=internal
Date: Wed, 5 Sep 2018 12:19:27 -0300 [thread overview]
Message-ID: <20180905151927.8884-1-ehabkost@redhat.com> (raw)
Currently there's no way to make configure not try to use the
system-provided capstone library using pkgconfig.
Add support to --enable-capstone=internal option to make QEMU not
use the system-provided library automatically.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
configure | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/configure b/configure
index 58862d2ae8..34ed00f6d9 100755
--- a/configure
+++ b/configure
@@ -1431,6 +1431,8 @@ for opt do
;;
--enable-capstone=system) capstone="system"
;;
+ --enable-capstone=internal) capstone="internal"
+ ;;
--with-git=*) git="$optarg"
;;
--enable-git-update) git_update=yes
@@ -1635,6 +1637,9 @@ Advanced options (experts only):
xen pv domain builder
--enable-debug-stack-usage
track the maximum stack usage of stacks created by qemu_alloc_stack
+ --enable-capstone[=LOCATION]
+ Where to look for capstone library.
+ Supported options: internal, git, system
Optional features, enabled with --enable-FEATURE and
disabled with --disable-FEATURE, default is enabled if available:
--
2.18.0.rc1.1.g3f1ff2140
next reply other threads:[~2018-09-05 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 15:19 Eduardo Habkost [this message]
2018-09-11 14:33 ` [Qemu-devel] [PATCH] configure: Support --enable-capstone=internal Richard Henderson
2018-09-11 15:31 ` Eduardo Habkost
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=20180905151927.8884-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=ddepaula@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).