From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/4] .travis.yml: reduce target list on core configure tweaks
Date: Mon, 18 Apr 2016 10:50:55 +0100 [thread overview]
Message-ID: <87k2jvw8hs.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA_bnaqsJPsoZP=FfRj9MYq0YtiX3BDqUJRnvYx76oTKvA@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 18 April 2016 at 10:15, Alex Bennée <alex.bennee@linaro.org> wrote:
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>> The wildcarding gives you a configure command that will
>>> potentially change behaviour as we introduce new targets,
>>> too; that makes me a bit nervous.
>>
>> Well it doesn't stop you using the full names but I take your point.
>> What about a different selection flag for selecting by backends?
>
> Am I right in guessing that the reason you don't want to just
> say --target-list=arm-softmmu,arm-linux-user is that that won't
> work on non-Linux hosts?
Not really. The main use case is for ppc and mips targets which have
lots of variant builds for all the various sizes and endianess.
>
> thanks
> -- PMM
--
Alex Bennée
next prev parent reply other threads:[~2016-04-18 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 15:56 [Qemu-devel] [PATCH 0/4] Current Travis queue Alex Bennée
2016-04-15 15:56 ` [Qemu-devel] [PATCH 1/4] ./configure: accept stems to match a range of targets Alex Bennée
2016-04-15 15:56 ` [Qemu-devel] [PATCH 2/4] .travis.yml: reduce target list on core configure tweaks Alex Bennée
2016-04-15 16:07 ` Peter Maydell
2016-04-18 9:15 ` Alex Bennée
2016-04-18 9:17 ` Peter Maydell
2016-04-18 9:50 ` Alex Bennée [this message]
2016-04-15 15:57 ` [Qemu-devel] [PATCH 3/4] .travis.yml: add libnfs-dev for NFS block driver Alex Bennée
2016-04-15 15:57 ` [Qemu-devel] [PATCH 4/4] .travis.yml: add trusty GCE target Alex Bennée
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=87k2jvw8hs.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.