| commit | 63e8d6321ae5732b552b884de69d82230cfbe1bc | [log] [tgz] |
|---|---|---|
| author | Julio Merino <jmmv@google.com> | Thu Feb 25 18:17:53 2016 +0000 |
| committer | Philipp Wollermann <philwo@google.com> | Fri Feb 26 10:07:09 2016 +0000 |
| tree | c34c87f5c39abfc4715a0979b1710cb6cbbe09e7 | |
| parent | b6efd0f8f287c5021d52715c47e2da23ffeb10de [diff] |
Improve handling of exit routines to ensure we respect the exit status. As part of this, change atexit to receive the name of a function instead of just a chunk of code. This way, we can also control the return value of each individual atexit function and report it to the user, should these routines fail when the program apparently succeeded. -- MOS_MIGRATED_REVID=115575895
{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.