Replies: 2 comments
-
There's a shift of moving to new build infrastructure, away from the traditional Makefile or autotools infra, whether it's to get away from perceived arcaneness or lack of performance. The thing is that the usual pick of the mix build tools that are currently in flavour have much higher dependency requirement than the code base they're actually used to build. I am capable of build this project with a C compiler which supports C99 + a copy of make. As an example for cmake and such I would need a much newer compiler (with C++11 support) + its dependencies. You could make the argument that I've gone off into the weeds and a current system not only would have the language support but would have everything ready to set off and that's true however such tooling imposes that only current mainstream systems are used because anything fringe will be very hard or impossible. |
Beta Was this translation helpful? Give feedback.
-
Makefile in its current form is undoubtedly a pain to maintain and improve. I think having just CMake in the near future is enough. Supporting both Meson and CMake at the same time could be problematic. As for Bazel - I don't see many requests for it just yet. |
Beta Was this translation helpful? Give feedback.
-
We mentioned here and there that the
Makefile
build is considered deprecated and should be removed. Though it was never really discussed or tracked somewhere.Supporting only
cmake
is indeed maybe not enough(?). We could add support for other build systems. Meson, Bazel?Personally I am still in favor of deprecating the
Makefile
way. Its pretty messy IMHO.Thoughts, objections etc. are very welcome.
Beta Was this translation helpful? Give feedback.
All reactions