qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: Support --target-list=? to list available targets
Date: Thu, 21 Apr 2011 19:45:12 +0200	[thread overview]
Message-ID: <4DB06D28.1040007@mail.berlios.de> (raw)
In-Reply-To: <1303391455-5289-1-git-send-email-peter.maydell@linaro.org>

Am 21.04.2011 15:10, schrieb Peter Maydell:
> Add support for getting configure to print the list of all targets
> that can be built, via the option '--target-list=?'.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> Yes, you can get the list of targets by running configure without
> any arguments and then scrolling up to find the target list in
> the screenful of output, but I think this is a bit more user-friendly.
>
> configure | 36 ++++++++++++++++++++++--------------
> 1 files changed, 22 insertions(+), 14 deletions(-)

The qemu executable supports this use pattern (-cpu ?),
but it's unusual for configure.

Other options (--audio-drv-list=LIST, --audio-card-list=LIST)
show the available values in the help message (configure --help).

What about a similar help text for --target-list? Like this:

   --target-list=LIST       set target list []
                            Available targets: i386-softmmu ...
                            i386-linux-user ...

Users would not have to call configure twice to get the list of
available targets (the first call is configure --help because
they don't know whether it is --target, --targets, --targetlist
or --target-list).

  reply	other threads:[~2011-04-21 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 13:10 [Qemu-devel] [PATCH] configure: Support --target-list=? to list available targets Peter Maydell
2011-04-21 17:45 ` Stefan Weil [this message]
2011-04-22  0:50   ` Peter Maydell

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=4DB06D28.1040007@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --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 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).