One of the important parts in the post seems to be that it is not just a C++ build system, there are many other tasks executed through the build system. In that sense, it seems like build2 isn't a great fit.
back
1 comments
On the contrary, build2 is a language-agnostic, general-purpose build system. There is the bash module[1], for example. And now that we have support for dynamically buildable/loadable build system modules, we can develop support for more languages, code generators, etc., without bundling it with the build system core. I myself am itching to take a stab at Rust. Hopefully will find time after the release.
[1] https://build2.org/build2/doc/build2-build-system-manual.xht...
The frontpage starts with "build2 is an open source (MIT), cross-platform build toolchain for developing and packaging C and C++ code."
My impression about the modules you linked to: A secondary feature because many C/C++ project need some additional scripting.
See my reply to a sibling comment.
But the tag-line on the home page says: "C++ Build Toolchain"!
Yes, we need to change that. Our initial focus was on taking really good care of C/C++ compilation but now we are at the stage (i.e., we have support for external build system modules) where this is starting to change.