5 ms·

I wonder if they considered build2[1]? It seems to tick most of their boxes. In particular, it has first-class Windows support and, in the upcoming release, eve

by boris 7y ago

I wonder if they considered build2[1]? It seems to tick most of their boxes. In particular, it has first-class Windows support and, in the upcoming release, even native Clang-targeting-MSVC support (not the clang-cl wrapper)[2]. While some of the features they are looking for (like faster build times which I assume means distributed compilation and caching) are not there yet, we are working on them (and would welcome help)[3]. [1] https://build2.org https://build2.org [2] https://stage.build2.org/?builds=&cf=windows_10-clang* https://stage.build2.org/?builds=&cf=windows_10-clang* [3] https://github.com/build2/README/blob/master/roadmap.md https://github.com/build2/README/blob/master/roadmap.md

dochtman 7y ago
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.
- boris 7y ago
  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.xhtml#module-bash https://build2.org/build2/doc/build2-build-system-manual.xht...
  - qznc 7y ago
    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.
    - boris 7y ago
      See my reply to a sibling comment.
  - grok2 7y ago
    But the tag-line on the home page says: "C++ Build Toolchain"!
    - boris 7y ago
      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.
jyounker 7y ago
I think part of the reason is battle-testing. Blaze (the Google internal version of Bazel) has been used by 20k people per day for well over five years to continually build a single mammoth shared C++, Java, Python, Shell (plus others) code base complete with a globally distributed cache system and thousands if not tens of thousands of build machines.

by boris 7y ago

dochtman 7y ago

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.

boris 7y ago
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.xhtml#module-bash https://build2.org/build2/doc/build2-build-system-manual.xht...
- qznc 7y ago
  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.
  - boris 7y ago
    See my reply to a sibling comment.
- grok2 7y ago
  But the tag-line on the home page says: "C++ Build Toolchain"!
  - boris 7y ago
    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.

jyounker 7y ago

I think part of the reason is battle-testing. Blaze (the Google internal version of Bazel) has been used by 20k people per day for well over five years to continually build a single mammoth shared C++, Java, Python, Shell (plus others) code base complete with a globally distributed cache system and thousands if not tens of thousands of build machines.