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

	Commit message (Collapse)	Author	Age
*	move testing-only things into test/	Egor Tensin	2026-03-30
\|
*	project.boost.build: saner command line options	Egor Tensin	2026-03-29
\|
*	boost: root/ -> install_dir/	Egor Tensin	2026-03-29
\|
*	project.build: make arguments sane	Egor Tensin	2026-02-02
\|
*	project.boost: switch from `stage` to `install`	Egor Tensin	2026-01-20
\| \| \| \| \| \| \| \| \|	That's part of a global transition aiming to switch to Boost CMake files. Since 1.70.0, they've been releasing CMake files, which I should (?) be using. Additionally, modern CMake versions simply deprecate the FindBoost module (see policy CMP0167), insisting on using the supplied CMake files. I'll try to continue supporting old Boost versions; let's see how it goes.
*	drop Cygwin, it's obsolete	Egor Tensin	2025-12-29
\|
*	actions/check-runtime-library: locate objdump on Windows	Egor Tensin	2023-11-05
\|
*	actions/software-environment: print objdump path	Egor Tensin	2023-11-05
\|
*	common.cmake: bump default C++ standard	Egor Tensin	2023-07-04
\|
*	project.cmake.build -> project.build	Egor Tensin	2023-07-03
\| \| \| \|	Accordingly, rename cmake-build to project-build.
*	project.cmake: require the build dir argument	Egor Tensin	2023-07-03
\| \| \| \| \| \|	It doesn't make a lot of sense for the build dir argument to be optional. There's still a placeholder you can use to build in a temporary directory.
*	actions/check-runtime-library: fix linked libs on Windows again	Egor Tensin	2023-06-30
\| \| \| \| \| \|	On Windows 2022, MinGW now links to api-ms-win-crt-* libraries; keeping track of that becomes too burdensome, so I'll switch to a black-list of libraries rather than a white-list.
*	actions/check-runtime-library: fix linked libs on Windows	Egor Tensin	2023-03-12
\| \| \| \| \|	Apparently, MinGW doesn't link to either ucrtbase.dll or msvcrt.dll at all on Windows.
*	actions/check-runtime-library: msvcrt.dll -> ucrtbase.dll	Egor Tensin	2023-01-02
\|
*	actions/build-example: set-output is deprecated	Egor Tensin	2023-01-02
\|
*	actions/check-boost-bootstrapped: only print bootstrap.log if it's there	Egor Tensin	2021-12-16
\|
*	project.boost.download: add --no-retry parameter	Egor Tensin	2021-05-03
\| \| \| \| \|	This is to facilitate testing mostly, but still required substantion refactoring.
*	add GitHub workflow to check Boost CDNs	Egor Tensin	2021-05-03
\|
*	actions/build-boost: no more --verbose, it's stable	Egor Tensin	2021-04-24
\|
*	workflows: cache Boost downloads	Egor Tensin	2021-03-13
\|
*	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.