Comment by jpgvm
20 hours ago
Upvote for Bazel. I think these days I place a lot more value on how well an ecosystem slots into Bazel/friends because monorepos are increasingly more useful and relevant.
So nice to see there are good rules for Zig and that folks are using them.
Also ironically I think starting with Bazel/Buck/whatever your poison of choice is almost always a good move even if people tell you it's overkill. The easiest time to do it as at the beginning, all times after that is too hard and the marginal cost of building with it from the start is minimal.
agreed, love Bazel + BuildBuddy
Downvote for this web site is a horror movie billboard and zig already has a build system which is zig and that's one of it's neat features.
People are free to knock themselves out with Bazel if they’re into that kind of masochism, but having it as the ONLY way to build your OSS project is a big no.
Yeah I'm never touching Bazel again. I value my sanity.
well, bazel is by far the most reliable one so I'm not sure why you're complaining
The problem with "the language tooling is already a build system" is that cross-language dependency chains are a thing. The moment you need a Rust or Zig file to be regenerated and recompiled when a JSON schema or .proto file is updated, you're outside what most of those language-specific toolchains can support. This is where Bazel absolutely shines.
Zig build system can do all that just fine though
1 reply →
If all of your dependencies need to use the same build system as your project then your build system/process is defect anyway. It should be possible to invoke a foreign build system as part of your build.
2 replies →
Rust build system can do all that just fine though