From d5079a59bf85d298ec8598eb3f6b002accb297ce Mon Sep 17 00:00:00 2001
From: Lukacs Berki <lberki@google.com>
Date: Tue, 25 Aug 2015 12:34:20 +0000
Subject: Require an android_local_tools_repository stanza in the WORKSPACE
 file so that Bazel finds Android tools and update the tools themselves to
 handle their new location.

This paves the way for eventually referencing every tool this way.

We have to figure out if android_http_tools_repository is the right way to distribute the Android tools, but now that we don't have a binary distribution yet, it's not an immediate problem.

This will break existing users of Android support in Bazel, whom I'll inform over bazel-discuss.

Fixes #384.

--
MOS_MIGRATED_REVID=101456190
---
 examples/android/README.md | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'examples')

diff --git a/examples/android/README.md b/examples/android/README.md
index 36f3345b68..dd0a3694aa 100644
--- a/examples/android/README.md
+++ b/examples/android/README.md
@@ -1,6 +1,10 @@
 In order to build these examples, add the following two rules to the top-level `WORKSPACE` file (two directories above this file):
 
 ```python
+android_local_tools_repository(
+    name="android_tools",
+    path="<full path to the source tree of Bazel>")
+
 android_sdk_repository(
     name="androidsdk",
     path="<full path to your Android SDK>",
-- 
cgit v1.2.3