Commit 57274679 authored by Ralph Giles's avatar Ralph Giles

Keep the continuous integration build scripts in the repo.

We 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.
parent cc8c6502
# 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
# Continuous integration build script for opusfile.
# This script is run by automated frameworks to verify commits
# see https://mf4.xiph.org/jenkins/job/opusfile-unix/
# 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
make -C unix PKG_CONFIG_PATH=$PWD/../opus clean
make -C unix PKG_CONFIG_PATH=$PWD/../opus
# run any built-in tests
make -C unix PKG_CONFIG_PATH=$PWD/../opus check
# build the documentation
make -C doc
make -C doc/latex
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment