4 ms·
It's interesting that you mention Bazel. Do any of Google's large public projects use it? Android has Repo, Chromium has depot_tools, and Fuchsia has jiri. Fuc
by TheAceOfHearts 9y ago
It's interesting that you mention Bazel. Do any of Google's large public projects use it? Android has Repo, Chromium has depot_tools, and Fuchsia has jiri.
Fuchsia has its own IDL [0], which is used to generate bindings for C, C++, Dart, Go, and Rust.
It's not perfect, but I'd say Webpack [1] is worth mentioning. You define loaders and it crawls your dependency graph. When you reference assets in code they get built, copied to the output folder, and all references updated.
[0] https://fuchsia.googlesource.com/fidl/ https://fuchsia.googlesource.com/fidl/
[1] https://webpack.js.org https://webpack.js.org
- iainmerrick 9y agoGoogle uses Bazel (or Blaze, which it's based on) for almost all their proprietary code, at least. Their big open source projects, Android and Chrome and now Fuchsia, seem to have very different coding cultures from the rest of Google. I've used both repo and depot_tools a bit and both are pretty bad -- very thin and leaky abstractions on top of the source control system.