Difference between revisions of "Build LDC for Android"

From D Wiki
Jump to: navigation, search
(Updating for latest 1.1.0 beta, first pass)
(Remove build instructions for ldc and future directions)
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
This page will show you how to build a ldc cross-compiler for Android/ARM on linux or Windows 10 (by using the new bash/Ubuntu linux subsystem), along with how to build and run both the druntime/phobos tests and an Android D app using the cross-compiler.  [https://github.com/joakim-noah/android/releases Prebuilt native and cross-compilers are available here].
+
This page shows you how to build and run the standard library's tests using ldc on linux or Windows 10 (by using the new bash on linux subsystem), both as a command-line binary and as a GUI Android app.  [https://github.com/ldc-developers/ldc/releases Prebuilt binaries of ldc are available here].
  
All of the standard library's unit tests and the full compiler testsuite passes on Android/ARM.  Remaining work to be done is listed last.
+
All of the standard library's unit tests and most of the compiler testsuite passes on Android/ARM.
  
 
==Prerequisites==
 
==Prerequisites==
  
* linux shell, where you'll build and run ldc
+
* linux/x64 shell, where you'll build and run ldc
 
** You can use a virtual machine like VirtualBox/VMware, with at least 512 MB of memory and 1 GB of swap, particularly if building the phobos unit tests, and 10 GB of disk space.
 
** You can use a virtual machine like VirtualBox/VMware, with at least 512 MB of memory and 1 GB of swap, particularly if building the phobos unit tests, and 10 GB of disk space.
** Windows 10: You can alternately use Bash on Ubuntu on Windows (Windows Subsystem for Linux)
+
** Windows 10: You can alternately use Bash on Windows (the Windows Subsystem for Linux), [[#Notes_for_Bash_on_Ubuntu_on_Windows|see full steps below]]
* C++ compiler and toolchain, to build a slightly patched llvm and parts of ldc
 
 
* A pre-built D compiler for linux, as the ldc frontend is written in D.
 
* A pre-built D compiler for linux, as the ldc frontend is written in D.
 
** You can get [http://dlang.org/download the official dmd release for linux] or [https://github.com/ldc-developers/ldc/releases one of the ldc releases for linux].  Many distros also have D compiler packages.
 
** You can get [http://dlang.org/download the official dmd release for linux] or [https://github.com/ldc-developers/ldc/releases one of the ldc releases for linux].  Many distros also have D compiler packages.
* Common development tools, such as CMake and git, and ldc uses libconfig++
+
* Common development tools, such as CMake and ninja
* ldc/druntime/phobos source
+
* Android native toolchain, [https://developer.android.com/ndk/index.html the NDK] and optionally [https://developer.android.com/studio/index.html the SDK]
** Get the source using git, as these Android patches were tested on the master branch of each repository.
+
** The SDK is only needed if you want to package a GUI app; the NDK is enough if you just want to build a command-line binary, such as a test runner.
* llvm 3.9 source, either from the official release or git
 
* Android native toolchain, [http://developer.android.com/ndk/index.html the NDK] and optionally [http://developer.android.com/sdk/index.html the SDK]
 
** The SDK is necessary if you want to package a GUI app; the NDK is enough if you just want to build a command-line binary, such as a test runner.  If you get the SDK, all that's needed is the "SDK Tools only" version, as long as you don't plan on using their IDE integration.  I will only write about using the command-line tools.  The SDK requires JDK 7: follow their instructions to make sure it's installed right.
 
 
* Android/ARM, whether a device or emulator
 
* Android/ARM, whether a device or emulator
 
** The SDK comes with an emulator.  I use actual hardware, so that's what I'll discuss.
 
** The SDK comes with an emulator.  I use actual hardware, so that's what I'll discuss.
  
==Notes for Bash on Ubuntu on Windows==
+
===Notes for Bash on Ubuntu on Windows===
 
* Necessary packages
 
* Necessary packages
 
<syntaxhighlight lang=bash>
 
<syntaxhighlight lang=bash>
Line 33: Line 29:
 
<syntaxhighlight lang=bash>
 
<syntaxhighlight lang=bash>
 
cd ~
 
cd ~
curl -L -O http://downloads.dlang.org/releases/2.x/2.072.1/dmd_2.072.1-0_amd64.deb
+
curl -L -O http://downloads.dlang.org/releases/2.x/2.075.1/dmd_2.075.1-0_amd64.deb
sudo dpkg -i dmd_2.072.1-0_amd64.deb
+
sudo dpkg -i dmd_2.075.1-0_amd64.deb
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 40: Line 36:
 
<syntaxhighlight lang=bash>
 
<syntaxhighlight lang=bash>
 
sudo mkdir -p /opt/android-sdk/ndk-bundle
 
sudo mkdir -p /opt/android-sdk/ndk-bundle
curl -L -O https://dl.google.com/android/repository/android-ndk-r13b-linux-x86_64.zip
+
curl -L -O https://dl.google.com/android/repository/android-ndk-r15c-linux-x86_64.zip
sudo unzip android-ndk-r13b-linux-x86_64.zip 'android-ndk-r13b/*' -d /opt/android-sdk/ndk-bundle
+
sudo unzip android-ndk-r15c-linux-x86_64.zip 'android-ndk-r15c/*' -d /opt/android-sdk/ndk-bundle
export NDK=/opt/android-sdk/ndk-bundle/android-ndk-r13b
+
export NDK=/opt/android-sdk/ndk-bundle/android-ndk-r15c
 
</syntaxhighlight>
 
</syntaxhighlight>
  
As Windows Subsystem for Linux does not support USB you have to install Android SDK and Ant on your windows system  
+
As Windows Subsystem for Linux does not support USB, you have to install Android SDK and Ant on your Windows system and execute the commands "android" and "ant" from your DOS console.  
and execute the commands "android" and "ant" from your DOS console.  
 
  
==Compile llvm==
+
==Run the druntime and phobos unit tests==
 
 
Get the source for llvm, either [http://llvm.org/releases/download.html#3.9.1 the latest official 3.9.1 release] or [https://github.com/llvm-mirror/llvm a git repository, like this llvm mirror].  [https://gist.github.com/joakim-noah/1fb23fba1ba5b7e87e1a Download the patch for llvm], apply it, and then [http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary build llvm as you would normally], with the ARM target:
 
 
 
<syntaxhighlight lang=bash>
 
curl -L -O http://releases.llvm.org/3.9.1/llvm-3.9.1.src.tar.xz
 
tar xvf llvm-3.9.1.src.tar.xz
 
cd llvm-3.9.1.src/
 
curl -O https://gist.githubusercontent.com/joakim-noah/1fb23fba1ba5b7e87e1a/raw/ff54ecbe824b5f45669ea3a86f136ded16b1dd91/android_tls
 
git apply android_tls
 
 
 
mkdir build
 
cd build/
 
cmake .. -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=ARM
 
make -j5
 
</syntaxhighlight>
 
 
 
==Build ldc for Android/ARM==
 
  
Clone the ldc repository, check out the release-1.0.0 branch, [https://gist.github.com/joakim-noah/eff6d4ccca7975f32c3c35eb85f29554 apply the Android patch], set the DMD environment variable to the path of your pre-built D compiler, set the NDK environment variable to the location of your NDK and NDK_ARCH to its architecture, either x86 or x86_64, and [[Building LDC from source|build ldc as usual]]:
+
You can build the druntime and phobos unit tests and run the command-line test runner binaries on Android (don't add the -j5 flag to build in parallel unless you have gigabytes of memory available, as compiling some of the phobos modules' tests takes a fair amount of RAM):
  
 
<syntaxhighlight lang=bash>
 
<syntaxhighlight lang=bash>
cd ../../
+
make druntime-test-runner phobos2-test-runner
git clone --recursive https://github.com/ldc-developers/ldc.git
 
cd ldc/
 
git checkout -b ddmd origin/release-1.0.0
 
git submodule update
 
curl -O https://gist.githubusercontent.com/joakim-noah/eff6d4ccca7975f32c3c35eb85f29554/raw/671c0d99e7b0d312ba5f197c158551ad0cbbebcc/ldc_1.0.0_android_arm
 
git apply ldc_1.0.0_android_arm
 
 
 
mkdir build
 
cd build/
 
export DMD=/path/to/your/dmd2/linux/bin64/dmd
 
export NDK=/path/to/your/android-ndk-r12
 
export NDK_ARCH=x86_64
 
cmake .. -DLLVM_CONFIG=../../llvm-3.9.1.src/build/bin/llvm-config
 
make ldc2 -j5
 
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Download and apply [https://gist.github.com/joakim-noah/069036835dd92cf648a8219bfe4d68c3 the patch for druntime] and [https://gist.github.com/joakim-noah/17c5c37c32609dec218ba6031658a2c9 the patch for phobos] before building them:
+
Copy the test runners to your device and run them.  Assuming you have an SSH server set up on the computer where you're building with the linux shell and its IP address is 192.168.35.7, you can scp the binaries into [https://play.google.com/store/apps/details?id=com.termux&hl=en the Termux Android app] with these commands and run the tests:
  
 
<syntaxhighlight lang=bash>
 
<syntaxhighlight lang=bash>
cd ../runtime/druntime/
+
apt install openssh
curl -O https://gist.githubusercontent.com/joakim-noah/069036835dd92cf648a8219bfe4d68c3/raw/9f42b65b0a17c9a15edc800bcdf644de99ffa72c/druntime_1.0.0_ldc_arm
+
scp jo@192.168.35.7:"/path/to/your/ldc/build/runtime/{druntime,phobos2}-test-runner" .
git apply druntime_1.0.0_ldc_arm
+
./druntime-test-runner
 
+
./phobos2-testrunner
cd ../phobos/
 
curl -O https://gist.githubusercontent.com/joakim-noah/17c5c37c32609dec218ba6031658a2c9/raw/689d1fc66cd0661a93d0eee55809569aeda1a0f2/phobos_1.0.0_ldc_arm
 
git apply phobos_1.0.0_ldc_arm
 
 
 
cd ../../build/
 
make druntime-ldc phobos2-ldc -j5
 
 
</syntaxhighlight>
 
</syntaxhighlight>
  
More info about the Android/ARM patches can be [https://github.com/joakim-noah/android/releases/tag/ddmd found with their release].
+
The tests take about 25 seconds to run on my quad-core tablet: all should pass.  One module, core.sync.semaphore, will fail for any Android older than 6.0, [https://github.com/D-Programming-Language/druntime/pull/784#issuecomment-42777328 because sem_destroy used to work differently in bionic]. You can also run the tests for specified modules by passing their names to the test runner:
 
 
==Build a command-line executable==
 
 
 
Now that we have a D cross-compiler and cross-compiled the standard library for Android/ARM, let's try building a small program, the classic Sieve of Eratosthenes single-core benchmark:
 
  
 
<syntaxhighlight lang=bash>
 
<syntaxhighlight lang=bash>
./bin/ldc2 -mtriple=armv7-none-linux-androideabi
+
./druntime-test-runner core.thread core.sync.semaphore
          -c ../tests/d2/dmd-testsuite/runnable/sieve.d
+
./phobos2-testrunner std.datetime std.random
 
 
$NDK/toolchains/llvm/prebuilt/linux-$NDK_ARCH/bin/clang -Wl,-z,nocopyreloc
 
--sysroot=$NDK/platforms/android-9/arch-arm -lgcc
 
-gcc-toolchain $NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-$NDK_ARCH
 
-target armv7-none-linux-androideabi -no-canonical-prefixes -fuse-ld=bfd
 
-Wl,--fix-cortex-a8 -Wl,--no-undefined -Wl,-z,noexecstack -Wl,-z,relro
 
-Wl,-z,now -fPIE -pie -mthumb -Wl,--export-dynamic -lc -lm sieve.o lib/libphobos2-ldc.a
 
lib/libdruntime-ldc.a -o sieve
 
 
</syntaxhighlight>
 
</syntaxhighlight>
  
The compiler and linker flags were taken from [http://wiki.dlang.org/Build_DMD_for_Android#Default_build_of_the_C_sample_app the output from running a NDK sample app's build scripts in verbose mode].
+
==Run the druntime and phobos unit tests in an apk==
 
 
Run this program on an Android device or emulator.  I've solely run on actual Android devices, with either [https://play.google.com/store/apps/details?id=com.termux&hl=en a terminal app] or [https://play.google.com/store/apps/details?id=berserker.android.apps.sshdroid&hl=en an SSH server app].  Once you have either of those apps installed, copy the sieve program to the device, go to the app's local directory by typing 'cd' at its command-line, copy the program there, and run it:
 
 
 
<syntaxhighlight lang=bash>
 
cd
 
cp /sdcard/sieve .
 
./sieve foobar
 
</syntaxhighlight>
 
 
 
The program requires an argument, which is ignored.  If it runs correctly, you'll see the following output, saying it ran 10 times and found 1899 primes in the first 8191 integers:
 
 
 
<syntaxhighlight lang=bash>
 
10 iterations
 
1899 primes
 
</syntaxhighlight>
 
 
 
==Run the druntime and phobos unit tests==
 
 
 
Go back to the linux shell and build the tests for druntime and phobos (don't add the -j5 flag to build in parallel unless you have GBs of memory available, as compiling some of the phobos modules' tests takes a fair amount of RAM):
 
 
 
<syntaxhighlight lang=bash>
 
make test-runner
 
</syntaxhighlight>
 
 
 
Copy the test-runner and [https://github.com/joakim-noah/android/releases/download/ddmd/test.list this list of druntime and phobos modules] to your device and run it.  I use the SSH server app on a random port, here's what I'd do (replace 192.168.35.7 with the IP address of your device and 20345 with the port you configured for the SSH service):
 
 
 
<syntaxhighlight lang=bash>
 
scp -P20345 test.list runtime/test-runner jo@192.168.35.7:
 
ssh -p20345 jo@192.168.35.7
 
./test-runner
 
</syntaxhighlight>
 
 
 
The tests take about 40 seconds to run on my dual Cortex-A15 device: all should pass.  Two passing test blocks in rt.lifetime were disabled, as they cause problems for subsequent tests.  One module, core.sync.semaphore, is not included in the list of modules, [https://github.com/D-Programming-Language/druntime/pull/784#issuecomment-42777328 because sem_destroy works differently in bionic], which has been amended to match in the latest Android.  Two test blocks in std.net.curl may fail, depending on what version of curl they're run against.
 
 
 
==Build a sample OpenGL Android app ported to D==
 
  
Clone [https://github.com/joakim-noah/android my android repository], which contains several headers and a C/OpenGL app from the NDK, translated to D:
+
You can also run the tests as part of a GUI app, ie an apk, which is a slightly different runtime environment.  First, you can try [[Build D for Android#Build_a_sample_OpenGL_ES_1.0_GUI_app_ported_to_D|cross-compiling a sample GUI app from the NDK that has been translated from C to D, as shown here]].  That simple OpenGLES 1.0 GUI app can be modified to run all the tests, which is what we'll do next.  Clone my Android repo, if you haven't already, go to the native-activity sample app, and create the output directory the SDK expects:
  
 
<syntaxhighlight lang=bash>
 
<syntaxhighlight lang=bash>
 
cd ../../
 
cd ../../
 
git clone https://github.com/joakim-noah/android.git
 
git clone https://github.com/joakim-noah/android.git
</syntaxhighlight>
 
 
You can find more info about building using the NDK in [[Build DMD for Android#Build_an_Android_sample_app|my earlier instructions for Android/x86]].  This is just the essence, redone for ARM.  You will build a purely native D apk without any Java source.
 
 
Go to the native-activity sample app, compile the D source, then link the objects into a shared library and place it in the directory that the SDK expects:
 
  
<syntaxhighlight lang=bash>
 
 
cd android/samples/native-activity/
 
cd android/samples/native-activity/
 
../../../ldc/build/bin/ldc2 -mtriple=armv7-none-linux-androideabi
 
                            -I../../ -c jni/main.d
 
 
../../../ldc/build/bin/ldc2 -mtriple=armv7-none-linux-androideabi
 
                            -I../../ -c ../../android/sensor.d
 
 
../../../ldc/build/bin/ldc2 -mtriple=armv7-none-linux-androideabi
 
                      -I../../ -c ../../android_native_app_glue.d
 
 
 
mkdir -p libs/armeabi-v7a/
 
mkdir -p libs/armeabi-v7a/
 
$NDK/toolchains/llvm/prebuilt/linux-$NDK_ARCH/bin/clang -Wl,-soname,libnative-activity.so
 
-shared --sysroot=$NDK/platforms/android-9/arch-arm main.o sensor.o
 
../../../ldc/build/lib/libphobos2-ldc.a ../../../ldc/build/lib/libdruntime-ldc.a
 
android_native_app_glue.o -lgcc
 
-gcc-toolchain $NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-$NDK_ARCH
 
-no-canonical-prefixes -fuse-ld=bfd -target armv7-none-linux-androideabi
 
-Wl,--fix-cortex-a8 -Wl,--no-undefined -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now
 
-mthumb -L$NDK/platforms/android-9/arch-arm/usr/lib -llog -landroid -lEGL -lGLESv1_CM
 
-lc -lm -o libs/armeabi-v7a/libnative-activity.so
 
</syntaxhighlight>
 
 
Package the app as the SDK directs.  I use the older Ant approach, which is being deprecated: replace it with the Gradle command from a newer SDK if needed.  For Ant, set the path to your SDK, then run these commands:
 
 
<syntaxhighlight lang=bash>
 
export SDK=/path/to/your/android-sdk-linux
 
$SDK/tools/android update project -p . -s --target 1
 
ant debug
 
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Transfer the resulting bin/NativeActivity-debug.apk to your device, go to Settings->Security and allow installation of apps from unknown sources, ie outside the Play Store, then install it.  Go to your app folder and run the app named NativeActivity: it'll show a black screen and start flashing a bunch of colors upon a touch.
+
Download and apply [https://gist.github.com/joakim-noah/8ba3cd4958266f357295 a small patch to have the sample app invoke the test runner] and [https://gist.github.com/joakim-noah/348edc378d47fb90e32708be19286a2e a patch for the test runner in druntime], then build the tests into a shared library this time:
 
 
==Run the druntime and phobos unit tests in an apk==
 
 
 
Create the libs/armeabi-v7a/ directory as shown in the last section, then download and apply [https://gist.github.com/joakim-noah/8ba3cd4958266f357295 the small patch to have the sample app invoke the test runner], and rebuild:
 
  
 
<syntaxhighlight lang=bash>
 
<syntaxhighlight lang=bash>
Line 212: Line 85:
 
git apply native_ldc_arm
 
git apply native_ldc_arm
  
cd ../../../ldc/build/
+
cd ../../../ldc/runtime/druntime/
 +
curl -O https://gist.githubusercontent.com/joakim-noah/348edc378d47fb90e32708be19286a2e/raw/2b473ff45ff4abc68852ebb1868354b8528026e0/druntime_1.3_ldc_arm
 +
git apply druntime_1.3_ldc_arm
 +
 
 +
cd ../../build/
 
make test-runner-apk
 
make test-runner-apk
 
</syntaxhighlight>
 
</syntaxhighlight>
Line 222: Line 99:
 
<syntaxhighlight lang=bash>
 
<syntaxhighlight lang=bash>
 
cd ../../android/samples/native-activity/
 
cd ../../android/samples/native-activity/
 +
export SDK=/path/to/your/android-sdk-linux
 +
$SDK/tools/android update project -p . -s --target 1
 
ant debug
 
ant debug
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Transfer the resulting bin/NativeActivity-debug.apk to your device, and install it as before.  Also, copy [https://github.com/joakim-noah/android/releases/download/ddmd/test.list the list of modules to test] to the /sdcard/ directory.  The app will append its results to /sdcard/test.log, so if you happen to have a file with that name, move it.
+
Transfer the resulting bin/NativeActivity-debug.apk to your device and install it.  Also, copy [https://github.com/joakim-noah/android/releases/download/tea/test.list the list of modules to test] to the /sdcard/ directory.  The app will append its results to /sdcard/test.log, so if you happen to have a file with that name, move it.
 
 
This time, it should show a black screen for about a minute, while all the tests run.  A touch after that and it should start flashing a bunch of colors.  If not, look at the output in /sdcard/test.log and check if the app hung after any particular tested module.  You can remove that module from test.list and try running again.
 
 
 
==Directions for future work==
 
 
 
* Port the NDK support libraries and more of its sample apps to D, including apps that require using JNI, ie interfacing with Java.
 
 
 
* Two modules, core.thread and std.parallelism, have tests that cause the test runner to hang when run from inside an apk as opposed to on the command line.  Trying to suspend a thread from another thread, either directly by calling thread_suspendAll() or indirectly when the GC runs a full collect on a multi-threaded app, fails, because pthread_kill doesn't return and hangs the calling thread.  It appears that this is related to using SIGUSR1/2 for suspending and resuming threads: simply switching the two signals works around this issue for now.
 
 
 
* You may notice that I added an empty main function in the D translation of the C sample app: that's a hack to build a shared library.  Some of the linux shared library support in druntime's rt.sections_elf_shared may eventually be integrated with Android to get rid of that.
 
  
* Now that we can write D code for Android, it'll make building easier if the D cross-compilers are integrated with a build tool, like [https://github.com/atilaneves/reggae reggae] or [http://jasonwhite.github.io/button/ Button].
+
The app should show a black screen for about a minute, while all the tests run.  A touch after that and it should start flashing a bunch of colors.  If not, look at the output in /sdcard/test.log and check if the app hung after any particular tested module. You can remove that module from test.list and try running again.
  
[[Category:LDC]]
 
 
[[Category: Android]]
 
[[Category: Android]]

Latest revision as of 10:39, 10 November 2018

This page shows you how to build and run the standard library's tests using ldc on linux or Windows 10 (by using the new bash on linux subsystem), both as a command-line binary and as a GUI Android app. Prebuilt binaries of ldc are available here.

All of the standard library's unit tests and most of the compiler testsuite passes on Android/ARM.

Prerequisites

  • linux/x64 shell, where you'll build and run ldc
    • You can use a virtual machine like VirtualBox/VMware, with at least 512 MB of memory and 1 GB of swap, particularly if building the phobos unit tests, and 10 GB of disk space.
    • Windows 10: You can alternately use Bash on Windows (the Windows Subsystem for Linux), see full steps below
  • A pre-built D compiler for linux, as the ldc frontend is written in D.
  • Common development tools, such as CMake and ninja
  • Android native toolchain, the NDK and optionally the SDK
    • The SDK is only needed if you want to package a GUI app; the NDK is enough if you just want to build a command-line binary, such as a test runner.
  • Android/ARM, whether a device or emulator
    • The SDK comes with an emulator. I use actual hardware, so that's what I'll discuss.

Notes for Bash on Ubuntu on Windows

  • Necessary packages
sudo apt-get install build-essential
sudo apt-get install git
sudo apt-get install cmake
sudo apt-get install unzip
sudo apt-get install libconfig-dev
  • DMD Compiler
cd ~
curl -L -O http://downloads.dlang.org/releases/2.x/2.075.1/dmd_2.075.1-0_amd64.deb
sudo dpkg -i dmd_2.075.1-0_amd64.deb
  • Android Native Development Kit
sudo mkdir -p /opt/android-sdk/ndk-bundle
curl -L -O https://dl.google.com/android/repository/android-ndk-r15c-linux-x86_64.zip
sudo unzip android-ndk-r15c-linux-x86_64.zip 'android-ndk-r15c/*' -d /opt/android-sdk/ndk-bundle
export NDK=/opt/android-sdk/ndk-bundle/android-ndk-r15c

As Windows Subsystem for Linux does not support USB, you have to install Android SDK and Ant on your Windows system and execute the commands "android" and "ant" from your DOS console.

Run the druntime and phobos unit tests

You can build the druntime and phobos unit tests and run the command-line test runner binaries on Android (don't add the -j5 flag to build in parallel unless you have gigabytes of memory available, as compiling some of the phobos modules' tests takes a fair amount of RAM):

make druntime-test-runner phobos2-test-runner

Copy the test runners to your device and run them. Assuming you have an SSH server set up on the computer where you're building with the linux shell and its IP address is 192.168.35.7, you can scp the binaries into the Termux Android app with these commands and run the tests:

apt install openssh
scp jo@192.168.35.7:"/path/to/your/ldc/build/runtime/{druntime,phobos2}-test-runner" .
./druntime-test-runner
./phobos2-testrunner

The tests take about 25 seconds to run on my quad-core tablet: all should pass. One module, core.sync.semaphore, will fail for any Android older than 6.0, because sem_destroy used to work differently in bionic. You can also run the tests for specified modules by passing their names to the test runner:

./druntime-test-runner core.thread core.sync.semaphore
./phobos2-testrunner std.datetime std.random

Run the druntime and phobos unit tests in an apk

You can also run the tests as part of a GUI app, ie an apk, which is a slightly different runtime environment. First, you can try cross-compiling a sample GUI app from the NDK that has been translated from C to D, as shown here. That simple OpenGLES 1.0 GUI app can be modified to run all the tests, which is what we'll do next. Clone my Android repo, if you haven't already, go to the native-activity sample app, and create the output directory the SDK expects:

cd ../../
git clone https://github.com/joakim-noah/android.git

cd android/samples/native-activity/
mkdir -p libs/armeabi-v7a/

Download and apply a small patch to have the sample app invoke the test runner and a patch for the test runner in druntime, then build the tests into a shared library this time:

curl -O https://gist.githubusercontent.com/joakim-noah/8ba3cd4958266f357295/raw/a52fcf1e63715f8b1bd3527afaa85872087b0f30/native_ldc_arm
git apply native_ldc_arm

cd ../../../ldc/runtime/druntime/
curl -O https://gist.githubusercontent.com/joakim-noah/348edc378d47fb90e32708be19286a2e/raw/2b473ff45ff4abc68852ebb1868354b8528026e0/druntime_1.3_ldc_arm
git apply druntime_1.3_ldc_arm

cd ../../build/
make test-runner-apk

This assumes that the ldc and android repositories are in the same directory, as shown in these instructions. If not, modify ANDROID_DIR in the CMake build script to use the path you want.

Finally, package the test runner apk:

cd ../../android/samples/native-activity/
export SDK=/path/to/your/android-sdk-linux
$SDK/tools/android update project -p . -s --target 1
ant debug

Transfer the resulting bin/NativeActivity-debug.apk to your device and install it. Also, copy the list of modules to test to the /sdcard/ directory. The app will append its results to /sdcard/test.log, so if you happen to have a file with that name, move it.

The app should show a black screen for about a minute, while all the tests run. A touch after that and it should start flashing a bunch of colors. If not, look at the output in /sdcard/test.log and check if the app hung after any particular tested module. You can remove that module from test.list and try running again.