Build is done manually by the regular build.sh script. All we need is the setup (setting of CXXFLAGS etc.) and the upload part.
This allows to easily run multiple build runs (e.g. in different configurations)
Closes#94
Makes the yaml file shorter and the build table shown by travis easier
to read as there already is a dedicated column for the compiler which is
currently not useful. Furthermore we make the "env" column harder to
read by adding the B2_TOOLSET to it which is kinda redundant when
setting a compiler
* Deduplicate build.sh and enforce.sh
* Unify Windows workflows
* Factor out common linux install script
* Build tests from inside BOOST_ROOT
* Exit with 1 on error on windows
* Remove outdated workaround for Boost.Test #144
* Fix missing unification in BDDE and mingw and add B2_CI_VERSION
* Use B2_CI_VERSION to check for wanted behavior
* Use other methods of getting the CPU count
* Fixes#50
* Update AzP variable defintions
* Zero out B2_CXXFLAGS not CXXFLAGS for bootstrap
* Go back to lib folder on Windows
* Move boost-root to location expected by old AzP configs
This allows the lcov_branch_coverage setting
for code coverage to be configured by the calling
script, by setting the environment variable
LCOV_BRANCH_COVERAGE.
By setting lcov_branch_coverage=0 it is possible to
get full coverage for a library with effort, otherwise
it is difficult to impossible.
The defaulted value continues to be 1 for no change in behaviour.
The `command -v` is a POSIX standard builtin.
https://github.com/koalaman/shellcheck/wiki/SC2230
Although that is not an issue on Linux flavours, checks using empty
string (e.g. for `CXX`) on macOS output.
usage: which [-as] program ...
what displays the non-standard behaviour of `which`. Annoyance.
