diff options
| author | Andy Polyakov <appro@openssl.org> | 2018-10-14 15:19:41 +0200 |
|---|---|---|
| committer | Andy Polyakov <appro@openssl.org> | 2018-10-19 10:35:36 +0200 |
| commit | 03ad7c009e16a233c733098db3169c560142ccd3 (patch) | |
| tree | fb84b40a92a0dca7d0e5a79b587339041453da94 /NOTES.ANDROID | |
| parent | 9d71a24ebf57e7157888af1ca587eafe914bf96f (diff) | |
Configurations/15-android.conf: add support for "standalone toolchain".
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/7400)
Diffstat (limited to 'NOTES.ANDROID')
| -rw-r--r-- | NOTES.ANDROID | 18 |
1 files changed, 13 insertions, 5 deletions
diff --git a/NOTES.ANDROID b/NOTES.ANDROID index d13f47d667..bbbd8e4db9 100644 --- a/NOTES.ANDROID +++ b/NOTES.ANDROID @@ -24,16 +24,18 @@ in order to invoke $(CROSS_COMPILE)gcc and company. (Configure will fail and give you a hint if you get it wrong.) Apart from PATH adjustment you need to set ANDROID_NDK environment to point at NDK directory - as /some/where/android-ndk-<ver>. NDK customarily supports multiple + as /some/where/android-ndk-<ver>. Both variables are significant at both + configuration and compilation times. NDK customarily supports multiple Android API levels, e.g. android-14, android-21, etc. By default latest one available is chosen. If you need to target older platform, pass additional -D__ANDROID_API__=N to Configure. N is numeric value of the target platform version. For example, to compile for ICS on ARM with NDK 10d: - ANDROID_NDK=/some/where/android-ndk-10d + export ANDROID_NDK=/some/where/android-ndk-10d PATH=$ANDROID_NDK/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin:$PATH ./Configure android-arm -D__ANDROID_API__=14 + make Caveat lector! Earlier OpenSSL versions relied on additional CROSS_SYSROOT variable set to $ANDROID_NDK/platforms/android-<api>/arch-<arch> to @@ -43,12 +45,18 @@ conflict, and mixing the two is therefore not supported. Migration to CROSS_SYSROOT-less setup is recommended. - One can engage clang by adjusting PATH to cover NDK's clang. Just keep - in mind that if you miss it, Configure will try to use gcc... Also, - PATH would need even further adjustment to cover unprefixed, yet + One can engage clang by adjusting PATH to cover same NDK's clang. Just + keep in mind that if you miss it, Configure will try to use gcc... + Also, PATH would need even further adjustment to cover unprefixed, yet target-specific, ar and ranlib. It's possible that you don't need to bother, if binutils-multiarch is installed on your Linux system. + Another option is to create so called "standalone toolchain" tailored + for single specific platform including Android API level, and assign its + location to ANDROID_NDK. In such case you have to pass matching target + name to Configure and shouldn't use -D__ANDROID_API__=N. PATH adjusment + becomes simpler, $ANDROID_NDK/bin:$PATH suffices. + Running tests (on Linux) ------------------------ |