| commit | 4a45d92130a6b1306a3840d006df165b8040a6cf | [log] [tgz] |
|---|---|---|
| author | Julio Merino <jmmv@google.com> | Thu Sep 08 14:52:49 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Fri Sep 09 09:02:41 2016 +0000 |
| tree | 0ac4f430fc8aa0bf381edd98648cd6cb63a3ad80 | |
| parent | 3fd3f1b7c103379353dd50756aefc051761cfb61 [diff] |
Use inheritance to support site-specific options. Rename BlazeStartupOptions to StartupOptions and turn the latter into a class that can be subclassed to implement site-specific options behavior. This lends itself to easier customization for the site-specific versions, especially if there is more than one, and gets rid of the strange build-time parameterization of the old blaze_startup_options*.cc files. Note that this change introduces various TODOs. This is intentional. This change is quite complex as it is and I want to focus it on reshuffling the class structure without actually touching the internals. The latter can be done in subsequent, more targetted changes that are easier to review and understand. -- MOS_MIGRATED_REVID=132555032
{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.