|
|
|
|
|
by DoofusOfDeath
2850 days ago
|
|
One of my problems with "modern" CMake is the same as my problem with "modern" C++: Their proponents argue for using certain new language features to get things done. But because of backwards-compatibility concerns, the system still supports the old, quasi-deprecated constructs for doing those same things. And so you end up with an overly complicated language that seems to have multiple, reasonable ways to do the same thing. And codebases containing a mix of the two, even for newly written code. IMO it would be better for CMake to make a clean break, and have CMake 4 only support "modern" CMake. (edit: And, as I've posted elsewhere, switch to a more robust scripting language.) |
|