From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PATCH 00/10] configure cleanups for QEMU 8.2
Date: Tue, 29 Aug 2023 10:29:21 +0200 [thread overview]
Message-ID: <20230829082931.67601-1-pbonzini@redhat.com> (raw)
This includes a few more patches cleaning up the configure/meson
separation. The highlights are fixing --host-cc, removing the
last traces of compiler detection from config-host.mak, and
dropping the useless pc-bios/Makefile.
Paolo Bonzini (10):
meson: do not unnecessarily use cmake for dependencies
meson: update unsupported host/CPU messages
configure: remove HOST_CC
configure: create native file with contents of $host_cc
meson: compile bundled device trees
contrib/plugins: use an independent makefile
meson: do not use config_host to pick tap implementations
configure, meson: move simple OS definitions to meson
configure: remove $linux and $mingw32 variables
configure: move --enable-debug-tcg to meson
configure | 65 +++++++++--------------
contrib/plugins/Makefile | 18 +++----
hw/9pfs/meson.build | 4 +-
meson.build | 43 ++++++++-------
meson_options.txt | 2 +
net/meson.build | 18 ++++---
pc-bios/Makefile | 19 -------
pc-bios/meson.build | 25 +++++++--
scripts/meson-buildoptions.sh | 3 ++
tests/migration/meson.build | 2 +-
tests/qtest/meson.build | 2 +-
tests/tcg/tricore/Makefile.softmmu-target | 2 +-
12 files changed, 101 insertions(+), 102 deletions(-)
delete mode 100644 pc-bios/Makefile
--
2.41.0
next reply other threads:[~2023-08-29 8:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 8:29 Paolo Bonzini [this message]
2023-08-29 8:29 ` [PATCH 01/10] meson: do not unnecessarily use cmake for dependencies Paolo Bonzini
2023-08-29 17:14 ` Daniel P. Berrangé
2023-08-29 8:29 ` [PATCH 02/10] meson: update unsupported host/CPU messages Paolo Bonzini
2023-08-29 10:34 ` Daniel P. Berrangé
2023-08-31 8:20 ` Paolo Bonzini
2023-08-31 8:51 ` Daniel P. Berrangé
2023-08-29 8:29 ` [PATCH 03/10] configure: remove HOST_CC Paolo Bonzini
2023-08-29 17:12 ` Daniel P. Berrangé
2023-08-29 18:40 ` Richard Henderson
2023-08-29 8:29 ` [PATCH 04/10] configure: create native file with contents of $host_cc Paolo Bonzini
2023-08-29 16:54 ` Peter Maydell
2023-08-29 17:14 ` Daniel P. Berrangé
2023-08-31 8:26 ` Paolo Bonzini
2023-08-29 18:45 ` Richard Henderson
2023-08-29 8:29 ` [PATCH 05/10] meson: compile bundled device trees Paolo Bonzini
2023-08-29 14:25 ` Philippe Mathieu-Daudé
2023-08-29 18:48 ` Richard Henderson
2023-08-29 18:47 ` Richard Henderson
2023-08-29 8:29 ` [PATCH 06/10] contrib/plugins: use an independent makefile Paolo Bonzini
2023-08-29 17:16 ` Daniel P. Berrangé
2023-08-29 8:29 ` [PATCH 07/10] meson: do not use config_host to pick tap implementations Paolo Bonzini
2023-08-29 14:26 ` Philippe Mathieu-Daudé
2023-08-29 17:05 ` Daniel P. Berrangé
2023-08-29 8:29 ` [PATCH 08/10] configure, meson: move simple OS definitions to meson Paolo Bonzini
2023-08-29 14:28 ` Philippe Mathieu-Daudé
2023-08-29 8:29 ` [PATCH 09/10] configure: remove $linux and $mingw32 variables Paolo Bonzini
2023-08-29 14:28 ` Philippe Mathieu-Daudé
2023-08-29 17:05 ` Daniel P. Berrangé
2023-08-29 8:29 ` [PATCH 10/10] configure: move --enable-debug-tcg to meson Paolo Bonzini
2023-08-29 16:57 ` Peter Maydell
2023-08-29 18:52 ` Richard Henderson
2023-08-31 8:17 ` Philippe Mathieu-Daudé
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=20230829082931.67601-1-pbonzini@redhat.com \
--to=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).