Zengtudor/pybind11
1
0
Fork 0
mirror of https://github.com/pybind/pybind11.git synced 2024-11-11 08:03:55 +00:00
Code Issues Packages Projects Releases Wiki Activity
192eb88475
pybind11/.travis.yml

110 lines
3.1 KiB
YAML
Raw Normal View History

Added configuration files for Travis CI integration
2015-10-11 14:29:35 +00:00
language: cpp
sudo: false
Improve CI test coverage: eigen, numpy and C++14
2016-07-29 22:15:01 +00:00
matrix:
include:
- os: linux
compiler: gcc-4.8
Add g++-6 builds to travis-ci The current linux/g++ testing (using a backported g++-4.8 on a 4-year-old Ubuntu) is quite ancient. It's good as a baseline level of support, but it means we aren't testing g++'s C++14 support at all (which is why #334 happened). This commit adds a docker-based travis-ci build using the debian "testing" distribution, which will give us both another test system (with different versions of build tools), while, more importantly, also adding a build and test run using g++ in C++14 mode.
2016-08-14 16:31:52 +00:00
env: PYTHON=2.7 CPP=11 GCC=4.8
addons:
apt:
sources:
- ubuntu-toolchain-r-test
- kubuntu-backports # cmake 2.8.12
packages:
- g++-4.8
- cmake
Improve CI test coverage: eigen, numpy and C++14
2016-07-29 22:15:01 +00:00
- os: linux
compiler: gcc-4.8
Add g++-6 builds to travis-ci The current linux/g++ testing (using a backported g++-4.8 on a 4-year-old Ubuntu) is quite ancient. It's good as a baseline level of support, but it means we aren't testing g++'s C++14 support at all (which is why #334 happened). This commit adds a docker-based travis-ci build using the debian "testing" distribution, which will give us both another test system (with different versions of build tools), while, more importantly, also adding a build and test run using g++ in C++14 mode.
2016-08-14 16:31:52 +00:00
env: PYTHON=3.5 CPP=11 GCC=4.8
addons:
apt:
sources:
- ubuntu-toolchain-r-test
- deadsnakes
- kubuntu-backports # cmake 2.8.12
packages:
- g++-4.8
- python3.5-dev
- cmake
Improve CI test coverage: eigen, numpy and C++14
2016-07-29 22:15:01 +00:00
- os: osx
osx_image: xcode7.3
env: PYTHON=2.7 CPP=14
- os: osx
osx_image: xcode7.3
env: PYTHON=3.5 CPP=14
Add g++-6 builds to travis-ci The current linux/g++ testing (using a backported g++-4.8 on a 4-year-old Ubuntu) is quite ancient. It's good as a baseline level of support, but it means we aren't testing g++'s C++14 support at all (which is why #334 happened). This commit adds a docker-based travis-ci build using the debian "testing" distribution, which will give us both another test system (with different versions of build tools), while, more importantly, also adding a build and test run using g++ in C++14 mode.
2016-08-14 16:31:52 +00:00
- compiler: gcc-6
services: docker
sudo: true
env: PYTHON=2.7 CPP=14 DOCKER=debian:testing NATIVE_DEPS=1
install:
Build sphinx docs with -W during travis-ci builds
2016-08-17 02:46:37 +00:00
- >
docker exec --tty "$containerid" apt-get -y --no-install-recommends install
Build docs just once, in a dedicated build This switches the travis-ci build to build the docs in a dedicated build rather than as part of the regular linux/osx builds.
2016-08-17 13:14:22 +00:00
python2.7-dev python-scipy libeigen3-dev
Build sphinx docs with -W during travis-ci builds
2016-08-17 02:46:37 +00:00
cmake make g++
Add g++-6 builds to travis-ci The current linux/g++ testing (using a backported g++-4.8 on a 4-year-old Ubuntu) is quite ancient. It's good as a baseline level of support, but it means we aren't testing g++'s C++14 support at all (which is why #334 happened). This commit adds a docker-based travis-ci build using the debian "testing" distribution, which will give us both another test system (with different versions of build tools), while, more importantly, also adding a build and test run using g++ in C++14 mode.
2016-08-14 16:31:52 +00:00
- compiler: gcc-6
services: docker
sudo: true
env: PYTHON=3.5 CPP=14 DOCKER=debian:testing NATIVE_DEPS=1
install:
Build sphinx docs with -W during travis-ci builds
2016-08-17 02:46:37 +00:00
- >
docker exec --tty "$containerid" apt-get -y --no-install-recommends install
Build docs just once, in a dedicated build This switches the travis-ci build to build the docs in a dedicated build rather than as part of the regular linux/osx builds.
2016-08-17 13:14:22 +00:00
python3.5-dev python3-scipy libeigen3-dev
Build sphinx docs with -W during travis-ci builds
2016-08-17 02:46:37 +00:00
cmake make g++
Build docs just once, in a dedicated build This switches the travis-ci build to build the docs in a dedicated build rather than as part of the regular linux/osx builds.
2016-08-17 13:14:22 +00:00
# Documentation build:
- os: linux
language: docs
compiler: sphinx
env: PYTHON=2.7 DOCS=1
pip/venv in `before_install`; override `install` for docs build Rather than adding an `if [ -n "$DOCS" ]` as a separate install instruction, this simplifies the travis-ci logic to do the pip/venv setup in the `before_install` hook, leaving the install hook to just install the needed packages. This makes the default install script simpler: it doesn't need to check NATIVE_DEPS or DOCS because both of those now override `install` anyway, so the top-level `install` is really just the install for the gcc-4.8 and osx builds; the docker builds and docs build override install completely.
2016-08-17 18:19:08 +00:00
install: pip install sphinx sphinx_rtd_theme
script: make -C docs html SPHINX_OPTIONS=-W
travis: cache pip
2016-01-21 18:21:59 +00:00
cache:
directories:
- $HOME/.cache/pip
Cache C/C++ compilation
2016-05-21 08:29:30 +00:00
- ccache
Add g++-6 builds to travis-ci The current linux/g++ testing (using a backported g++-4.8 on a 4-year-old Ubuntu) is quite ancient. It's good as a baseline level of support, but it means we aren't testing g++'s C++14 support at all (which is why #334 happened). This commit adds a docker-based travis-ci build using the debian "testing" distribution, which will give us both another test system (with different versions of build tools), while, more importantly, also adding a build and test run using g++ in C++14 mode.
2016-08-14 16:31:52 +00:00
before_install:
- |
if [ -n "$DOCKER" ]; then
docker pull $DOCKER
export containerid=$(docker run --detach --tty \
--volume="$PWD":/pybind11 --workdir=/pybind11 \
--env="CC=$CC" --env="CXX=$CXX" --env="DEBIAN_FRONTEND=$DEBIAN_FRONTEND" \
--env=GCC_COLORS=\ \
$DOCKER)
docker exec --tty "$containerid" apt-get update
docker exec --tty "$containerid" apt-get -y upgrade
export SCRIPT_RUN_PREFIX="docker exec --tty $containerid"
fi
Improve CI test coverage: eigen, numpy and C++14
2016-07-29 22:15:01 +00:00
- |
Add g++-6 builds to travis-ci The current linux/g++ testing (using a backported g++-4.8 on a 4-year-old Ubuntu) is quite ancient. It's good as a baseline level of support, but it means we aren't testing g++'s C++14 support at all (which is why #334 happened). This commit adds a docker-based travis-ci build using the debian "testing" distribution, which will give us both another test system (with different versions of build tools), while, more importantly, also adding a build and test run using g++ in C++14 mode.
2016-08-14 16:31:52 +00:00
if [ -z "$NATIVE_DEPS" ]; then
if [ "$TRAVIS_OS_NAME" = "linux" ]; then
if [ -n "$GCC" ]; then export CXX=g++-$GCC CC=gcc-$GCC; fi
pip install --user --upgrade pip virtualenv
virtualenv -p python$PYTHON venv
elif [ "$TRAVIS_OS_NAME" = "osx" ]; then
if [ "${PYTHON:0:1}" = "3" ]; then
PMAJOR=3; brew update; brew install python$PMAJOR;
else
curl -fsSL -O https://bootstrap.pypa.io/get-pip.py
sudo -H python get-pip.py
fi
pip$PMAJOR install --user --upgrade pip virtualenv
python$PMAJOR -m virtualenv venv
Use system version of Python 2.7 on OS X on Travis
2016-08-01 22:42:07 +00:00
fi
Add g++-6 builds to travis-ci The current linux/g++ testing (using a backported g++-4.8 on a 4-year-old Ubuntu) is quite ancient. It's good as a baseline level of support, but it means we aren't testing g++'s C++14 support at all (which is why #334 happened). This commit adds a docker-based travis-ci build using the debian "testing" distribution, which will give us both another test system (with different versions of build tools), while, more importantly, also adding a build and test run using g++ in C++14 mode.
2016-08-14 16:31:52 +00:00
source venv/bin/activate
Build docs just once, in a dedicated build This switches the travis-ci build to build the docs in a dedicated build rather than as part of the regular linux/osx builds.
2016-08-17 13:14:22 +00:00
fi
pip/venv in `before_install`; override `install` for docs build Rather than adding an `if [ -n "$DOCS" ]` as a separate install instruction, this simplifies the travis-ci logic to do the pip/venv setup in the `before_install` hook, leaving the install hook to just install the needed packages. This makes the default install script simpler: it doesn't need to check NATIVE_DEPS or DOCS because both of those now override `install` anyway, so the top-level `install` is really just the install for the gcc-4.8 and osx builds; the docker builds and docs build override install completely.
2016-08-17 18:19:08 +00:00
install:
Build docs just once, in a dedicated build This switches the travis-ci build to build the docs in a dedicated build rather than as part of the regular linux/osx builds.
2016-08-17 13:14:22 +00:00
- |
pip/venv in `before_install`; override `install` for docs build Rather than adding an `if [ -n "$DOCS" ]` as a separate install instruction, this simplifies the travis-ci logic to do the pip/venv setup in the `before_install` hook, leaving the install hook to just install the needed packages. This makes the default install script simpler: it doesn't need to check NATIVE_DEPS or DOCS because both of those now override `install` anyway, so the top-level `install` is really just the install for the gcc-4.8 and osx builds; the docker builds and docs build override install completely.
2016-08-17 18:19:08 +00:00
pip install numpy scipy
Add g++-6 builds to travis-ci The current linux/g++ testing (using a backported g++-4.8 on a 4-year-old Ubuntu) is quite ancient. It's good as a baseline level of support, but it means we aren't testing g++'s C++14 support at all (which is why #334 happened). This commit adds a docker-based travis-ci build using the debian "testing" distribution, which will give us both another test system (with different versions of build tools), while, more importantly, also adding a build and test run using g++ in C++14 mode.
2016-08-14 16:31:52 +00:00
pip/venv in `before_install`; override `install` for docs build Rather than adding an `if [ -n "$DOCS" ]` as a separate install instruction, this simplifies the travis-ci logic to do the pip/venv setup in the `before_install` hook, leaving the install hook to just install the needed packages. This makes the default install script simpler: it doesn't need to check NATIVE_DEPS or DOCS because both of those now override `install` anyway, so the top-level `install` is really just the install for the gcc-4.8 and osx builds; the docker builds and docs build override install completely.
2016-08-17 18:19:08 +00:00
wget -q -O eigen.tar.gz https://bitbucket.org/eigen/eigen/get/3.2.9.tar.gz
tar xzf eigen.tar.gz
export CMAKE_EXTRA_ARGS="${CMAKE_EXTRA_ARGS} -DCMAKE_INCLUDE_PATH=eigen-eigen-dc6cfdf9bcec"
Improve CI test coverage: eigen, numpy and C++14
2016-07-29 22:15:01 +00:00
script:
Report warnings as errors on Travis and AppVeyor
2016-08-15 11:41:44 +00:00
- $SCRIPT_RUN_PREFIX cmake ${CMAKE_EXTRA_ARGS}
-DPYBIND11_PYTHON_VERSION=$PYTHON
-DPYBIND11_CPP_STANDARD=-std=c++$CPP
-DPYBIND11_WERROR=ON
Add g++-6 builds to travis-ci The current linux/g++ testing (using a backported g++-4.8 on a 4-year-old Ubuntu) is quite ancient. It's good as a baseline level of support, but it means we aren't testing g++'s C++14 support at all (which is why #334 happened). This commit adds a docker-based travis-ci build using the debian "testing" distribution, which will give us both another test system (with different versions of build tools), while, more importantly, also adding a build and test run using g++ in C++14 mode.
2016-08-14 16:31:52 +00:00
- $SCRIPT_RUN_PREFIX make CTEST_OUTPUT_ON_FAILURE=TRUE check -j 2
after_script:
- if [ -n "$DOCKER" ]; then docker stop "$containerid"; docker rm "$containerid"; fi
Reference in New Issue Copy Permalink