Bazel – Correct, reproducible, fast builds for everyone

Re:Bazel – Correct, reproducible, fast builds for everyone by kchod on Tuesday March 24, 2015 @12:07PM (#9257466)

The Golang source code for the server code at google is built with this tool. The rules that accomplish this are rather complex due to their interactions with our C++ libraries, and predates the open source "Go" tool. The experience with the Google internal rules, motivated some of the choices in the "go" tool, I believe.

If you're interested, hanwen wrote a bunch rules with similar semantics as the internal rules, see https://github.com/google/bazel/tree/master/base_workspace/e... .

It would be nice to make these semantics match the external ones better, but it requires us to open up more tooling, so people won't need to write BUILD files.

[ Parent | on HN ]

Re:Bazel – Correct, reproducible, fast builds for everyone by runlevel1 on Tuesday March 24, 2015 @01:15PM (#9257934)

There's a typo in your link. Should be:

https://github.com/google/bazel/tree/master/examples/go

[ Parent | on HN ]

Re:Bazel – Correct, reproducible, fast builds for everyone by zzzhao on Tuesday March 24, 2015 @01:11PM (#9257903)

In what cases would using Bazel make sense to build Go projects? If they're extremely large? If they have a lot of dependencies on code in other languages? If you need sophisticated build/release tooling?

BTW, thanks for the release! Will have a fun time digging through this over the next few days. I heard some murmurs that Blaze was going to be open sourced from around the watercooler but didn't think it'd be so soon.

[ Parent | on HN ]

Re:Bazel – Correct, reproducible, fast builds for everyone by hanwenn on Tuesday March 24, 2015 @03:10PM (#9258742)

I guess if you want to integrate Go tools with builds in other languages. If you are using pure Go for your entire ecosystem, there is not much point in using Bazel, as the "go" tool is very capable for that scenario.

[ Parent | on HN ]