4 ms·
I don't think describing the build in C++ (https://pagghiu.github.io/SaneCppLibraries/library_build.html https://pagghiu.github.io/SaneCppLibraries/library_buil
by eterevsky 3y ago
I don't think describing the build in C++ (https://pagghiu.github.io/SaneCppLibraries/library_build.html https://pagghiu.github.io/SaneCppLibraries/library_build.htm...) can exactly be called a "sane" idea.
Declarative build definitions are generally much easier to work with and scale than using an imperative language.
- pagghiu 3y agoI could bring multiple examples, but just to make one CMake, what I think today is the most popular way of describing builds in c++, describes builds in an imperative language. https://en.wikipedia.org/wiki/CMake#CMakeLists.txt https://en.wikipedia.org/wiki/CMake#CMakeLists.txt Most "declarative" build systems are not actually what they "declare" to be. I've seen too many DSLs introducing half backed imperative concepts here and there to do _if_ and _for_ constructs or function calls, redoing the same as imperative languages but poorly.