Building a C Project
What This Guide Covers
CI environment for C Projects
Travis CI VMs are 64-bit and provide versions of:
- core GNU build toolchain (autotools, make), cmake, scons
C projects on travis-ci.org assume you use Autotools and Make by default.
For precise versions on the VM, please consult “Build system information” in the build log.
Because there is no dominant convention in the community about dependency management, Travis CI skips dependency installation for C projects.
If you need to perform special tasks before your tests can run, override the
install: key in your
install: make get-deps
See general build configuration guide to learn more.
Default Test Script
Because C projects on travis-ci.org assume Autotools and Make by default, naturally, the default command Travis CI will use to run your project test suite is
./configure && make && make test
Projects that find this sufficient can use a very minimalistic .travis.yml file:
This can be overridden as described in the general build configuration guide. For example, to build
by running Scons without arguments, override the
script: key in
.travis.yml like this:
Choosing compilers to test against
It is possible to test projects against either GCC or Clang, or both. To do so, specify the compiler to use using the
.travis.yml. For example, to build with Clang:
or both GCC and Clang:
compiler: - clang - gcc
Testing against two compilers will create (at least) 2 rows in your build matrix. For each row, Travis CI C builder will export the
env variable to point to either
For C projects,
compiler can be given as arrays
to construct a build matrix.
OpenMP projects should set the environment variable
OMP_NUM_THREADS to a reasonably small value (say, 4).
OpenMP detects the cores on the hosting hardware, rather than the VM on which your tests run.
The default environment variable
$CC is known to interfere with MPI projects.
In this case, we recommend unsetting it:
before_install: - test -n $CC && unset CC