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

	Commit message (Collapse)	Author	Age
*	use default settings for Black	Egor Tensin	2026-06-23
\|
*	update my email	Egor Tensin	2026-05-17
\|
*	reformat everything for fun	Egor Tensin	2026-05-17
\|
*	fix PyLint warnings	Egor Tensin	2026-03-30
\|
*	boost: root/ -> install_dir/	Egor Tensin	2026-03-29
\|
*	project.boost: finalize transition from `stage` to `install`	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.
*	project.toolset: refactoring	Egor Tensin	2021-05-07
\|
*	brush up import lists	Egor Tensin	2021-05-06
\|
*	"toolchain" -> "toolset", part 2	Egor Tensin	2021-05-06
\|
*	project: minor refactoring	Egor Tensin	2021-03-20
\|
*	project.platform: add platform 'auto'	Egor Tensin	2021-03-20
\| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	fix PyLint warnings	Egor Tensin	2021-01-17
\|
*	project.cmake: make it --platform aware	Egor Tensin	2020-03-30
\|
*	project: minor-ish refactoring	Egor Tensin	2020-03-30
\|
*	project.boost: factor out Configuration/Platform/Linkage	Egor Tensin	2020-03-28