OpenMW/CI/before_install.linux.sh

#!/bin/bash -ex

sudo ln -sf /usr/bin/clang-10 /usr/local/bin/clang
sudo ln -sf /usr/bin/clang++-10 /usr/local/bin/clang++
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 2018-11-08 16:38:09 +00:00			`#!/bin/bash -ex`

bump to bionic; gcc-9 and clang-10 2020-03-22 19:56:48 +00:00			`sudo ln -sf /usr/bin/clang-10 /usr/local/bin/clang`
			`sudo ln -sf /usr/bin/clang++-10 /usr/local/bin/clang++`