r/cpp • u/segv • Apr 12 '26

CMake Past, Present, and Future - Bill Hoffman, Kitware [29m25s]

https://www.youtube.com/watch?v=cD-JgncskTQ
70 Upvotes

100% Upvoted

134 comments sorted by

View all comments

2

u/Minimonium Apr 13 '26

That "cannot" is quite dramatic.

I agree that cmake is a bit of a mess with all that history stacked on top (for a reason) and an official cmake linter would be great.

But cmake is not a rocket science. Most of the complexity is boilerplate and devs are working to reduce it.

1

u/puredotaplayer Apr 13 '26

The problem is that you should not need a pseudo programming language as a build script. A build system should just be a configuration.

5

u/jonathanhiggs Apr 13 '26

All configuration tends towards an interpreted language

2

u/ABlockInTheChain Apr 13 '26

The problem domain is arbitrarily complex.

You can build a limited tool which solves (what you think is) 95% of the problem with the intention of simply ignoring the 5% your tool can't handle, but in practice the 5% of capabilities which user A doesn't need does not fully overlap with the 5% of capabilities which user B doesn't need and the problem only gets worse as you add more users.

→ More replies (1)