From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH RESEND 3/3] .travis.yml: Test building with Xcode 11.3
Date: Tue, 18 Feb 2020 15:20:18 +0100 [thread overview]
Message-ID: <20200218142018.7224-4-philmd@redhat.com> (raw)
In-Reply-To: <20200218142018.7224-1-philmd@redhat.com>
We currently run a CI job on macOS Mojave with Xcode 10.
QEMU policy is to support the two last major OS releases.
Add a job building on macOS Catalina, which comes with Xcode 11.
Split the target list in two, as we don't need to cover twice the
same targets.
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
---
.travis.yml | 36 +++++++++++++++++++++++++++++++++++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index a2a7fd0dd1..d02a477623 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -269,9 +269,10 @@ matrix:
# MacOSX builds - cirrus.yml also tests some MacOS builds including latest Xcode
+ # On macOS Mojave, the SDK comes bundled with Xcode 10.
- name: "OSX Xcode 10.3"
env:
- - CONFIG="--target-list=i386-softmmu,ppc-softmmu,ppc64-softmmu,m68k-softmmu,x86_64-softmmu --extra-cflags=-I/usr/local/opt/ncurses/include --extra-ldflags=-L/usr/local/opt/ncurses/lib"
+ - CONFIG="--target-list=i386-softmmu,ppc-softmmu,ppc64-softmmu,m68k-softmmu --extra-cflags=-I/usr/local/opt/ncurses/include --extra-ldflags=-L/usr/local/opt/ncurses/lib"
os: osx
osx_image: xcode10.3
compiler: clang
@@ -301,6 +302,39 @@ matrix:
- ${SRC_DIR}/configure ${BASE_CONFIG} ${CONFIG} || { cat config.log && exit 1; }
+ # On macOS Catalina, the SDK comes bundled with Xcode 11.
+ - name: "OSX Xcode 11.3"
+ env:
+ - CONFIG="--target-list=arm-softmmu,ppc64-softmmu,x86_64-softmmu --extra-cflags=-I/usr/local/opt/ncurses/include --extra-ldflags=-L/usr/local/opt/ncurses/lib"
+ os: osx
+ osx_image: xcode11.3
+ compiler: clang
+ addons:
+ homebrew:
+ packages:
+ - ccache
+ - libgcrypt
+ - libiscsi
+ - libssh2
+ - libusb
+ - lzfse
+ - lzo
+ - gettext
+ - glib
+ - gnu-sed
+ - ncurses
+ - pixman
+ - python
+ - snappy
+ - vde
+ update: true
+ before_script:
+ - brew link --overwrite python
+ - export PATH="/usr/local/opt/ccache/libexec:$PATH"
+ - mkdir -p ${BUILD_DIR} && cd ${BUILD_DIR}
+ - ${SRC_DIR}/configure ${BASE_CONFIG} ${CONFIG} || { cat config.log && exit 1; }
+
+
# Python builds
- name: "GCC Python 3.5 (x86_64-softmmu)"
env:
--
2.21.1
next prev parent reply other threads:[~2020-02-18 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 14:20 [PATCH RESEND 0/3] travis-ci: Improve OSX coverage Philippe Mathieu-Daudé
2020-02-18 14:20 ` [PATCH RESEND 1/3] .travis.yml: Expand OSX code coverage Philippe Mathieu-Daudé
2020-02-18 14:20 ` [PATCH RESEND 2/3] .travis.yml: Build with ncurses on OSX Philippe Mathieu-Daudé
2020-02-18 14:20 ` Philippe Mathieu-Daudé [this message]
2020-02-25 12:29 ` [PATCH RESEND 3/3] .travis.yml: Test building with Xcode 11.3 Alex Bennée
2020-04-09 17:44 ` Philippe Mathieu-Daudé
2020-04-09 17:54 ` Daniel P. Berrangé
2020-02-25 9:18 ` [PATCH RESEND 0/3] travis-ci: Improve OSX coverage Philippe Mathieu-Daudé
2020-04-09 17:48 ` 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=20200218142018.7224-4-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--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).