You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
use c++11 std::align from <memory> (#2026)
* use c++11 std::align from <memory>
* for Ubuntu, use gcc5 instead of 4.8
* use travis to set gcc to 5
eval
and sudo
* use eval in .travis.yml
* use gcc-8
* replace precise with trusty llvm toolchain, because we have been using trusty for awhile now
* push things to matrix, so we can support multiple releases if we want
* we should not be allowing for failures, we are ready to start trusting clang and its analyzer
* scan-build was pushed to another package
* use gcc-8 still but wrap in scan-build
* travis.yml cleanup, have output of scripts go to stdout, make search for substring a regex
use double []
fix missing ,
use bash to use regex
black spaces matter
* set human readable names for our various builds, split out our static analysis between openmw and openmw-cs
* test if not set, then set otherwise ignore
* use quotes
* do not eval it, set it in travis env
* no more &&
* what does clang7 have to say?
* use sourceline for now
* use clang-7 instead of clang-7.0
* yes, llvm-toolchain-trusty-7 not llvm-toolchain-trusty-7.0
* for static analysis, openmw is compiled and checked on its own while openmw-cs is build with all the rest. this might change in the future.
and actually do it the other way around
6 years ago
|
|
|
#!/bin/bash -ex
|
|
|
|
|
|
|
|
free -m
|
|
|
|
|
|
|
|
env GENERATOR='Unix Makefiles' CONFIGURATION=Release CI/build_googletest.sh
|
|
|
|
GOOGLETEST_DIR="$(pwd)/googletest/build"
|
|
|
|
|
|
|
|
mkdir build
|
|
|
|
cd build
|
use c++11 std::align from <memory> (#2026)
* use c++11 std::align from <memory>
* for Ubuntu, use gcc5 instead of 4.8
* use travis to set gcc to 5
eval
and sudo
* use eval in .travis.yml
* use gcc-8
* replace precise with trusty llvm toolchain, because we have been using trusty for awhile now
* push things to matrix, so we can support multiple releases if we want
* we should not be allowing for failures, we are ready to start trusting clang and its analyzer
* scan-build was pushed to another package
* use gcc-8 still but wrap in scan-build
* travis.yml cleanup, have output of scripts go to stdout, make search for substring a regex
use double []
fix missing ,
use bash to use regex
black spaces matter
* set human readable names for our various builds, split out our static analysis between openmw and openmw-cs
* test if not set, then set otherwise ignore
* use quotes
* do not eval it, set it in travis env
* no more &&
* what does clang7 have to say?
* use sourceline for now
* use clang-7 instead of clang-7.0
* yes, llvm-toolchain-trusty-7 not llvm-toolchain-trusty-7.0
* for static analysis, openmw is compiled and checked on its own while openmw-cs is build with all the rest. this might change in the future.
and actually do it the other way around
6 years ago
|
|
|
|
|
|
|
${ANALYZE} cmake \
|
|
|
|
-DCMAKE_C_COMPILER="${CC}" \
|
|
|
|
-DCMAKE_CXX_COMPILER="${CXX}" \
|
|
|
|
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
|
|
|
|
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
|
|
|
|
-DBUILD_UNITTESTS=TRUE \
|
|
|
|
-DUSE_SYSTEM_TINYXML=TRUE \
|
|
|
|
-DCMAKE_INSTALL_PREFIX="/usr" \
|
|
|
|
-DBINDIR="/usr/games" \
|
|
|
|
-DCMAKE_BUILD_TYPE="DEBUG" \
|
|
|
|
-DGTEST_ROOT="${GOOGLETEST_DIR}" \
|
|
|
|
-DGMOCK_ROOT="${GOOGLETEST_DIR}" \
|
|
|
|
..
|