diff options
author | David Benjamin <davidben@google.com> | 2016-04-28 14:51:36 -0400 |
---|---|---|
committer | Adam Langley <agl@google.com> | 2016-05-19 16:56:25 +0000 |
commit | 75021b747f2d1547553ee4f9c14e4be350c198c6 (patch) | |
tree | 633f2f1d45556b7b933461adb1f1e1e6463bc50b /BUILDING.md | |
parent | f07ba17942eaffe52763ff75487acab5d2f2d5c1 (diff) | |
download | boringssl-75021b747f2d1547553ee4f9c14e4be350c198c6.zip boringssl-75021b747f2d1547553ee4f9c14e4be350c198c6.tar.gz boringssl-75021b747f2d1547553ee4f9c14e4be350c198c6.tar.bz2 |
Update Android build instructions.
We now have a copy of android-cmake. Also remove the mention of running cmake
twice. It seems to work fine once?
The API level also got specified twice somehow.
BUG=26
Change-Id: I1331b079a4d8531cd53f7de3605ac318c14b3e26
Reviewed-on: https://boringssl-review.googlesource.com/7985
Reviewed-by: Adam Langley <agl@google.com>
Diffstat (limited to 'BUILDING.md')
-rw-r--r-- | BUILDING.md | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/BUILDING.md b/BUILDING.md index 33ad87a..0e34db3 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -79,18 +79,18 @@ It's possible to build BoringSSL with the Android NDK using CMake. This has been tested with version 10d of the NDK. Unpack the Android NDK somewhere and export `ANDROID_NDK` to point to the -directory. Clone https://github.com/taka-no-me/android-cmake into `util/`. Then -make a build directory as above and run CMake *twice* like this: +directory. Then make a build directory as above and run CMake like this: - cmake -DANDROID_NATIVE_API_LEVEL=android-9 \ - -DANDROID_ABI=armeabi-v7a \ - -DCMAKE_TOOLCHAIN_FILE=../util/android-cmake/android.toolchain.cmake \ + cmake -DANDROID_ABI=armeabi-v7a \ + -DCMAKE_TOOLCHAIN_FILE=../third_party/android-cmake/android.toolchain.cmake \ -DANDROID_NATIVE_API_LEVEL=16 \ -GNinja .. -Once you've run that twice, Ninja should produce Android-compatible binaries. -You can replace `armeabi-v7a` in the above with `arm64-v8a` to build aarch64 -binaries. +Once you've run that, Ninja should produce Android-compatible binaries. You +can replace `armeabi-v7a` in the above with `arm64-v8a` and use API level 21 or +higher to build aarch64 binaries. + +For other options, see [android-cmake's documentation](./third_party/android-cmake/README.md). ## Known Limitations on Windows |