News for hackers. Stuff that matters.
Re:Building a Build System: Bazel Reaches Beta by adonovan on Wednesday September 09, 2015 @05:42PM (#10194826)
(Former Blaze engineer and current Go tool builder here.)

Blaze's support for building Go source code predates the existence of the 'go' tool and uses very different conventions for package naming, directory layout, testing, and project organization. As a result, most Google Go code cannot be built with 'go'. This can be a source of frustration at times.

Re:Building a Build System: Bazel Reaches Beta by defen on Wednesday September 09, 2015 @05:54PM (#10194893)
Is "Blaze" something else or an autocorrect/typo of "Bazel" (topic of this post)?
Re:Building a Build System: Bazel Reaches Beta by activez on Wednesday September 09, 2015 @06:04PM (#10194953)
From the faq (http://bazel.io/faq.html):

Did you rewrite your internal tool as open-source? Is it a fork?

Bazel shares most of its code with the internal tool and its rules are used for millions of builds every day.

What's up with the word "Blaze" in the codebase?

This is an internal name for the tool. Please refer to Bazel as Bazel.

Re:Building a Build System: Bazel Reaches Beta by e98cuenc on Wednesday September 09, 2015 @06:00PM (#10194931)
Blaze is the internal name of Bazel in Google (I don't know if both projects are identical, or if Blaze was just the "inspiration" for Bazel)
Re:Building a Build System: Bazel Reaches Beta by asuffield on Wednesday September 09, 2015 @09:58PM (#10195800)
They refer to distinct things but share a lot of their code. Blaze doesn't contain anything that you would find useful, you need our infrastructure for its other features to work.
Re:Building a Build System: Bazel Reaches Beta by qznc on Wednesday September 09, 2015 @05:57PM (#10194916)
Blaze is the Google-internal thing. Bazel is its Open Source clone.