| commit | cc9ac3f152f24662691eba330234fbe70956bc78 | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Tue Jun 16 06:42:41 2015 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Tue Jun 16 14:00:01 2015 +0000 |
| tree | db0fec783f6971b7c3e55737690974685821c68e | |
| parent | 551bb0973da646ae7b1a35878ee02c334156ccb6 [diff] |
Default Android dependencies to a //external: label with a default binding to //tools/android: . This is useful because we can then eventually implement an android_tools_repository() rule that lets Bazel download the Android tools from somewhere instead of requiring it to be in every workspace with Android tools. The number of tools here is somewhat scary, therefore, I'm considering creating an android_tools rule which would have an attribute for each of these things. Some non-trivial things about this CL: - The labels to load are removed from AndroidConfiguration because they would resolve to e.g. //external:dx_jar, which labels just don't exist and I don't want to add dummy //external:labels not prefixed with android_ - RedirectChaser is taught how to chase redirect through bind() rules because the Android SDK is now found by //external:android_sdk -> //tools/android:sdk -> @androidsdk//:sdk . Ideally, it would be ///external:android_sdk -> @androidsdk//:sdk, but I figured I'd not fix that in this CL. -- MOS_MIGRATED_REVID=96080553
{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.
How to install Bazel
How to get started using Bazel
The Bazel command line is documented in the user manual
The rule reference documentation is in the build encyclopedia
How to use the query command
How to extend Bazel
The test environment is described in the test encyclopedia
About the Bazel project:
