libzmq/.travis.yml
Luca Boccassi 9393f06381 Problem: CI use of sodium or nacl is confusing
Solution: establish a matrix of CI options. On one axis we have the
build system (autotools, cmake, android) and on the other axis we
have the encryption options (tweetnacl, libsodium or none).
2016-02-11 22:39:36 +00:00

40 lines
1.0 KiB
YAML

# Travis CI script
language: c
os:
- linux
- osx
env:
- BUILD_TYPE=default CURVE=libsodium
- BUILD_TYPE=android CURVE=libsodium
- BUILD_TYPE=cmake CURVE=libsodium
- BUILD_TYPE=default CURVE=tweetnacl
- BUILD_TYPE=android CURVE=tweetnacl
- BUILD_TYPE=cmake CURVE=tweetnacl
- BUILD_TYPE=default
- BUILD_TYPE=android
- BUILD_TYPE=cmake
sudo: false
addons:
apt:
sources:
- kubuntu-backports
packages:
- cmake
before_install:
- if [ $TRAVIS_OS_NAME == "osx" ] ; then brew update; brew install binutils ; fi
before_script:
# ZMQ stress tests need more open socket (files) than the usual default
# On OSX, it seems the way to set the max files limit is constantly changing, so
# try to use all known knobs to ensure compatibility across various versions
- if [ $TRAVIS_OS_NAME == "osx" ] ; then sudo sysctl -w kern.maxfiles=64000 ; sudo sysctl -w kern.maxfilesperproc=64000 ; sudo launchctl limit maxfiles 64000 64000 ; fi ; ulimit -n 64000
# Build and check this project according to the BUILD_TYPE
script: ./ci_build.sh