cmake-common - Utilities to help develop C++/CMake projects

	Commit message (Collapse)	Author	Age
...
*	remove excessive logging & obsolete project.ci.* packages	Egor Tensin	2021-04-13
\| \| \| \|	Logging command line arguments before parsing them is a bit excessive.
*	tools: drop the .py extension	Egor Tensin	2021-04-13
\|
*	workflows/basic: add job for publishing to PyPI	Egor Tensin	2021-04-13
\|
*	workflows/basic: call clang-format.py	Egor Tensin	2021-04-05
\|
*	project.ci: use same variable names for all CIs	Egor Tensin	2021-03-24
\| \| \| \|	Using different ones was quite weird to begin with.
*	project.ci: change build directory	Egor Tensin	2021-03-24
\| \| \| \|	It's now <source directory>/../build for consistency.
*	workflows: fail-fast	Egor Tensin	2021-03-20
\| \| \| \|	They are stable enough.
*	workflows/basic: enable on windows-2016	Egor Tensin	2021-03-19
\|
*	workflows/ci_appveyor: create C:\projects before caching	Egor Tensin	2021-03-14
\|
*	workflows: _really_ fix Boost caching?..	Egor Tensin	2021-03-14
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	actions/cache@v2 doesn't work on windows-2016 images, since those contain the GNU tar, which cannot work with \ as path separator. This was fixed in package @actions/cache v1.0.5, which is used by action actions/cache@v2.1.4 [1][2]. In addition, it simply couldn't find tar.exe on those images thanks to my action cleanup-path, which removed the corresponding directory (I think it was Git's bin/) from PATH. It worked for windows-2019 images thanks to them containing tar.exe in System32. Solved by turning cleanup-path into a JavaScript action with a "post" step, which restores the original PATH value. [1]: https://github.com/actions/virtual-environments/issues/480 [2]: https://github.com/actions/toolkit/issues/632
*	project.ci: cache Boost downloads	Egor Tensin	2021-03-13
\|
*	workflows: fix Boost caching	Egor Tensin	2021-03-13
\| \| \| \|	It seemingly doesn't work unless the key includes runner.os?
*	workflows: cache Boost downloads	Egor Tensin	2021-03-13
\|
*	project.ci: auto-fill --toolset from environment	Egor Tensin	2021-01-25
\|
*	project.ci: auto-detect CI system	Egor Tensin	2021-01-25
\|
*	bye-bye, Travis & AppVeyor!no_more_travis	Egor Tensin	2021-01-19
\|
*	project.ci: add GitHub Actions	Egor Tensin	2021-01-18
\|
*	project.ci: --install picks the directory automatically	Egor Tensin	2021-01-18
\|
*	workflows: add Travis/AppVeyor simulations	Egor Tensin	2021-01-18
\|
*	workflows: add "Basic usage"	Egor Tensin	2021-01-18
\|
*	workflows: mask the less interesting ones	Egor Tensin	2021-01-18
\|
*	workflows: check if Travis/AppVeyor are broken	Egor Tensin	2021-01-17
\|
*	GIANT CLUSTERFUCK OF A COMMIT	Egor Tensin	2021-01-17
	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.