| commit | 8d487c5a0ce868b14a2478f1c1691b8e0e9e2ab5 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Mon Jan 09 17:21:33 2017 +0000 |
| committer | Marcel Hlopko <hlopko@google.com> | Tue Jan 10 10:21:05 2017 +0000 |
| tree | cc94faf050adbc4159e41069aed63303ea95ab53 | |
| parent | 1f22ed5e1036c42db2ab0688a910c70331b5878f [diff] |
Add missing #include statements for ijar We may not assume that those are pulled in by other header files; in fact, they are not on FreeBSD stable/11. -- Change-Id: Ic976cc71968aab0a1c3d6652fe8d8f1c4afa480b Reviewed-on: https://cr.bazel.build/8145 PiperOrigin-RevId: 143970238 MOS_MIGRATED_REVID=143970238
{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.