-
Ralph Giles authoredWe use scripts like these with jenkins to do automatic build and test runs on every commit. Keeping the build instructions in the source repository itself makes it easier to track changes, and easier to make atomic updates when something is moved in the build system which breaks the jenkins runs.
Ralph Giles authoredWe use scripts like these with jenkins to do automatic build and test runs on every commit. Keeping the build instructions in the source repository itself makes it easier to track changes, and easier to make atomic updates when something is moved in the build system which breaks the jenkins runs.
autotools.sh 521 B
# Continuous integration build script for opusfile.
# This script is run by automated frameworks to verify commits
# see https://mf4.xiph.org/jenkins/job/opusfile-autotools/
# This is intended to be run from the top-level source directory.
# WARNING: clobbers outside the current tree!
rm -f ../opus
ln -s /srv/jenkins/jobs/opus/workspace ../opus
# compile
./autogen.sh
./configure PKG_CONFIG_PATH=$PWD/../opus
make clean
make
# verify distribution target
make distcheck
# build the documentation
make -C doc/latex