From: Eduardo Habkost <ehabkost@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Danilo C. L. de Paula" <ddepaula@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: Support --enable-capstone=internal
Date: Tue, 11 Sep 2018 12:31:05 -0300 [thread overview]
Message-ID: <20180911153105.GL12698@habkost.net> (raw)
In-Reply-To: <0dd0910c-6120-a485-e0b0-c354bd4038cd@linaro.org>
On Tue, Sep 11, 2018 at 07:33:08AM -0700, Richard Henderson wrote:
> On 09/05/2018 08:19 AM, Eduardo Habkost wrote:
> > Currently there's no way to make configure not try to use the
> > system-provided capstone library using pkgconfig.
>
> Certainly there is.
>
> >
> > Add support to --enable-capstone=internal option to make QEMU not
> > use the system-provided library automatically.
Oops, the commit message is inaccurate: we can prevent
./configure from trying the system library, but there's no way to
make it avoid using git submodule at the same time.
> >
> > 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[=LOCATION]
> > + Where to look for capstone library.
> > + Supported options: internal, git, system
>
> That's what "git" means here.
"git" makes ./configure add capstone to GIT_SUBMODULES, and I'm
pretty sure we don't want that if we're not building from a git
tree.
--
Eduardo
prev parent reply other threads:[~2018-09-11 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 15:19 [Qemu-devel] [PATCH] configure: Support --enable-capstone=internal Eduardo Habkost
2018-09-11 14:33 ` Richard Henderson
2018-09-11 15:31 ` Eduardo Habkost [this message]
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=20180911153105.GL12698@habkost.net \
--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).