2014-12-22 21:37:23 -08:00
|
|
|
sudo: false
|
|
|
|
|
|
Adding a .travis.yml file to use the travis-ci.org
From wikipedia:
Travis CI is a hosted, distributed continuous integration service used
to build and test projects hosted at GitHub.
Travis CI is configured by adding a file named .travis.yml, which is a
YAML format text file, to the root directory of the GitHub repository.
Travis CI automatically detects when a commit has been made and pushed
to a GitHub repository that is using Travis CI, and each time this
happens, it will try to build the project and run tests. This includes
commits to all branches, not just to the master branch. When that
process has completed, it will notify a developer in the way it has been
configured to do so — for example, by sending an email containing the
test results (showing success or failure), or by posting a message on an
IRC channel. It can be configured to run the tests on a range of
different machines, with different software installed (such as older
versions of a programming language, to test for compatibility).
2013-12-12 16:23:07 +01:00
|
|
|
language: c
|
|
|
|
|
|
2015-06-20 22:44:09 -07:00
|
|
|
addons:
|
|
|
|
|
apt:
|
|
|
|
|
packages:
|
|
|
|
|
- libonig-dev
|
|
|
|
|
- valgrind
|
|
|
|
|
|
|
|
|
|
before_install:
|
|
|
|
|
- rm lexer.h lexer.c parser.h parser.c
|
|
|
|
|
|
|
|
|
|
install:
|
Adding a .travis.yml file to use the travis-ci.org
From wikipedia:
Travis CI is a hosted, distributed continuous integration service used
to build and test projects hosted at GitHub.
Travis CI is configured by adding a file named .travis.yml, which is a
YAML format text file, to the root directory of the GitHub repository.
Travis CI automatically detects when a commit has been made and pushed
to a GitHub repository that is using Travis CI, and each time this
happens, it will try to build the project and run tests. This includes
commits to all branches, not just to the master branch. When that
process has completed, it will notify a developer in the way it has been
configured to do so — for example, by sending an email containing the
test results (showing success or failure), or by posting a message on an
IRC channel. It can be configured to run the tests on a range of
different machines, with different software installed (such as older
versions of a programming language, to test for compatibility).
2013-12-12 16:23:07 +01:00
|
|
|
- bundle install --gemfile=docs/Gemfile
|
2015-06-20 22:44:09 -07:00
|
|
|
|
|
|
|
|
- wget http://ftp.debian.org/debian/pool/main/b/bison/bison_3.0.2.dfsg-2_amd64.deb
|
|
|
|
|
- ar p bison_3.0.2.dfsg-2_amd64.deb data.tar.xz | tar xJ
|
|
|
|
|
|
|
|
|
|
- wget http://ftp.debian.org/debian/pool/main/libo/libonig/libonig-dev_5.9.6-1_amd64.deb
|
|
|
|
|
- ar p libonig-dev_5.9.6-1_amd64.deb data.tar.xz | tar xJ
|
|
|
|
|
- wget http://ftp.debian.org/debian/pool/main/libo/libonig/libonig2_5.9.6-1_amd64.deb
|
|
|
|
|
- ar p libonig2_5.9.6-1_amd64.deb data.tar.xz | tar xJ
|
|
|
|
|
- mv usr/lib/x86_64-linux-gnu/libonig.so* usr/lib
|
|
|
|
|
|
|
|
|
|
- valgrind --version
|
|
|
|
|
|
|
|
|
|
before_script:
|
Adding a .travis.yml file to use the travis-ci.org
From wikipedia:
Travis CI is a hosted, distributed continuous integration service used
to build and test projects hosted at GitHub.
Travis CI is configured by adding a file named .travis.yml, which is a
YAML format text file, to the root directory of the GitHub repository.
Travis CI automatically detects when a commit has been made and pushed
to a GitHub repository that is using Travis CI, and each time this
happens, it will try to build the project and run tests. This includes
commits to all branches, not just to the master branch. When that
process has completed, it will notify a developer in the way it has been
configured to do so — for example, by sending an email containing the
test results (showing success or failure), or by posting a message on an
IRC channel. It can be configured to run the tests on a range of
different machines, with different software installed (such as older
versions of a programming language, to test for compatibility).
2013-12-12 16:23:07 +01:00
|
|
|
- autoreconf -i
|
2015-06-20 22:44:09 -07:00
|
|
|
- ./configure
|
|
|
|
|
--with-oniguruma=usr
|
|
|
|
|
YACC="usr/bin/bison -y"
|
Adding a .travis.yml file to use the travis-ci.org
From wikipedia:
Travis CI is a hosted, distributed continuous integration service used
to build and test projects hosted at GitHub.
Travis CI is configured by adding a file named .travis.yml, which is a
YAML format text file, to the root directory of the GitHub repository.
Travis CI automatically detects when a commit has been made and pushed
to a GitHub repository that is using Travis CI, and each time this
happens, it will try to build the project and run tests. This includes
commits to all branches, not just to the master branch. When that
process has completed, it will notify a developer in the way it has been
configured to do so — for example, by sending an email containing the
test results (showing success or failure), or by posting a message on an
IRC channel. It can be configured to run the tests on a range of
different machines, with different software installed (such as older
versions of a programming language, to test for compatibility).
2013-12-12 16:23:07 +01:00
|
|
|
|
|
|
|
|
script:
|
2015-06-20 22:44:09 -07:00
|
|
|
- make -j4
|
|
|
|
|
LDFLAGS="-Lusr/lib -R$(pwd)/usr/lib"
|
|
|
|
|
BISON_PKGDATADIR=$(pwd)/usr/share/bison
|
|
|
|
|
- make check -j4
|
|
|
|
|
|
|
|
|
|
after_failure:
|
|
|
|
|
- cat test-suite.log
|
|
|
|
|
- cat tests/*.log
|
Adding a .travis.yml file to use the travis-ci.org
From wikipedia:
Travis CI is a hosted, distributed continuous integration service used
to build and test projects hosted at GitHub.
Travis CI is configured by adding a file named .travis.yml, which is a
YAML format text file, to the root directory of the GitHub repository.
Travis CI automatically detects when a commit has been made and pushed
to a GitHub repository that is using Travis CI, and each time this
happens, it will try to build the project and run tests. This includes
commits to all branches, not just to the master branch. When that
process has completed, it will notify a developer in the way it has been
configured to do so — for example, by sending an email containing the
test results (showing success or failure), or by posting a message on an
IRC channel. It can be configured to run the tests on a range of
different machines, with different software installed (such as older
versions of a programming language, to test for compatibility).
2013-12-12 16:23:07 +01:00
|
|
|
|
|
|
|
|
compiler:
|
|
|
|
|
- gcc
|
|
|
|
|
- clang
|
|
|
|
|
|
|
|
|
|
notifications:
|
|
|
|
|
email: false
|