| commit | 19e126a1a7643e170ceec65a11f6a4d330ae1b3b | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@google.com> | Wed Feb 22 23:02:44 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Thu Feb 23 11:31:00 2017 +0000 |
| tree | 122df8eaa766e0eae39dab89aabca53772d131d3 | |
| parent | 1d7db156291762b46550b9610ee1b1c73fde58ad [diff] |
Add a flag to enable desugaring java.* classes by rewriting package names java.* and sun.* classes cannot be desugared directly because there are hard coded restrictions in the JVM that prevent using loading or using reflection on them. Add a --core_library flag that rewrites package names to have a __desugar__ prefix when reading them, and strips the prefix when writing them back out. -- PiperOrigin-RevId: 148273386 MOS_MIGRATED_REVID=148273386
{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.