| commit | 65d66a3afa09abdf5d66e14d3c4a82a08c7a05e0 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Dec 01 16:49:02 2016 +0000 |
| committer | Irina Iancu <elenairina@google.com> | Fri Dec 02 07:41:22 2016 +0000 |
| tree | ccc3e5c9115166c24434fdb66280a6c220d0b962 | |
| parent | 14e35546302a48d1074bc2456ef4d63c27c9d3a1 [diff] |
Add --ltoindexopt to pass options to LTO indexing step This makes it much easier to pass options just to the LTO indexing. Previously these had to be passed via --linkopt, but that also passed the options to the final native link, which causes issues since most useful ThinLTO indexing options are plugin options and gold gives an error when these are passed to native links not involving a plugin. -- MOS_MIGRATED_REVID=140735846
{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.