From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Subject: [PULL 3/6] tests/lcitool: Remove g++ from the containers (except for the MinGW one)
Date: Fri, 17 May 2024 14:25:49 +0200 [thread overview]
Message-ID: <20240517122552.584215-4-thuth@redhat.com> (raw)
In-Reply-To: <20240517122552.584215-1-thuth@redhat.com>
We don't need C++ for the normal QEMU builds anymore, so installing
g++ in each and every container seems to be a waste of time and disk
space. The only container that still needs it is the Fedora MinGW
container that builds the only remaining C++ code in ./qga/vss-win32/
and we can install it there with an extra project yml file instead.
Message-ID: <20240516084059.511463-4-thuth@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
tests/lcitool/projects/qemu-minimal.yml | 1 -
tests/lcitool/projects/qemu-win-installer.yml | 4 ++++
tests/lcitool/projects/qemu.yml | 1 -
tests/lcitool/refresh | 1 +
4 files changed, 5 insertions(+), 2 deletions(-)
create mode 100644 tests/lcitool/projects/qemu-win-installer.yml
diff --git a/tests/lcitool/projects/qemu-minimal.yml b/tests/lcitool/projects/qemu-minimal.yml
index d44737dc1d..6bc232a1c3 100644
--- a/tests/lcitool/projects/qemu-minimal.yml
+++ b/tests/lcitool/projects/qemu-minimal.yml
@@ -7,7 +7,6 @@ packages:
- ccache
- findutils
- flex
- - g++
- gcc
- gcc-native
- glib2
diff --git a/tests/lcitool/projects/qemu-win-installer.yml b/tests/lcitool/projects/qemu-win-installer.yml
new file mode 100644
index 0000000000..86aa22297c
--- /dev/null
+++ b/tests/lcitool/projects/qemu-win-installer.yml
@@ -0,0 +1,4 @@
+# Additional packages that are required to build the code in qga/vss-win32/
+---
+packages:
+ - g++
diff --git a/tests/lcitool/projects/qemu.yml b/tests/lcitool/projects/qemu.yml
index 9173d1e36e..b63b6bd850 100644
--- a/tests/lcitool/projects/qemu.yml
+++ b/tests/lcitool/projects/qemu.yml
@@ -22,7 +22,6 @@ packages:
- findutils
- flex
- fuse3
- - g++
- gcc
- gcc-native
- gcovr
diff --git a/tests/lcitool/refresh b/tests/lcitool/refresh
index 174818d9c9..789acefb75 100755
--- a/tests/lcitool/refresh
+++ b/tests/lcitool/refresh
@@ -192,6 +192,7 @@ try:
"s390x-softmmu,s390x-linux-user"))
generate_dockerfile("fedora-win64-cross", "fedora-38",
+ project='qemu,qemu-win-installer',
cross="mingw64",
trailer=cross_build("x86_64-w64-mingw32-",
"x86_64-softmmu"))
--
2.45.0
next prev parent reply other threads:[~2024-05-17 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 12:25 [PULL 0/6] Fix s390x crash and clean up container images Thomas Huth
2024-05-17 12:25 ` [PULL 1/6] tests/lcitool/refresh: Treat the output of lcitool as text, not as bytes Thomas Huth
2024-05-17 12:25 ` [PULL 2/6] tests/lcitool: Remove 'xfsprogs' from QEMU Thomas Huth
2024-05-17 12:25 ` Thomas Huth [this message]
2024-05-17 12:25 ` [PULL 4/6] tests/lcitool/projects/qemu.yml: Sort entries alphabetically again Thomas Huth
2024-05-17 12:25 ` [PULL 5/6] tests/docker/dockerfiles: Update container files with "lcitool-refresh" Thomas Huth
2024-05-17 12:25 ` [PULL 6/6] hw/intc/s390_flic: Fix crash that occurs when saving the machine state Thomas Huth
2024-05-18 13:25 ` [PULL 0/6] Fix s390x crash and clean up container images Richard Henderson
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=20240517122552.584215-4-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).