From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
"Stefan Weil" <sw@weilnetz.de>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
luoyonggang@gmail.com, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH v2 0/7] Run cross-compilation build tests in the gitlab-CI
Date: Sun, 23 Aug 2020 13:17:50 +0200 [thread overview]
Message-ID: <20200823111757.72002-1-thuth@redhat.com> (raw)
Now that we can use all our QEMU build containers in the gitlab-CI,
we can also run the cross-compilation jobs there. Of course, some
problems have to be fixed first, so this is taken care of in the first
four patches.
The following two patches make sure that we can also enable WHPX builds with
our debian-win64-cross container, so that we can compile-test this accelerator
code now, too.
The last patch then finally enables the cross-compilation jobs in the CI.
v2:
- Dropped patches that are not necessary anymore
- Added the first two patches to fix problems with the new meson build
system
Thomas Huth (7):
configure: Add system = 'linux' for meson when cross-compiling
tests/docker: Install python3-setuptools in the debian9-mxe containers
tests/Makefile: test-image-locking needs CONFIG_POSIX
tests/Makefile: test-replication needs CONFIG_POSIX
dockerfiles/debian-win64-cross: Download WHPX MinGW headers
configure: Allow automatic WHPX detection
gitlab-ci: Add cross-compiling build tests
.gitlab-ci.d/crossbuilds.yml | 113 ++++++++++++++++++
.gitlab-ci.yml | 1 +
MAINTAINERS | 1 +
configure | 4 +
tests/Makefile.include | 6 +-
.../dockerfiles/debian-win64-cross.docker | 9 +-
tests/docker/dockerfiles/debian9-mxe.docker | 2 +-
7 files changed, 133 insertions(+), 3 deletions(-)
create mode 100644 .gitlab-ci.d/crossbuilds.yml
--
2.18.2
next reply other threads:[~2020-08-23 11:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 11:17 Thomas Huth [this message]
2020-08-23 11:17 ` [PATCH v2 1/7] configure: Add system = 'linux' for meson when cross-compiling Thomas Huth
2020-09-01 16:18 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 2/7] tests/docker: Install python3-setuptools in the debian9-mxe containers Thomas Huth
2020-09-01 16:19 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 3/7] tests/Makefile: test-image-locking needs CONFIG_POSIX Thomas Huth
2020-09-01 16:21 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 4/7] tests/Makefile: test-replication " Thomas Huth
2020-09-01 16:22 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 5/7] dockerfiles/debian-win64-cross: Download WHPX MinGW headers Thomas Huth
2020-09-01 16:25 ` Daniel P. Berrangé
2020-09-01 16:31 ` Thomas Huth
2020-08-23 11:17 ` [PATCH v2 6/7] configure: Allow automatic WHPX detection Thomas Huth
2020-09-01 16:25 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 7/7] gitlab-ci: Add cross-compiling build tests Thomas Huth
2020-09-01 16:27 ` Daniel P. Berrangé
2020-09-01 16:36 ` Thomas Huth
2020-08-25 7:59 ` [PATCH v2 0/7] Run cross-compilation build tests in the gitlab-CI Paolo Bonzini
2020-09-01 16:29 ` Daniel P. Berrangé
2020-09-01 16:38 ` Thomas Huth
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=20200823111757.72002-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--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).