subsurface/scripts/android/travisbuild.sh

#!/bin/bash

set -x
set -e

# by running the build wrapper again we should be able to test newer
# versions of the dependencies even without updating the docker image
# (but of course having the right things in place will save a ton of time)
docker exec -e TRAVIS="$TRAVIS" -t android-builder subsurface/packaging/android/android-build-wrapper.sh

ls -l ../subsurface-mobile-build-docker-arm*/build/outputs/apk/
android: Add android build on travis-ci This adds a android-apk-build which runs on travis-ci. This is using a quite ugly trick, building in a docker container, basically just to get a newer cmake. The cmake in trusty is way to old to work with android builds. A good side-effect is that this is a complete copy-paste for anyone who would like to build android-binaries them self on Linux. All the uglyness is hidden away in a docker container. Signed-off-by: Anton Lundin <glance@acc.umu.se> 2017-02-06 08:06:55 +01:00			`#!/bin/bash`

Travis: try to make sure failing builds fail In some situations Travis CI doesn't seem to notice that a build failed and give us a green check mark even though the build didn't succeed. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2017-11-24 08:14:17 -08:00			`set -x`
			`set -e`

Travis: use Android docker image for build This should make it easier to make changes to our build environment. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2018-12-22 18:55:43 -08:00			`# by running the build wrapper again we should be able to test newer`
			`# versions of the dependencies even without updating the docker image`
			`# (but of course having the right things in place will save a ton of time)`
Android Docker: give the android builder its own name Users that use docker locally for Windows style build and Android style builds will (probably) not like that we use the same name for both docker containers. So, give the android builder its own name. Signed-off-by: Jan Mulder <jlmulder@xs4all.nl> 2018-12-29 08:56:08 +01:00			`docker exec -e TRAVIS="$TRAVIS" -t android-builder subsurface/packaging/android/android-build-wrapper.sh`
android: Add android build on travis-ci This adds a android-apk-build which runs on travis-ci. This is using a quite ugly trick, building in a docker container, basically just to get a newer cmake. The cmake in trusty is way to old to work with android builds. A good side-effect is that this is a complete copy-paste for anyone who would like to build android-binaries them self on Linux. All the uglyness is hidden away in a docker container. Signed-off-by: Anton Lundin <glance@acc.umu.se> 2017-02-06 08:06:55 +01:00
Android Docker: give the docker build its own output tree Again, this is relevant for developers that do local docker android builds, and normal android builds. A normal build uses the directory subsurface-mobile-build-arm(64), and when doing a docker android build this directory is shared between host and container. That sharing is good, as it nicely exposes the build tree to the host (for easy compare, inspection, etc.). But reusing the same tree as the local one is inconvenient (and possibly dangerous due to all kinds of caching issues). So, give the docker build its own output tree for the shared subsurface-mobile-build-arm(64) build output. Signed-off-by: Jan Mulder <jlmulder@xs4all.nl> 2018-12-29 09:01:06 +01:00			`ls -l ../subsurface-mobile-build-docker-arm*/build/outputs/apk/`