File 0374-Document-how-to-cross-compile-for-Android-x86_64.patch of Package erlang
From f78c0e7f240a12d3e5284cc33ac2e885de5b1c92 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=B4me=20de=20Bretagne?=
<jerome.debretagne@gmail.com>
Date: Sat, 15 May 2021 17:16:02 +0200
Subject: [PATCH] Document how to cross compile for Android x86_64
Remove references to a specific OTP version in the instructions.
---
HOWTO/INSTALL-ANDROID.md | 62 ++++++++++++++++++++++++++++++----------
1 file changed, 47 insertions(+), 15 deletions(-)
diff --git a/HOWTO/INSTALL-ANDROID.md b/HOWTO/INSTALL-ANDROID.md
index 7d5af0b0ec..c3a6d6fe36 100644
--- a/HOWTO/INSTALL-ANDROID.md
+++ b/HOWTO/INSTALL-ANDROID.md
@@ -7,7 +7,7 @@ Introduction
This document describes how to cross compile Erlang/OTP to Android/Rasberry Pi platforms.
-### Download and Install Android NDK ###
+### Download and Install the Android NDK ###
https://developer.android.com/ndk
@@ -27,7 +27,7 @@ to generate the configure scripts.
### Configure Erlang/OTP ###
-Use the following commands when compiling a 64-bit version.
+Use the following commands when compiling an ARM 64-bit version.
$ export NDK_ABI_PLAT=android21 # When targeting Android 5.0 Lollipop
@@ -54,15 +54,14 @@ Use the following commands when compiling a 64-bit version.
$
$ # This previous step is needed for the OpenSSL static linking to work as
$ # the --with-ssl option expects a path with both the 'lib' and 'include'
- $ # directories. Otherwise the Erlang/OTP build will fallback to dynamic
- $ # linking if it doesn't find 'libcrypto.a' in its expected location.
+ $ # directories.
$ ./otp_build configure \
--xcomp-conf=./xcomp/erl-xcomp-arm64-android.conf \
--with-ssl=/path/to/OpenSSL/source/dir/built/for/android-arm64 \
--disable-dynamic-ssl-lib
-Use the following commands instead when compiling a 32-bit version.
+Use the following commands when compiling an ARM 32-bit version.
$ export NDK_ABI_PLAT=androideabi16 # When targeting Android 4.1 Jelly Bean
@@ -89,14 +88,47 @@ Use the following commands instead when compiling a 32-bit version.
$
$ # This previous step is needed for the OpenSSL static linking to work as
$ # the --with-ssl option expects a path with both the 'lib' and 'include'
- $ # directories. Otherwise the Erlang/OTP build will fallback to dynamic
- $ # linking if it doesn't find 'libcrypto.a' in its expected location.
+ $ # directories.
$ ./otp_build configure \
--xcomp-conf=./xcomp/erl-xcomp-arm-android.conf \
--with-ssl=/path/to/OpenSSL/source/dir/built/for/android-arm \
--disable-dynamic-ssl-lib
+Use the following commands when compiling an x86 64-bit version.
+
+ $ export NDK_ABI_PLAT=android21 # When targeting Android 5.0 Lollipop
+
+
+ $ # Either without OpenSSL support:
+ $
+ $ ./otp_build configure \
+ --xcomp-conf=./xcomp/erl-xcomp-x86_64-android.conf \
+ --without-ssl
+
+
+ $ # Or with OpenSSL linked statically:
+ $
+ $ cd /path/to/OpenSSL/source/dir/built/for/android-x86_64
+ $ # First follow the NOTES.UNIX build instructions from OpenSSL
+ $
+ $ # Then to avoid the full installation of this locally-compiled build,
+ $ # manually create a 'lib64' directory at the root of the OpenSSL source
+ $ # (at the same level as 'include') and link 'libcrypto.a' inside it.
+ $
+ $ mkdir lib64
+ $ ln -s ../libcrypto.a lib64/libcrypto.a
+ $ cd - # Return to the Erlang/OTP directory
+ $
+ $ # This previous step is needed for the OpenSSL static linking to work
+ $ # as the --with-ssl option expects a path with both the 'lib64' and
+ $ # 'include' directories.
+ $ ./otp_build configure \
+ --xcomp-conf=./xcomp/erl-xcomp-x86_64-android.conf \
+ --with-ssl=/path/to/OpenSSL/source/dir/built/for/android-x86_64 \
+ --disable-dynamic-ssl-lib
+
+
### Compile Erlang/OTP ###
$ make noboot [-j4]
@@ -106,15 +138,15 @@ Use the following commands instead when compiling a 32-bit version.
### Make Release ###
- $ make RELEASE_ROOT=/path/to/release/erlang_23.0_arm release
+ $ make RELEASE_ROOT=/path/to/release/erlang release
### Target Deployment for Rasberry Pi ###
-Make a tarball out of /path/to/release/erlang_23.0_arm and copy it to target
+Make a tarball out of /path/to/release/erlang and copy it to target
device. Extract it and install.
- $ ./Install /usr/local/erlang_23.0_arm
+ $ ./Install /usr/local/erlang
### Target Deployment for Android testing ###
@@ -124,17 +156,17 @@ Android device, for testing purpose mainly, as the /data/local/tmp path used
for installation below is executable only from the adb shell command, but not
from other local applications due to Android sandbox security model.
- $ cd /path/to/release/erlang_23.0_arm
+ $ cd /path/to/release/erlang
$ # For testing purpose, configure the Erlang/OTP scripts to use the target
$ # installation path in /data/local/tmp which is executable from adb shell
- $ ./Install -cross -minimal /data/local/tmp/erlang_23.0
+ $ ./Install -cross -minimal /data/local/tmp/erlang
To properly integrate into an Android application, the installation would have
to target /data/data/[your/app/package/name]/files/[erlang/dir/once/unpacked]
as shown in https://github.com/JeromeDeBretagne/erlanglauncher as an example.
WARNING: adb has issues with symlinks (and java.util.zip too). There is only
-one symlink for epmd in recent Erlang/OTP releases (20 to master-based 23) so
+one symlink for epmd in recent Erlang/OTP releases (20 to master-based 24) so
it has to be removed before using adb push, and then recreated manually on the
target device itself if needed (or epmd can simply be duplicated instead).
@@ -143,12 +175,12 @@ target device itself if needed (or epmd can simply be duplicated instead).
$ cp erts-X.Y.Z/bin/epmd bin/epmd
$ cd ..
$ # The release can now be deployed in the pre-configured target directory
- $ adb push erlang_23.0_arm /data/local/tmp/erlang_23.0
+ $ adb push erlang /data/local/tmp/erlang
Start an interactive shell onto the target Android device, and launch erl.
$ adb shell
- :/ $ /data/local/tmp/erlang_23.0/bin/erl
+ :/ $ /data/local/tmp/erlang/bin/erl
Eshel VX.Y.Z (abort with ^G)
1> q().
ok
--
2.26.2
