mirrors/hyperrogue
1
0
Fork 0
mirror of https://github.com/zenorogue/hyperrogue.git synced 2024-12-19 07:20:25 +00:00
Code Issues Releases Wiki Activity
e992c6a3cd
hyperrogue/.travis.yml

208 lines
5.3 KiB
YAML
Raw Normal View History

Add travis config
2018-06-25 20:28:41 +00:00
language: cpp
TravisCI and Makefile integration for the emscripten build! For testing the emscripten build in TravisCI, it looks like some arcane combination of node + Browserify + the wasmify plugin + maybe some other stuff *might* work, but I have no real idea yet. For grabbing the build artifacts from Travis, you can temporarily insert lines into the .travis.yml such as curl --upload-file ./hyper.html https://transfer.sh/hyper.html curl --upload-file ./hyper.js https://transfer.sh/hyper.js curl --upload-file ./hyper.wasm https://transfer.sh/hyper.wasm However, "hyper.wasm" is about 2.8 megabytes in size, so this hack definitely should never become part of the *master* `.travis.yml`.
2018-06-27 01:55:19 +00:00
services:
- docker
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
matrix:
include:
- os: linux
compiler: gcc
env: >-
TRAVIS_OS_NAME=linux
TRAVIS_COMPILER_NAME=gcc
TRAVIS_BUILD_SYSTEM=autotools
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
- os: osx
compiler: clang
env: >-
TRAVIS_OS_NAME=osx
TRAVIS_COMPILER_NAME=clang
TRAVIS_BUILD_SYSTEM=autotools
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
- os: linux
compiler: gcc
env: >-
TRAVIS_OS_NAME=linux
TRAVIS_COMPILER_NAME=gcc
TRAVIS_BUILD_SYSTEM=Makefile
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
- os: linux
compiler: clang
env: >-
TRAVIS_OS_NAME=linux
TRAVIS_COMPILER_NAME=clang
TRAVIS_BUILD_SYSTEM=Makefile
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
Get the build green again. Fix a bug in the Travis config. The `HYPERROGUE_USE_ROGUEVIZ=1` build now uses inline variables. So we pass `-std=c++17` in the Makefile. But GCC 5.4.0 (Travis's default system compiler on Ubuntu Xenial) doesn't recognize inline variables even in `-std=c++17` mode. Therefore, we must pass `dist: bionic` to Travis, to get it to use Ubuntu Bionic, whose system compiler is GCC 7.4.0. But we do this only for the one entry in the build matrix that builds RogueViz with GCC on Linux. Nobody else needs `dist: bionic`. The bug was that my hack to support `g++-5` accidentally prevented Travis from ever using `clang++`! So all our "Clang" builds were quietly using regular `g++` instead. This is now fixed, and in fact I've removed the `g++-5` build because its GCC 5.5.0 is not significantly different from the regular `g++` build's GCC 5.4.0. Also, add two more configurations to the build matrix. Since `HYPERROGUE_USE_ROGUEVIZ=1` now uses `-std=c++17`, we want to make sure that we run builds on every platform both with `HYPERROGUE_USE_ROGUEVIZ=1` (to prove that the RogueViz code compiles) and without (to prove that the non-RogueViz code still compiles as `-std=c++11`).
2020-04-03 19:11:12 +00:00
- os: linux
dist: bionic
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
compiler: gcc
env: >-
Get the build green again. Fix a bug in the Travis config. The `HYPERROGUE_USE_ROGUEVIZ=1` build now uses inline variables. So we pass `-std=c++17` in the Makefile. But GCC 5.4.0 (Travis's default system compiler on Ubuntu Xenial) doesn't recognize inline variables even in `-std=c++17` mode. Therefore, we must pass `dist: bionic` to Travis, to get it to use Ubuntu Bionic, whose system compiler is GCC 7.4.0. But we do this only for the one entry in the build matrix that builds RogueViz with GCC on Linux. Nobody else needs `dist: bionic`. The bug was that my hack to support `g++-5` accidentally prevented Travis from ever using `clang++`! So all our "Clang" builds were quietly using regular `g++` instead. This is now fixed, and in fact I've removed the `g++-5` build because its GCC 5.5.0 is not significantly different from the regular `g++` build's GCC 5.4.0. Also, add two more configurations to the build matrix. Since `HYPERROGUE_USE_ROGUEVIZ=1` now uses `-std=c++17`, we want to make sure that we run builds on every platform both with `HYPERROGUE_USE_ROGUEVIZ=1` (to prove that the RogueViz code compiles) and without (to prove that the non-RogueViz code still compiles as `-std=c++11`).
2020-04-03 19:11:12 +00:00
TRAVIS_OS_NAME=linux
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
TRAVIS_COMPILER_NAME=gcc
TRAVIS_BUILD_SYSTEM=Makefile
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
HYPERROGUE_USE_ROGUEVIZ=1
Get the build green again. Fix a bug in the Travis config. The `HYPERROGUE_USE_ROGUEVIZ=1` build now uses inline variables. So we pass `-std=c++17` in the Makefile. But GCC 5.4.0 (Travis's default system compiler on Ubuntu Xenial) doesn't recognize inline variables even in `-std=c++17` mode. Therefore, we must pass `dist: bionic` to Travis, to get it to use Ubuntu Bionic, whose system compiler is GCC 7.4.0. But we do this only for the one entry in the build matrix that builds RogueViz with GCC on Linux. Nobody else needs `dist: bionic`. The bug was that my hack to support `g++-5` accidentally prevented Travis from ever using `clang++`! So all our "Clang" builds were quietly using regular `g++` instead. This is now fixed, and in fact I've removed the `g++-5` build because its GCC 5.5.0 is not significantly different from the regular `g++` build's GCC 5.4.0. Also, add two more configurations to the build matrix. Since `HYPERROGUE_USE_ROGUEVIZ=1` now uses `-std=c++17`, we want to make sure that we run builds on every platform both with `HYPERROGUE_USE_ROGUEVIZ=1` (to prove that the RogueViz code compiles) and without (to prove that the non-RogueViz code still compiles as `-std=c++11`).
2020-04-03 19:11:12 +00:00
- os: linux
compiler: clang
env: >-
TRAVIS_OS_NAME=linux
TRAVIS_COMPILER_NAME=clang
TRAVIS_BUILD_SYSTEM=Makefile
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
HYPERROGUE_USE_ROGUEVIZ=1
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
- os: osx
compiler: clang
env: >-
TRAVIS_OS_NAME=osx
TRAVIS_COMPILER_NAME=clang
TRAVIS_BUILD_SYSTEM=Makefile
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
Get the build green again. Fix a bug in the Travis config. The `HYPERROGUE_USE_ROGUEVIZ=1` build now uses inline variables. So we pass `-std=c++17` in the Makefile. But GCC 5.4.0 (Travis's default system compiler on Ubuntu Xenial) doesn't recognize inline variables even in `-std=c++17` mode. Therefore, we must pass `dist: bionic` to Travis, to get it to use Ubuntu Bionic, whose system compiler is GCC 7.4.0. But we do this only for the one entry in the build matrix that builds RogueViz with GCC on Linux. Nobody else needs `dist: bionic`. The bug was that my hack to support `g++-5` accidentally prevented Travis from ever using `clang++`! So all our "Clang" builds were quietly using regular `g++` instead. This is now fixed, and in fact I've removed the `g++-5` build because its GCC 5.5.0 is not significantly different from the regular `g++` build's GCC 5.4.0. Also, add two more configurations to the build matrix. Since `HYPERROGUE_USE_ROGUEVIZ=1` now uses `-std=c++17`, we want to make sure that we run builds on every platform both with `HYPERROGUE_USE_ROGUEVIZ=1` (to prove that the RogueViz code compiles) and without (to prove that the non-RogueViz code still compiles as `-std=c++11`).
2020-04-03 19:11:12 +00:00
- os: osx
compiler: gcc
env: >-
TRAVIS_OS_NAME=osx
TRAVIS_COMPILER_NAME=gcc
TRAVIS_BUILD_SYSTEM=Makefile
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
HYPERROGUE_USE_ROGUEVIZ=1
- os: osx
compiler: clang
env: >-
TRAVIS_OS_NAME=osx
TRAVIS_COMPILER_NAME=clang
TRAVIS_BUILD_SYSTEM=Makefile
Get the build green again. Fix a bug in the Travis config. The `HYPERROGUE_USE_ROGUEVIZ=1` build now uses inline variables. So we pass `-std=c++17` in the Makefile. But GCC 5.4.0 (Travis's default system compiler on Ubuntu Xenial) doesn't recognize inline variables even in `-std=c++17` mode. Therefore, we must pass `dist: bionic` to Travis, to get it to use Ubuntu Bionic, whose system compiler is GCC 7.4.0. But we do this only for the one entry in the build matrix that builds RogueViz with GCC on Linux. Nobody else needs `dist: bionic`. The bug was that my hack to support `g++-5` accidentally prevented Travis from ever using `clang++`! So all our "Clang" builds were quietly using regular `g++` instead. This is now fixed, and in fact I've removed the `g++-5` build because its GCC 5.5.0 is not significantly different from the regular `g++` build's GCC 5.4.0. Also, add two more configurations to the build matrix. Since `HYPERROGUE_USE_ROGUEVIZ=1` now uses `-std=c++17`, we want to make sure that we run builds on every platform both with `HYPERROGUE_USE_ROGUEVIZ=1` (to prove that the RogueViz code compiles) and without (to prove that the non-RogueViz code still compiles as `-std=c++11`).
2020-04-03 19:11:12 +00:00
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
HYPERROGUE_USE_ROGUEVIZ=1
TravisCI and Makefile integration for the emscripten build! For testing the emscripten build in TravisCI, it looks like some arcane combination of node + Browserify + the wasmify plugin + maybe some other stuff *might* work, but I have no real idea yet. For grabbing the build artifacts from Travis, you can temporarily insert lines into the .travis.yml such as curl --upload-file ./hyper.html https://transfer.sh/hyper.html curl --upload-file ./hyper.js https://transfer.sh/hyper.js curl --upload-file ./hyper.wasm https://transfer.sh/hyper.wasm However, "hyper.wasm" is about 2.8 megabytes in size, so this hack definitely should never become part of the *master* `.travis.yml`.
2018-06-27 01:55:19 +00:00
- os: linux
env: >-
TRAVIS_OS_NAME=linux
TRAVIS_COMPILER_NAME=emscripten
TRAVIS_BUILD_SYSTEM=emscripten
Make "mymake" work on OSX, and add it to Travis. Fix a -Wformat bug exposed by compiling with Clang. To preprocess C++11 code, you need `g++ -E -std=c++11`, not just `g++ -E`. (The old code worked for GCC 6+ and Clang 6+ because they changed the default mode from C++03 to C++14. But for GCC 5, we still need `-std=c++11`. And regardless, it's a good idea.) Add a "-mac" option to mymake, and cleanly factor out `set_mac`, `set_linux`, and `set_win`. When you build mymake using `make -f Makefile.simple mymake`, you get a mymake that knows what platform it's on. This means you don't have to pass `mymake -mac` on OSX, nor `mymake -win` on Windows. The old code put `INCLUDE(___hyper-main.cpp)` into a C++ file that would be preprocessed, which doesn't work because libSDL does essentially `-Dmain=SDL_main`, which turns this into `INCLUDE(___hyper-SDL_main.cpp)`, which gives us a "file not found" error from mymake. The solution is to put filenames into quotation marks, so that the string "main" never appears as a token in the C++ file. (Alternatively, we could have renamed "hyper-main.cpp" to "hypermain.cpp".) Add several new "mymake" entries in the Travis build matrix, and add the "mymake" builds' badge to the README.
2020-04-04 02:01:26 +00:00
- os: osx
compiler: clang
env: >-
TRAVIS_OS_NAME=osx
TRAVIS_COMPILER_NAME=clang
TRAVIS_BUILD_SYSTEM=mymake
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
- os: osx
compiler: clang
env: >-
TRAVIS_OS_NAME=osx
TRAVIS_COMPILER_NAME=clang
TRAVIS_BUILD_SYSTEM=mymake
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
HYPERROGUE_USE_ROGUEVIZ=1
- os: linux
compiler: gcc
env: >-
TRAVIS_OS_NAME=linux
TRAVIS_COMPILER_NAME=gcc
TRAVIS_BUILD_SYSTEM=mymake
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
- os: linux
dist: bionic
compiler: gcc
env: >-
TRAVIS_OS_NAME=linux
TRAVIS_COMPILER_NAME=gcc
TRAVIS_BUILD_SYSTEM=mymake
HYPERROGUE_USE_GLEW=1
HYPERROGUE_USE_PNG=1
HYPERROGUE_USE_ROGUEVIZ=1
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
Expand the TravisCI integration to test autotools on both Linux and OSX.
2018-07-01 00:57:28 +00:00
before_install:
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
- |-
# Install SDL
if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then
sudo apt-get update -qq
sudo apt-get install -qq libsdl1.2-dev libsdl-gfx1.2-dev libsdl-mixer1.2-dev libsdl-ttf2.0-dev
elif [[ "$TRAVIS_OS_NAME" == "osx" ]]; then
brew update
brew install sdl sdl_gfx sdl_mixer sdl_ttf
# work around https://stackoverflow.com/questions/51034399/ for now
(cd /usr/local/include && ln -sf SDL/SDL.h)
else
exit 'Unsupported OS'
fi
- |-
# Install GLEW if asked for
if [[ "$HYPERROGUE_USE_GLEW" == "1" ]]; then
if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then
sudo apt-get install -qq libglew-dev
elif [[ "$TRAVIS_OS_NAME" == "osx" ]]; then
brew install glew
else
exit 'Unsupported OS'
fi
fi
- |-
# Install libpng if asked for
if [[ "$HYPERROGUE_USE_PNG" == "1" ]]; then
if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then
echo 'libpng is installed by default'
elif [[ "$TRAVIS_OS_NAME" == "osx" ]]; then
brew install libpng
else
exit 'Unsupported OS'
fi
fi
- |-
# Install autotools if asked for
if [[ "$TRAVIS_USE_AUTOTOOLS" == "1" ]]; then
if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then
echo 'autotools is installed by default'
elif [[ "$TRAVIS_OS_NAME" == "osx" ]]; then
brew install automake
else
exit 'Unsupported OS'
Expand the TravisCI integration to test autotools on both Linux and OSX.
2018-07-01 00:57:28 +00:00
fi
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
fi
Add travis config
2018-06-25 20:28:41 +00:00
script:
Expand the TravisCI integration to test autotools on both Linux and OSX.
2018-07-01 00:57:28 +00:00
- |-
# Build hyperrogue.
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
if [[ "$TRAVIS_BUILD_SYSTEM" == "autotools" ]]; then
autoreconf -vi
Add `-pedantic` to the compiler options, and clean up some cruft.
2020-02-22 05:20:08 +00:00
./configure CXXFLAGS="-W -Wall -Wextra -Werror -Wno-unused-parameter -Wno-maybe-uninitialized -Wno-unknown-warning-option"
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
make
elif [[ "$TRAVIS_BUILD_SYSTEM" == "Makefile" ]]; then
Get the build green again. Fix a bug in the Travis config. The `HYPERROGUE_USE_ROGUEVIZ=1` build now uses inline variables. So we pass `-std=c++17` in the Makefile. But GCC 5.4.0 (Travis's default system compiler on Ubuntu Xenial) doesn't recognize inline variables even in `-std=c++17` mode. Therefore, we must pass `dist: bionic` to Travis, to get it to use Ubuntu Bionic, whose system compiler is GCC 7.4.0. But we do this only for the one entry in the build matrix that builds RogueViz with GCC on Linux. Nobody else needs `dist: bionic`. The bug was that my hack to support `g++-5` accidentally prevented Travis from ever using `clang++`! So all our "Clang" builds were quietly using regular `g++` instead. This is now fixed, and in fact I've removed the `g++-5` build because its GCC 5.5.0 is not significantly different from the regular `g++` build's GCC 5.4.0. Also, add two more configurations to the build matrix. Since `HYPERROGUE_USE_ROGUEVIZ=1` now uses `-std=c++17`, we want to make sure that we run builds on every platform both with `HYPERROGUE_USE_ROGUEVIZ=1` (to prove that the RogueViz code compiles) and without (to prove that the non-RogueViz code still compiles as `-std=c++11`).
2020-04-03 19:11:12 +00:00
make -f Makefile.simple
Make "mymake" work on OSX, and add it to Travis. Fix a -Wformat bug exposed by compiling with Clang. To preprocess C++11 code, you need `g++ -E -std=c++11`, not just `g++ -E`. (The old code worked for GCC 6+ and Clang 6+ because they changed the default mode from C++03 to C++14. But for GCC 5, we still need `-std=c++11`. And regardless, it's a good idea.) Add a "-mac" option to mymake, and cleanly factor out `set_mac`, `set_linux`, and `set_win`. When you build mymake using `make -f Makefile.simple mymake`, you get a mymake that knows what platform it's on. This means you don't have to pass `mymake -mac` on OSX, nor `mymake -win` on Windows. The old code put `INCLUDE(___hyper-main.cpp)` into a C++ file that would be preprocessed, which doesn't work because libSDL does essentially `-Dmain=SDL_main`, which turns this into `INCLUDE(___hyper-SDL_main.cpp)`, which gives us a "file not found" error from mymake. The solution is to put filenames into quotation marks, so that the string "main" never appears as a token in the C++ file. (Alternatively, we could have renamed "hyper-main.cpp" to "hypermain.cpp".) Add several new "mymake" entries in the Travis build matrix, and add the "mymake" builds' badge to the README.
2020-04-04 02:01:26 +00:00
elif [[ "$TRAVIS_BUILD_SYSTEM" == "mymake" ]]; then
make -f Makefile.simple mymake
if [[ "$HYPERROGUE_USE_ROGUEVIZ" == "1" ]]; then
./mymake -rv
else
./mymake
fi
TravisCI and Makefile integration for the emscripten build! For testing the emscripten build in TravisCI, it looks like some arcane combination of node + Browserify + the wasmify plugin + maybe some other stuff *might* work, but I have no real idea yet. For grabbing the build artifacts from Travis, you can temporarily insert lines into the .travis.yml such as curl --upload-file ./hyper.html https://transfer.sh/hyper.html curl --upload-file ./hyper.js https://transfer.sh/hyper.js curl --upload-file ./hyper.wasm https://transfer.sh/hyper.wasm However, "hyper.wasm" is about 2.8 megabytes in size, so this hack definitely should never become part of the *master* `.travis.yml`.
2018-06-27 01:55:19 +00:00
elif [[ "$TRAVIS_BUILD_SYSTEM" == "emscripten" ]]; then
docker run --rm -v $(pwd):/src trzeci/emscripten make -f Makefile.simple emscripten
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
else
exit 'Unsupported build system'
fi
Expand the TravisCI integration to test autotools on both Linux and OSX.
2018-07-01 00:57:28 +00:00
- |-
# Test hyperrogue.
TravisCI and Makefile integration for the emscripten build! For testing the emscripten build in TravisCI, it looks like some arcane combination of node + Browserify + the wasmify plugin + maybe some other stuff *might* work, but I have no real idea yet. For grabbing the build artifacts from Travis, you can temporarily insert lines into the .travis.yml such as curl --upload-file ./hyper.html https://transfer.sh/hyper.html curl --upload-file ./hyper.js https://transfer.sh/hyper.js curl --upload-file ./hyper.wasm https://transfer.sh/hyper.wasm However, "hyper.wasm" is about 2.8 megabytes in size, so this hack definitely should never become part of the *master* `.travis.yml`.
2018-06-27 01:55:19 +00:00
if [[ "$TRAVIS_BUILD_SYSTEM" == "emscripten" ]]; then
ls -lAF hyper.html hyper.js hyper.wasm
Make "mymake" work on OSX, and add it to Travis. Fix a -Wformat bug exposed by compiling with Clang. To preprocess C++11 code, you need `g++ -E -std=c++11`, not just `g++ -E`. (The old code worked for GCC 6+ and Clang 6+ because they changed the default mode from C++03 to C++14. But for GCC 5, we still need `-std=c++11`. And regardless, it's a good idea.) Add a "-mac" option to mymake, and cleanly factor out `set_mac`, `set_linux`, and `set_win`. When you build mymake using `make -f Makefile.simple mymake`, you get a mymake that knows what platform it's on. This means you don't have to pass `mymake -mac` on OSX, nor `mymake -win` on Windows. The old code put `INCLUDE(___hyper-main.cpp)` into a C++ file that would be preprocessed, which doesn't work because libSDL does essentially `-Dmain=SDL_main`, which turns this into `INCLUDE(___hyper-SDL_main.cpp)`, which gives us a "file not found" error from mymake. The solution is to put filenames into quotation marks, so that the string "main" never appears as a token in the C++ file. (Alternatively, we could have renamed "hyper-main.cpp" to "hypermain.cpp".) Add several new "mymake" entries in the Travis build matrix, and add the "mymake" builds' badge to the README.
2020-04-04 02:01:26 +00:00
elif [[ "$TRAVIS_BUILD_SYSTEM" == "mymake" ]]; then
./hyper --help
TravisCI and Makefile integration for the emscripten build! For testing the emscripten build in TravisCI, it looks like some arcane combination of node + Browserify + the wasmify plugin + maybe some other stuff *might* work, but I have no real idea yet. For grabbing the build artifacts from Travis, you can temporarily insert lines into the .travis.yml such as curl --upload-file ./hyper.html https://transfer.sh/hyper.html curl --upload-file ./hyper.js https://transfer.sh/hyper.js curl --upload-file ./hyper.wasm https://transfer.sh/hyper.wasm However, "hyper.wasm" is about 2.8 megabytes in size, so this hack definitely should never become part of the *master* `.travis.yml`.
2018-06-27 01:55:19 +00:00
else
./hyperrogue --help
fi
Expand the TravisCI integration to test autotools on both Linux and OSX.
2018-07-01 00:57:28 +00:00
- |-
# Test "make dist". ("make distcheck" is expected to fail.)
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
if [[ "$TRAVIS_BUILD_SYSTEM" == "autotools" ]]; then make dist; fi
Expand the TravisCI integration to test autotools on both Linux and OSX.
2018-07-01 00:57:28 +00:00
- |-
# Test "sudo make install".
Merge Makefile.{mac,mgw} into Makefile.simple. https://travis-ci.org/Quuxplusone/hyperrogue
2018-06-26 02:26:48 +00:00
if [[ "$TRAVIS_BUILD_SYSTEM" == "autotools" ]]; then sudo make install; fi
Reference in New Issue Copy Permalink