| commit | 60c3a04251fe225c5a46536e0ba248a831026ad8 | [log] [tgz] |
|---|---|---|
| author | Todd Jeffreys <tjeffreys@google.com> | Wed Jul 27 20:29:48 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Jul 28 09:15:08 2016 +0000 |
| tree | 0de1aab9b002e94697a6bffb3076b59013b466f2 | |
| parent | 75714b0d6e65905e41da8415ca3e7ec101575d51 [diff] |
Add file:// support to bazel's new_http_archive rule. This modifies HttpConnection.java to support other URLConnections besides simply HttpURLConnection. Supporting at least file://, and possibly ftp:// in theory. In the absence of AAR android support, this allows me to import a Google Play Services AAR library using a combination of new_http_archive from file://$ANDROID_SDK/... and a custom BUILD file that repackages it via android_library. I added a check against zero-sized files, but I'm not 100% sure it's required. -- MOS_MIGRATED_REVID=128621789
{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.