From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [PATCH 0/3] Use meson_options.txt in the configure script
Date: Sun, 29 Aug 2021 19:32:07 +0200 [thread overview]
Message-ID: <20210829173210.39562-1-thuth@redhat.com> (raw)
It's cumbersome to maintain the build options twice, one time in the
configure script and one time in meson_options.txt. Thus let's add some
logic to the configure script to look at the meson_options.txt file
instead of handling every option twice.
Thomas Huth (3):
configure: Add the possibility to read options from meson_options.txt
configure: Remove options that can be handled via meson_options.txt
instead
configure: Get help text from meson_options.txt
configure | 429 ++++++----------------------------------------
meson_options.txt | 2 +-
2 files changed, 53 insertions(+), 378 deletions(-)
--
2.27.0
next reply other threads:[~2021-08-29 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 17:32 Thomas Huth [this message]
2021-08-29 17:32 ` [PATCH 1/3] configure: Add the possibility to read options from meson_options.txt Thomas Huth
2021-08-30 14:47 ` Eric Blake
2021-08-29 17:32 ` [PATCH 2/3] configure: Remove options that can be handled via meson_options.txt instead Thomas Huth
2021-08-30 15:06 ` Eric Blake
2021-08-30 15:33 ` Richard Henderson
2021-08-30 16:33 ` Thomas Huth
2021-08-29 17:32 ` [PATCH 3/3] configure: Get help text from meson_options.txt Thomas Huth
2021-08-30 15:30 ` Eric Blake
2021-08-30 16:48 ` Thomas Huth
2021-08-29 21:22 ` [PATCH 0/3] Use meson_options.txt in the configure script Marc-André Lureau
2021-08-30 5:11 ` Thomas Huth
2021-08-30 9:12 ` Philippe Mathieu-Daudé
2021-08-30 9:21 ` Peter Maydell
2021-08-31 12:49 ` Paolo Bonzini
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=20210829173210.39562-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--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).