From: Akihiko Odaki <akihiko.odaki@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Jason Wang" <jasowang@redhat.com>,
qemu-devel@nongnu.org, Programmingkid <programmingkidx@gmail.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Akihiko Odaki" <akihiko.odaki@gmail.com>
Subject: [PATCH v4 0/4] cutils: Introduce bundle mechanism
Date: Wed, 15 Jun 2022 06:07:42 +0900 [thread overview]
Message-ID: <20220614210746.78911-1-akihiko.odaki@gmail.com> (raw)
Developers often run QEMU without installing. The bundle mechanism
allows to look up files which should be present in installation even in
such a situation.
It is a general mechanism and can find any files located relative
to the installation tree. The build tree must have a new directory,
qemu-bundle, to represent what files the installation tree would
have for reference by the executables.
v4:
* Add Daniel P. Berrangé to CC. Hopefully this helps merging his patch:
https://mail.gnu.org/archive/html/qemu-devel/2022-06/msg02276.html
* Rebased to the latest QEMU.
v3:
* Note that the bundle mechanism is for any files located relative to the
installation tree including but not limited to datadir. (Peter Maydell)
* Fix "bridge" typo (Philippe Mathieu-Daudé)
v2: Rebased to the latest QEMU.
Akihiko Odaki (4):
cutils: Introduce bundle mechanism
datadir: Use bundle mechanism
ui/icons: Use bundle mechanism
net: Use bundle mechanism
.travis.yml | 2 +-
include/net/net.h | 2 +-
include/qemu/cutils.h | 19 +++++++++++++++++++
meson.build | 13 ++++++++++---
net/tap.c | 6 +++++-
pc-bios/keymaps/meson.build | 3 +++
pc-bios/meson.build | 17 +++++++++--------
qemu-options.hx | 4 ++--
scripts/oss-fuzz/build.sh | 2 +-
softmmu/datadir.c | 35 ++++++++++++-----------------------
tests/qtest/fuzz/fuzz.c | 15 ---------------
tests/vm/fedora | 2 +-
tests/vm/freebsd | 2 +-
tests/vm/netbsd | 2 +-
tests/vm/openbsd | 2 +-
ui/cocoa.m | 29 ++++++++++++++++-------------
ui/gtk.c | 6 +++++-
ui/icons/meson.build | 36 ++++++++++++++++++++++++++++--------
ui/sdl2.c | 18 +++++++++++-------
util/cutils.c | 33 +++++++++++++++++++++++++++++++++
20 files changed, 160 insertions(+), 88 deletions(-)
--
2.32.1 (Apple Git-133)
next reply other threads:[~2022-06-14 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 21:07 Akihiko Odaki [this message]
2022-06-14 21:07 ` [PATCH v4 1/4] cutils: Introduce bundle mechanism Akihiko Odaki
2022-06-15 8:19 ` Paolo Bonzini
2022-06-15 13:12 ` Akihiko Odaki
2022-06-14 21:07 ` [PATCH v4 2/4] datadir: Use " Akihiko Odaki
2022-06-15 8:16 ` Daniel P. Berrangé
2022-06-15 8:21 ` Paolo Bonzini
2022-06-14 21:07 ` [PATCH v4 3/4] ui/icons: " Akihiko Odaki
2022-06-14 21:07 ` [PATCH v4 4/4] net: " Akihiko Odaki
2022-06-15 8:30 ` [PATCH v4 0/4] cutils: Introduce " Daniel P. Berrangé
2022-06-15 11:02 ` Paolo Bonzini
2022-06-15 11:27 ` Daniel P. Berrangé
2022-06-15 8:39 ` Paolo Bonzini
2022-06-15 10:53 ` 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=20220614210746.78911-1-akihiko.odaki@gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.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).