xserver-multidpi/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

meson --prefix=/usr build/
ninja -C build/ install
ninja -C build/ test
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 21:29:12 +02: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: Set prefix to /usr, so we find xkbcomp. Reviewed-by: Adam Jackson <ajax@redhat.com> Signed-off-by: Eric Anholt <eric@anholt.net> 2017-08-04 22:19:00 +02:00			`meson --prefix=/usr 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 21:29:12 +02:00			`ninja -C build/ install`
			`ninja -C build/ test`