From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: [PULL 10/12] tests/lcitool: Install mingw-w64-tools for the Windows cross-builds
Date: Thu, 6 Jun 2024 12:50:45 +0100 [thread overview]
Message-ID: <20240606115047.421045-11-alex.bennee@linaro.org> (raw)
In-Reply-To: <20240606115047.421045-1-alex.bennee@linaro.org>
From: Thomas Huth <thuth@redhat.com>
Beside g++ we also need the mingw-w64-tools for properly building
the code in qga/vss-win32/ , so let's install that package now, too.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20240601070543.37786-5-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20240603175328.3823123-11-alex.bennee@linaro.org>
diff --git a/tests/docker/dockerfiles/fedora-win64-cross.docker b/tests/docker/dockerfiles/fedora-win64-cross.docker
index fef846d5a6..007e1574bd 100644
--- a/tests/docker/dockerfiles/fedora-win64-cross.docker
+++ b/tests/docker/dockerfiles/fedora-win64-cross.docker
@@ -75,6 +75,7 @@ ENV NINJA "/usr/bin/ninja"
ENV PYTHON "/usr/bin/python3"
RUN nosync dnf install -y \
+ mingw-w64-tools \
mingw32-nsis \
mingw64-SDL2 \
mingw64-SDL2_image \
diff --git a/tests/lcitool/projects/qemu-win-installer.yml b/tests/lcitool/projects/qemu-win-installer.yml
index 86aa22297c..f3663ba030 100644
--- a/tests/lcitool/projects/qemu-win-installer.yml
+++ b/tests/lcitool/projects/qemu-win-installer.yml
@@ -2,3 +2,4 @@
---
packages:
- g++
+ - mingw-w64-tools
--
2.39.2
next prev parent reply other threads:[~2024-06-06 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 11:50 [PULL 00/12] testing cleanups (ci, vm, lcitool, ansible) Alex Bennée
2024-06-06 11:50 ` [PULL 01/12] ci: remove centos-steam-8 customer runner Alex Bennée
2024-06-06 11:50 ` [PULL 02/12] docs/devel: update references to centos to non-versioned container Alex Bennée
2024-06-06 11:50 ` [PULL 03/12] tests/vm: update centos.aarch64 image to 9 Alex Bennée
2024-06-06 11:50 ` [PULL 04/12] tests/vm: remove plain centos image Alex Bennée
2024-06-06 11:50 ` [PULL 05/12] scripts/ci: remove CentOS bits from common build-environment Alex Bennée
2024-06-06 11:50 ` [PULL 06/12] docs/ci: clean-up references for consistency Alex Bennée
2024-06-06 11:50 ` [PULL 07/12] tests/lcitool: Delete obsolete centos-stream-8.yml file Alex Bennée
2024-06-06 11:50 ` [PULL 08/12] .gitlab-ci.d/buildtest.yml: Use -fno-sanitize=function in the clang-system job Alex Bennée
2024-06-06 11:50 ` [PULL 09/12] tests/lcitool: Bump to latest libvirt-ci and update Fedora and Alpine version Alex Bennée
2024-06-06 11:50 ` Alex Bennée [this message]
2024-06-06 11:50 ` [PULL 11/12] tests/lcitool: generate package lists for ansible Alex Bennée
2024-06-06 11:50 ` [PULL 12/12] scripts/ci: drive ubuntu/build-environment.yml from lcitool Alex Bennée
2024-06-06 18:54 ` [PULL 00/12] testing cleanups (ci, vm, lcitool, ansible) 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=20240606115047.421045-11-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).