aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/.github/workflows/boost_toolsets.yml
diff options
context:
space:
mode:
authorEgor Tensin <egor@tensin.name>2026-03-30 16:29:33 +0200
committerEgor Tensin <egor@tensin.name>2026-03-30 16:29:36 +0200
commitd5d02452c39d5ecaafa0e64e69b953fc6b7f617c (patch)
tree5132b3ae56e40760186ba3a42938ecbaff70ebcc /.github/workflows/boost_toolsets.yml
parentworkflows: clean up path ignore patterns (diff)
downloadcmake-common-remove_common_cmake.tar.gz
cmake-common-remove_common_cmake.zip
REMOVE common.cmakev6.0remove_common_cmake
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 $<TARGET_PDB_FILE> or whatever it's called.
Diffstat (limited to '.github/workflows/boost_toolsets.yml')
0 files changed, 0 insertions, 0 deletions