From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>
Subject: [PATCH 1/2] configure: support passthrough of -Dxxx args to meson
Date: Fri, 22 Sep 2023 14:55:54 +0100 [thread overview]
Message-ID: <20230922135555.241809-2-berrange@redhat.com> (raw)
In-Reply-To: <20230922135555.241809-1-berrange@redhat.com>
This can be useful for setting some meson global options, such as the
optimization level or debug state, which don't have an analogous
option explicitly defined in QEMU's configure wrapper script.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
configure | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configure b/configure
index e08127045d..cbd7e03e9f 100755
--- a/configure
+++ b/configure
@@ -931,6 +931,8 @@ cat << EOF
bsd-user all BSD usermode emulation targets
pie Position Independent Executables
+ -Dmesonoptname=val passthrough option to meson unmodified
+
NOTE: The object files are built at the place where configure is launched
EOF
exit 0
--
2.41.0
next prev parent reply other threads:[~2023-09-22 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 13:55 [PATCH 0/2] Improve _FORTIFY_SOURCE robustness Daniel P. Berrangé
2023-09-22 13:55 ` Daniel P. Berrangé [this message]
2023-09-22 14:00 ` [PATCH 1/2] configure: support passthrough of -Dxxx args to meson Peter Maydell
2023-09-22 14:36 ` Thomas Huth
2023-09-22 14:42 ` Daniel P. Berrangé
2023-09-22 13:55 ` [PATCH 2/2] osdep: set _FORTIFY_SOURCE=2 when optimization is enabled Daniel P. Berrangé
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=20230922135555.241809-2-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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).