From d316cba52b5aeac660e03068e65dd873669ce1db Mon Sep 17 00:00:00 2001 From: David Benjamin Date: Thu, 2 Jun 2016 16:17:39 -0400 Subject: external/boringssl: Sync to 8ca0b41. This includes the following changes: https://boringssl.googlesource.com/boringssl/+log/9d908ba519f2cfe5e21561bdee3e224b94d14a89..8ca0b4127da11d766067ea6ec4122017ba0edb0e Change-Id: I732653bc8fcba70707c615f8731ca75397a08736 --- src/BUILDING.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'src/BUILDING.md') diff --git a/src/BUILDING.md b/src/BUILDING.md index 33ad87a9..0e34db31 100644 --- a/src/BUILDING.md +++ b/src/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 -- cgit v1.2.3