mifr/subsurface
1
0
Fork 0
mirror of https://github.com/subsurface/subsurface.git synced 2024-12-03 15:43:09 +00:00
Code Issues Projects Releases Packages Wiki Activity
subsurface/.github/workflows/ios.yml

36 lines
1 KiB
YAML
Raw Normal View History

GitHub Action: add iOS build This is incredibly brute force, downloading a 3+GB installer and installing all of the Qt/iOS binaries. This first attempt is mainly to get an idea how long this will take and if this will fit within the size constraints of the build VM. This commit doesn't even try to build, yet. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-19 09:37:28 +00:00
name: iOS
GitHub Actions: only build pushes into and PR against master This should fix the odd double builds for people who create branches for pull requests in the main repository. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-26 01:04:01 +00:00
on:
push:
branches:
- master
pull_request:
branches:
- master
GitHub Action: add iOS build This is incredibly brute force, downloading a 3+GB installer and installing all of the Qt/iOS binaries. This first attempt is mainly to get an idea how long this will take and if this will fit within the size constraints of the build VM. This commit doesn't even try to build, yet. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-19 09:37:28 +00:00
jobs:
mobileBuild:
build-systsem: move back to Xcode 11 It appears that Xcode 12 applies some rather self defeating logic when picking build architectures in release builds for the simulator. It adds aarch64 by default and I can't find a way to turn that off from the command line. At the same time, you can't link against the simulator if you have build with aarch64 as the aarch64 simulator doesn't exist, yet. Since I couldn't get any of the claimed workarounds to work, I'm forcing Xcode 11 to be used in the Action. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-11-01 19:27:06 +00:00
runs-on: macOS-10.15
GitHub Action: add iOS build This is incredibly brute force, downloading a 3+GB installer and installing all of the Qt/iOS binaries. This first attempt is mainly to get an idea how long this will take and if this will fit within the size constraints of the build VM. This commit doesn't even try to build, yet. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-19 09:37:28 +00:00
steps:
build-systsem: move back to Xcode 11 It appears that Xcode 12 applies some rather self defeating logic when picking build architectures in release builds for the simulator. It adds aarch64 by default and I can't find a way to turn that off from the command line. At the same time, you can't link against the simulator if you have build with aarch64 as the aarch64 simulator doesn't exist, yet. Since I couldn't get any of the claimed workarounds to work, I'm forcing Xcode 11 to be used in the Action. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-11-01 19:27:06 +00:00
- name: switch to Xcode 11
run: sudo xcode-select -s "/Applications/Xcode_11.7.app"
GitHub Action: add iOS build This is incredibly brute force, downloading a 3+GB installer and installing all of the Qt/iOS binaries. This first attempt is mainly to get an idea how long this will take and if this will fit within the size constraints of the build VM. This commit doesn't even try to build, yet. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-19 09:37:28 +00:00
- name: checkout sources
uses: actions/checkout@v1
- name: setup Homebrew
GitHub Actions: add pkg-config to iOS build Our builds fail because we are missing pkg-config. I'm not quite sure if this is triggered by a new dependency or if pkg-config used to be there and now isn't. Either way, this should hopefully fix things. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-04-04 17:25:47 +00:00
run: brew install autoconf automake libtool pkg-config
GitHub Action: add iOS build This is incredibly brute force, downloading a 3+GB installer and installing all of the Qt/iOS binaries. This first attempt is mainly to get an idea how long this will take and if this will fit within the size constraints of the build VM. This commit doesn't even try to build, yet. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-19 09:37:28 +00:00
- name: set our Qt build
run: |
env
GitHub Actions/iOS: shift to using a pre-packaged Qt installation Since the official Qt binaries can no longer be installed without disclosing credentials (well, sure, that could be done through secrets), I decided that we should go back to packaging just the part of the iOS Qt SDK that we need. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-02-12 17:47:52 +00:00
curl -L --output Qt-5.14.1-ios.tar.xz https://f002.backblazeb2.com/file/Subsurface-Travis/Qt-5.14.1-ios.tar.xz
mkdir -p $HOME/Qt
xzcat Qt-5.14.1-ios.tar.xz | tar -x -C $HOME/Qt -f -
GitHub Action: add iOS build This is incredibly brute force, downloading a 3+GB installer and installing all of the Qt/iOS binaries. This first attempt is mainly to get an idea how long this will take and if this will fit within the size constraints of the build VM. This commit doesn't even try to build, yet. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-19 09:37:28 +00:00
- name: build Subsurface-mobile for iOS
run: |
cd packaging/ios
ln -s $HOME/Qt Qt
echo "build dependencies"
bash -x build.sh -simulator
echo "Subsurface-mobile for iOS"
cd build-Subsurface-mobile-*for_iOS-Release
sed -i.bak 's/-Wall/-Wno-everything/' Makefile # make the build far less verbose
make -j2
Reference in a new issue Copy permalink