4 ms·
I thought Google was all about Bazel these days. Anyone know why Google is pushing two apparently competing build systems?
by lobster_johnson 11y ago
I thought Google was all about Bazel these days. Anyone know why Google is pushing two apparently competing build systems?
- skybrian 11y agoOnly two? There are more than that. For example, Android Studio uses Gradle. Go and Dart have their own build systems as well. It might be because Google is a big company doing many things in many languages, Bazel was only open sourced recently, and so on.
- sunnyps 11y agoDon't forget Chromium which itself has two meta build systems (gyp and gn - similar to bazel/cmake/etc.) along with an underlying build system (ninja) which can target multiple compilers and runtimes on different platforms. P.S. Chromium is in the middle of a transition from gyp to gn[1] which is why it has two build systems. [1] https://chromium.googlesource.com/chromium/src/+/master/tools/gn/README.md https://chromium.googlesource.com/chromium/src/+/master/tool...
- warmwaffles 11y agoAlso google doesn't give a shit about the developers that have to use the tools.
- frik 11y agoGood to hear the move away from gyp. The hand tuned build scripts (VS/nmake/make) before gyp were better.
- asuffield 11y agoBazel is blaze released to the public. Android never used blaze because it had to be built by people outside Google. Different worlds.
- lobster_johnson 11y agoRight, but Bazel is public, so why not use that?
- gohrt 11y agobecause ninja launched years before blaze, and the team didn't want to switch again?
- deleted 11y ago[deleted]