ref: a9605ac06314404040839baf3253a4ee8168ac75
parent: b700b67bbad51bf326ace75954e056e0c8a6c5f4
author: Alex Cohn <alexcohn@netvision.net.il>
date: Wed Oct 21 05:49:58 EDT 2015
Update README.md See https://github.com/cisco/openh264/issues/1807#issuecomment-149794717.
--- a/README.md
+++ b/README.md
@@ -68,11 +68,12 @@
Valid `**ANDROID_TARGET**` can be found in `**ANDROID_SDK**/platforms`, such as `android-12`.
You can also set `ARCH`, `NDKLEVEL` according to your device and NDK version.
`ARCH` specifies the architecture of android device. Currently `arm`, `arm64`, `x86` and `x86_64` are supported, the default is `arm`. (`mips` and `mips64` can also be used, but there's no specific optimization for those architectures.)
-`NDKLEVEL` specifies android api level, the api level can be 12-19, the default is 12.
+`NDKLEVEL` specifies android api level, the default is 12, and lower levels are not supported. Availabe possibilities can be found in `**ANDROID_NDK**/platforms`, such as `android-21` (strip away the `android-` prefix).
By default these commands build for the `armeabi-v7a` ABI. To build for the other android
ABIs, add `ARCH=arm64`, `ARCH=x86`, `ARCH=x86_64`, `ARCH=mips` or `ARCH=mips64`.
To build for the older `armeabi` ABI (which has armv5te as baseline), add `APP_ABI=armeabi` (`ARCH=arm` is implicit).
+To build for 64-bit ABI, such as `arm64`, explicitly set `NDKLEVEL` to 21 or higher.
For iOS Builds
--------------