4 ms·
(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 dif
by adonovan 11y ago
(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.
- defen 11y agoIs "Blaze" something else or an autocorrect/typo of "Bazel" (topic of this post)?
- qznc 11y agoBlaze is the Google-internal thing. Bazel is its Open Source clone.
- e98cuenc 11y agoBlaze 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)
- asuffield 11y agoThey 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.
- activez 11y agoFrom the faq (http://bazel.io/faq.html 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.