Rainer Deyke via Boost
I'm currently taking a second looks at build2. I haven't got very far, but I'm already starting to hate it.
I would be interested to hear why (probably best off-list since it will be off-topic here). Having said that, build2 is (unfortunately) complex and it also "reimagines" a lot of fundamentals compared to the existing build systems and package managers (especially compared to meta build systems like CMake). So many people find it too "alien" at first. I wish it could be done in a simpler way and based on the established intuition, but I don't know how, given the general brokenness of the mainstream approaches we have now. One thing I can say in build2's defense is that it works: what other C++ build toolchains can you use that would allow you to build an application that depends on, say, both Boost and Qt (and all their dependencies, recursively) with a single build system reliably and uniformly across all the major platforms and compiler (including Windows)?