aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/project/cmake/build.py (unfollow)
Commit message (Collapse)Author
2021-03-20project.platform: add platform 'auto'Egor Tensin
There were two problems: * On Windows, VS 2019 defaults to x64 while VS 2017 defaults to x86. * Too much focus on x86(-64) might mean that building stuff on ARM can become difficult. These were all addressed by adding a new platform 'auto'. On Windows, it defaults to picking either x64 or x86 (depending on the host arch) for both Boost and CMake. On Linux, it lets the compiler decide what arch to target.
2021-03-14project.boost.download: create missing directoriesEgor Tensin
2021-01-19project.cmake: --toolset auto shouldn't set any compiler flagsEgor Tensin
2021-01-18project.cmake: create the build dir if necessaryEgor Tensin
2021-01-17GIANT CLUSTERFUCK OF A COMMITEgor Tensin
OK, this is epic. I was basically just trying to a) support Clang and b) add more test coverage. _THREE MONTHS_ and a few hundred CI runs later, this is what I came up with. I don't know how it ended up being what it is, but here we go. Some highlights of the changes: 1) CI builds has been moved to GitHub Actions, 2) the entire notion of a toolchain has been reworked; it now supports Clang on all platforms. * .github: this directory contains the GitHub Actions workflow scripts/actions. In the process, I created like 6 external GitHub actions, but it's still pretty massive. An upside is that it covers much more platform/toolchain combinations _and_ check a lot of the expected post-conditions. TODO: .ci/Makefile is obsolete now, as well as .travis.yml and .appveyor.yml. * common.cmake: added Clang support. In the process, a great deal has been learned about how CMake works; in particular, static runtime support has been reworked to be more robust. * project: the entire notion of a "toolchain" has been reworked. Instead of a measly --mingw parameter, there's now a separate --toolset parameter, which allows you to choose between GCC, Clang, MSVC, etc. Both Boost and CMake build scripts were enhanced greatly to support Clang and other toolchains in a more robust way.
2020-03-30project.cmake: make it --boost awareEgor Tensin
2020-03-30project.cmake: make it --platform awareEgor Tensin
2020-03-30project.cmake.build: refactoringEgor Tensin
2020-03-30project: minor-ish refactoringEgor Tensin
2020-03-29project: add os.pyEgor Tensin
2020-03-29fix READMEs, code style, etc.Egor Tensin
2020-03-29project.cmake: insignificant refactoringEgor Tensin
2020-03-29project.cmake: factor out common utilsEgor Tensin
2020-03-28project.boost: factor out Configuration/Platform/LinkageEgor Tensin
2020-03-28WIP: restructureEgor Tensin
A stupid attempt to reduce code duplication led me to believe that all the scripts could use _a bit_ of refactoring. This is going to be a major pain (factoring out all the things), which I'll take gladly. All the links and usage examples are broken right now, but nobody cares, so whatevs.
2020-01-18support all 4 cmake default configurationsEgor Tensin
2020-01-09better usage messages & READMEsEgor Tensin
2020-01-08fix PyLint-discovered bugsEgor Tensin
2020-01-07cmake/build: remove the --clean parameterEgor Tensin
2020-01-03rearrange all files completelyEgor Tensin
2020-01-01ci/build.py: split -D from its argumentEgor Tensin
2019-12-15build: clean up silly cmd line paramsEgor Tensin
They were just plain synonyms for CMake flags, barely had any value.
2019-12-14fix PyLint warningsEgor Tensin
2019-12-13build/ -> ci/Egor Tensin
2019-12-13build/boost: add generic build.py scriptEgor Tensin
2019-12-10add simple build scriptsEgor Tensin
They're intended to replace my build.sh (for Travis) and build.ps1 (for AppVeyor) scripts to call CMake in a platform-independent manner.