xserver/test/scripts/build-travis-deps.sh

#!/bin/sh

export PREFIX=/usr
export TRAVIS_BUILD_DIR=/root
export PIGLIT_DIR=$TRAVIS_BUILD_DIR/piglit
export XTEST_DIR=$TRAVIS_BUILD_DIR/xtest

set -e
set -x

meson setup build/
meson configure -Dprefix=$PREFIX build/
ninja -C build/ install
ninja -C build/ test

status=$?

cat build/meson-logs/testlog.txt

exit $status
travis: Add a build script for Travis CI. This currently does a meson build using a docker image I've prepared. The Dockerfile source is at: https://github.com/anholt/xserver-travis Docker proved to be necessary to cut the build time per Travis push. If some day we end up using meson in more of the X stack, we may be able to move more dependencies out of the docker image and into the CI build (putting the I in CI). Until then, we'll have to do docker image rebuilds when dependencies are added/updated. To enable Travis CI on your github repository, see the first two steps of the docs at: https://docs.travis-ci.com/user/getting-started/ Once you do that, pushing branches to your github repo will trigger builds, which will send you email if they fail. Current build status can be veiewed your account on travis-ci.org: https://travis-ci.org/anholt/xserver 2017-06-01 12:29:12 -07:00			`#!/bin/sh`

			`export PREFIX=/usr`
			`export TRAVIS_BUILD_DIR=/root`
			`export PIGLIT_DIR=$TRAVIS_BUILD_DIR/piglit`
			`export XTEST_DIR=$TRAVIS_BUILD_DIR/xtest`

			`set -e`
travis: Switch linux build from stretch to rawhide Stretch's Mesa is too far behind, and building Mesa to build xserver is not the sort of problem we're trying to solve here. But our Travis scripts run inside a docker image, and that image can be whatever, so since I have to keep rawhide building anyway let's switch to that for now. The dockerfile can be found at: https://github.com/nwnk/xserver-travis The $DISTRO part of the change is foreshadowing for the day we readd a (probably sid-based) debian image; patches for other environments are welcome. Signed-off-by: Adam Jackson <ajax@redhat.com> 2018-03-14 13:13:54 -04:00			`set -x`
travis: Add a build script for Travis CI. This currently does a meson build using a docker image I've prepared. The Dockerfile source is at: https://github.com/anholt/xserver-travis Docker proved to be necessary to cut the build time per Travis push. If some day we end up using meson in more of the X stack, we may be able to move more dependencies out of the docker image and into the CI build (putting the I in CI). Until then, we'll have to do docker image rebuilds when dependencies are added/updated. To enable Travis CI on your github repository, see the first two steps of the docs at: https://docs.travis-ci.com/user/getting-started/ Once you do that, pushing branches to your github repo will trigger builds, which will send you email if they fail. Current build status can be veiewed your account on travis-ci.org: https://travis-ci.org/anholt/xserver 2017-06-01 12:29:12 -07:00
travis: Switch linux build from stretch to rawhide Stretch's Mesa is too far behind, and building Mesa to build xserver is not the sort of problem we're trying to solve here. But our Travis scripts run inside a docker image, and that image can be whatever, so since I have to keep rawhide building anyway let's switch to that for now. The dockerfile can be found at: https://github.com/nwnk/xserver-travis The $DISTRO part of the change is foreshadowing for the day we readd a (probably sid-based) debian image; patches for other environments are welcome. Signed-off-by: Adam Jackson <ajax@redhat.com> 2018-03-14 13:13:54 -04:00			`meson setup build/`
			`meson configure -Dprefix=$PREFIX build/`
travis: Add a build script for Travis CI. This currently does a meson build using a docker image I've prepared. The Dockerfile source is at: https://github.com/anholt/xserver-travis Docker proved to be necessary to cut the build time per Travis push. If some day we end up using meson in more of the X stack, we may be able to move more dependencies out of the docker image and into the CI build (putting the I in CI). Until then, we'll have to do docker image rebuilds when dependencies are added/updated. To enable Travis CI on your github repository, see the first two steps of the docs at: https://docs.travis-ci.com/user/getting-started/ Once you do that, pushing branches to your github repo will trigger builds, which will send you email if they fail. Current build status can be veiewed your account on travis-ci.org: https://travis-ci.org/anholt/xserver 2017-06-01 12:29:12 -07:00			`ninja -C build/ install`
			`ninja -C build/ test`
ci: Ignore builds for branches aimed at other CI services Make appveyor ignore builds for /travis.*/ and vice versa. If you're only testing a Windows change, building for OSX and Linux too is a bit rude. Signed-off-by: Adam Jackson <ajax@redhat.com> 2018-03-14 16:43:09 -04:00
			`status=$?`

			`cat build/meson-logs/testlog.txt`

			`exit $status`