project.build: fix for CMP0144

2026-05-17T15:32:41Z

At least I hope that it is.

update my email

2026-05-17T11:15:21Z

add .git-blame-ignore-revs

2026-05-17T11:05:26Z

reformat everything for fun

2026-05-17T11:02:51Z

workflows: add Python black run

2026-05-17T10:55:19Z

workflows: reschedule for my convenience

2026-04-12T16:38:08Z

test: remove unused script

2026-03-31T05:06:00Z

REMOVE common.cmake

2026-03-30T14:29:36Z

This repo literally started with common.cmake. However, I think that in this day and age, it is, to put it mildly, outdated. Feature by feature: * The C++ standard is better defined on a per-project basis, and it's very easy. Frankly, I'm surprised GCC still (as of March '26) defaults to something pre-11 (or at least I think it does). * The warning options are, again, very easy to do on a per-project basis, and perhaps they should be defined there. * The Windows-only defines (NOMINMAX, etc.) are, again, very easy to define on the project level, and don't warrant a separate file. * The static runtime thing is more tricky. I use static runtime linking on Windows only, basically. And since about 3.15, it supports CMAKE_MSVC_RUNTIME_LIBRARY, which can set up the linking without my help. I don't care about the older versions enough to keep maintenance. * Symbol stripping is better done when calling `cmake --install --strip` in modern CMake version. Otherwise, it's a simple compilation flag for Release builds. * Installing PDBs does require some trickery though. It's simple enough: you just call install() with $ or whatever it's called.

workflows: clean up path ignore patterns

2026-03-30T10:20:13Z

move testing-only things into test/

2026-03-30T09:54:40Z

cmake-common, branch v6.0.1