| commit | 5053a80a83cdba21fa8515f873a42a4b8b68e6f4 | [log] [tgz] |
|---|---|---|
| author | Nathan Harmata <nharmata@google.com> | Fri Mar 11 17:36:44 2016 +0000 |
| committer | David Chen <dzc@google.com> | Fri Mar 11 21:29:43 2016 +0000 |
| tree | 4c60566957573c6ae4a003445c57409fed1215f5 | |
| parent | 7aa72a0a126c7fd6b54517b2a9f95b2cc6f1d50e [diff] |
Remove unused declared function AddJVMSpecificArguments. Kudos to @tfarina for pointing out this dead function declaration. An older commit (prior to bazel being open sourced) moved the file out of blaze_util.cc but forgot to delete the function declaration from the header file. And a subsequent change (also before bazel was open sourced) renamed/moved the implementation to a place that is now internal-only. -- MOS_MIGRATED_REVID=116980458
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.