| commit | 184be1c7858cbc6bb8bb93c0a0a487a08c914cb6 | [log] [tgz] |
|---|---|---|
| author | Michael Staib <mstaib@google.com> | Sat Feb 27 00:00:46 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Sun Feb 28 17:04:56 2016 +0000 |
| tree | 7f1c93a583a12a98f61f2e7dcf9f739dc1c3fb0d | |
| parent | 0e28eda71066ac90257637a42887b637d7042496 [diff] |
Stop using preprocessed .aidl files for types in the same android_library. This makes very little sense, because we only do this when compiling them within a rule. The preprocessed files are not shipped to other rules, meaning we treat things differently depending on the dependency structure. And, worst of all, this can lead to a bug in the aidl compiler, which causes the preprocessed definition to take precedence over the input file, which causes certain modifiers to be stripped away. Also, Gradle doesn't do it, and that's proof enough that this is no longer the way to go, if ever it was. Unfortunately, this causes a problem: the preprocessing had an effect, in that all preprocessed types are available without the use of imports. This means that .aidl files which were previously legal before this change may now be broken, if they relied on this behavior. But, those .aidl files are actually not legal according to the .aidl specification. Unfortunate, but the right thing to do. This CL also updates the idl documentation. Which, let's face it, could probably have used some improvement. RELNOTES[INC]: .aidl files correctly require import statements for types defined in the same package and the same android_library. -- MOS_MIGRATED_REVID=115718918
{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.