Name |
Last commit
|
Last update |
---|---|---|
.. | ||
build.ps1 | ||
build.sh | ||
coverity-build.sh | ||
coverity-publish.sh | ||
setup-linux.sh | ||
setup-mingw.ps1 | ||
setup-osx.sh | ||
test.ps1 | ||
test.sh |
We currently unconditionally override the PATH variable with a custom path with the main intent of making available our own custom MinGW installation. This worked quite well so far, but is heavily dependent on the machine we're running this on. And naturally, it fails on the new Windows machines we need to upgrade to, as tools like CMake are not contained in the path we currently set up. Fix this by remodeling the way we set up the PATH environment. Instead of overriding it completely, we now override it only when executing the CMake build.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
build.ps1 | Loading commit data... | |
build.sh | Loading commit data... | |
coverity-build.sh | Loading commit data... | |
coverity-publish.sh | Loading commit data... | |
setup-linux.sh | Loading commit data... | |
setup-mingw.ps1 | Loading commit data... | |
setup-osx.sh | Loading commit data... | |
test.ps1 | Loading commit data... | |
test.sh | Loading commit data... |