diff options
Diffstat (limited to 'examples/android/README.md')
| -rw-r--r-- | examples/android/README.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/examples/android/README.md b/examples/android/README.md index 3ac5607633..9f894f7e4e 100644 --- a/examples/android/README.md +++ b/examples/android/README.md @@ -6,6 +6,7 @@ android_sdk_repository( path="<path to your Android SDK>", api_level=21, build_tools_version="21.1.1") + android_ndk_repository( name="androidndk", path="<path to your Android NDK>", @@ -19,10 +20,12 @@ bazel build //examples/android/java/bazel:hello_world ``` Yes, we know that this is a little clunky. We are working on the following things (and more): + * Supporting other architectures than `armeabi-v7a` and compilers other than GCC 4.9 * Eliminating the big ugly deprecation message from the console output of Bazel We also have a nice way to speed up the edit-compile-install development cycle for physical Android devices and emulators: Bazel knows what code changed since the last build, and can use this knowledge to install only the changed code to the device. This currently works with L devices and changes to Java code and Android resources. To try this out, take an `android_binary` rule and: + * Set the `proguard_specs` attribute to `[]` (the empty list) or just omit it altogether * Set the `multidex` attribute to `native` * Set the `dex_shards` attribute to a number between 2 and 200. This controls the size of chunks the code is split into. As this number is increased, compilation and installation becomes faster but app startup becomes slower. A good initial guess is 10. |