NOTES.ANDROID 3.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. NOTES FOR ANDROID PLATFORMS
  2. ===========================
  3. Requirement details
  4. -------------------
  5. Beside basic tools like perl and make you'll need to download the Android
  6. NDK. It's available for Linux, Mac OS X and Windows, but only Linux
  7. version was actually tested. There is no reason to believe that Mac OS X
  8. wouldn't work. And as for Windows, it's unclear which "shell" would be
  9. suitable, MSYS2 might have best chances. NDK version should play lesser
  10. role, the goal is to support a range of most recent versions.
  11. Configuration
  12. -------------
  13. Android is naturally cross-compiled target and you can't use ./config.
  14. You have to use ./Configure and name your target explicitly; there are
  15. android-arm, android-arm64, android-mips, android-mip64, android-x86
  16. and android-x86_64. Do not pass --cross-compile-prefix (as you might
  17. be tempted), as it will be "calculated" automatically based on chosen
  18. platform. Though you still need to know the prefix to extend your PATH,
  19. in order to invoke $(CROSS_COMPILE)gcc and company. (Configure will fail
  20. and give you a hint if you get it wrong.) Apart from PATH adjustment
  21. you need to set ANDROID_NDK environment to point at NDK directory
  22. as /some/where/android-ndk-<ver>. NDK customarily supports multiple
  23. Android API levels, e.g. android-14, android-21, etc. By default latest
  24. one available is chosen. If you need to target older platform, pass
  25. additional -D__ANDROID_API__=N to Configure. N is numeric value of the
  26. target platform version. For example, to compile for ICS on ARM with
  27. NDK 10d:
  28. ANDROID_NDK=/some/where/android-ndk-10d
  29. PATH=$ANDROID_NDK/toolchains/arm-linux-androideabi-4.8/prebuild/linux-x86_64/bin:$PATH
  30. ./Configure android-arm -D__ANDROID_API__=14
  31. Caveat lector! Earlier OpenSSL versions relied on additional CROSS_SYSROOT
  32. variable set to $ANDROID_NDK/platforms/android-<api>/arch-<arch> to
  33. appoint headers-n-libraries' location. It's still recognized in order
  34. to facilitate migration from older projects. However, since API level
  35. appears in CROSS_SYSROOT value, passing -D__ANDROID_API__=N can be in
  36. conflict, and mixing the two is therefore not supported. Migration to
  37. CROSS_SYSROOT-less setup is recommended.
  38. One can engage clang by passing CC=clang to Configure. In such case
  39. PATH needs even more adjustments to cover NDK's clang itself, as well
  40. as unprefixed, yet target-specific, ar and ranlib (or not, if you use
  41. binutils-multiarch on your Linux).
  42. Running tests (on Linux)
  43. ------------------------
  44. This is not actually supported. Notes are meant rather as inspiration.
  45. Even though build output targets alien system, it's possible to execute
  46. test suite on Linux system by employing qemu-user. The trick is static
  47. linking. Pass -static to Configure, then edit generated Makefile and
  48. remove occurrences of -ldl and -pie flags. You would also need to pick
  49. API version that comes with usable static libraries, 42/2=21 used to
  50. work. Once built, you should be able to
  51. env EXE_SHELL=qemu-<arch> make test
  52. If you need to pass additional flag to qemu, quotes are your friend, e.g.
  53. env EXE_SHELL="qemu-mips64el -cpu MIPS64R6-generic" make test