From 129976722b0dc2e0f73c5bac1148c6cbe8ec3e44 Mon Sep 17 00:00:00 2001
From: Damien Martin-Guillerez <dmarting@google.com>
Date: Thu, 3 Sep 2015 21:54:08 +0000
Subject: Quick fix for shipping the android tools in the Bazel binary

This is not really nice, there are several hacks there. This
repository will get removed in the future and linked to a
remote one instead. I tested it against the tutorial and
it works like a charm. mobile-install seems like to work,
maybe that's also fixing the last issue reported in #392.

Known issue: Java compilation output errors about files being
modified in the future.

--
MOS_MIGRATED_REVID=102282979
---
 examples/android/README.md | 4 ----
 1 file changed, 4 deletions(-)

(limited to 'examples/android')

diff --git a/examples/android/README.md b/examples/android/README.md
index dd0a3694aa..36f3345b68 100644
--- a/examples/android/README.md
+++ b/examples/android/README.md
@@ -1,10 +1,6 @@
 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