From d5d02452c39d5ecaafa0e64e69b953fc6b7f617c Mon Sep 17 00:00:00 2001 From: Egor Tensin Date: Mon, 30 Mar 2026 16:29:33 +0200 Subject: REMOVE 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 $ or whatever it's called. --- pyproject.toml | 3 --- 1 file changed, 3 deletions(-) (limited to 'pyproject.toml') diff --git a/pyproject.toml b/pyproject.toml index 80f5b5b..8bfa7c6 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -38,7 +38,4 @@ script-files = [ "tools/project-clang-format.py", ] -[tool.setuptools.data-files] -"share/cmake" = ["common.cmake"] - [tool.setuptools_scm] -- cgit v1.3