CMake recently dropped support for older CMake "minimum versions".
-
CMake recently dropped support for older CMake "minimum versions".
How many of you understand what that actually means for CMake?
CMake controls most bug fixes with "policies" that default to "OLD" unless the minimum version declared in CMakeLists.txt >= the version that introduced that policy.
What this means is:
1) If you crank the minimum version in CMakeLists.txt, you will get different behaviour!2) Upgrading CMake basically means nothing changes and you get a huge techdebt cliff.
-
CMake recently dropped support for older CMake "minimum versions".
How many of you understand what that actually means for CMake?
CMake controls most bug fixes with "policies" that default to "OLD" unless the minimum version declared in CMakeLists.txt >= the version that introduced that policy.
What this means is:
1) If you crank the minimum version in CMakeLists.txt, you will get different behaviour!2) Upgrading CMake basically means nothing changes and you get a huge techdebt cliff.
@thesamesam lol cmake -
A a1ba@suya.place shared this topic
-
@thesamesam lol cmake
-
@a1ba @thesamesam should have used KConfig?
@uis @thesamesam idk what's worse cmake or autotools -
@uis @thesamesam idk what's worse cmake or autotools
-
-
@lanodan @uis @thesamesam @a1ba or only one yet.
autotools at least does not have FetchContent, while cmake may SILENTLY download something. This might be good for separate task, not during configure -
@lanodan @uis @thesamesam @a1ba or only one yet.
autotools at least does not have FetchContent, while cmake may SILENTLY download something. This might be good for separate task, not during configure@mittorn @lanodan @uis @thesamesam btw I remember using it and while, yes, it can download and unpack stuff, it's weird that it's not verbose by default. Not arguing if it's an attack vector or something, just... why silent
