Created on
25/07/18 16:00

Modified on
25/07/18 16:00

Filed under
Android

Tags
android toolchain gsoc

Preface

Toolchain work for Android has been progressing in the last few weeks, finally reaching a stage where a completely working Clang/LLVM toolchain is available. The toolchain can build test programs that run on vanilla AOSP as well as Lineage OS, with proper sanitizer support. Though actually plugging this toolchain into Android build process is not tested yet, the sanitizers for the toolchain is built with the toolchain itself, and various problems in the headers has been fixed. This article explains complex parts in the bootstrap script as well as places where manual intervention is needed.

We're going to build pieces of the toolchain in this order to satisfy dependency:

  • GCC toolchain (binutils, libc objects & headers, compiler)
  • LLVM + Clang
  • Compiler-rt builtins
  • Libunwind
  • Libc++abi
  • Libc++
  • Compiler-rt non-builtins (sanitizers, profilers, etc.)

Set up environment and repositories

This part defaults to using aarch64-linux-android as the target and using the HEAD version of LLVM tools. Edit accordingly if this is not desired. CMake and Ninja is required to follow this guide; install them if they're not present on your system.

Set up GCC for target

GCC is needed for cross compiling with Clang/LLVM. Follow this article on GCC cross-compiling for Android to get a working copy of cross GCC. This should get you through the comment block that reads:

# install GNU binutils
# copy headers into $PREFIX/$TARGET/sys-include
# copy crt*.o lib{c,m,dl}.so to $PREFIX/lib64 and $PREFIX/$TARGET/lib
# install GCC

Note that later Clang/LLVM build requires prebuilt libraries in two different locations. Copy the object files accordingly.

LLVM + Clang

Configure options to note:

  • LLVM_TARGETS_TO_BUILD=AArch64: Enable only AArch64 target. Remember to substitute this if the target is not aarch64 (e.g. ARM for 32 bit)

Compiler-rt builtins

Configure options to note:

  • CMAKE_INSTALL_PREFIX=$PREFIX/lib/clang/7.0.0: Install to Clang "resource path" so that libraries can be automatically found by Clang while compiling.
  • COMPILER_RT_BUILD_BUILTINS=ON and COMPILER_RT_BUILD_*=OFF: Build builtins only as other components require libc++ to build.

Libunwind

Nothing special here.

Libcxxabi

Configure options to note:

  • LIBCXXABI_LIBCXX_INCLUDES="../../libcxx/include": Specify libc++ header path for reference by libc++abi during build.
  • LIBCXXABI_USE_COMPILER_RT=ON: This option name speaks for itself.
  • LIBCXXABI_USE_LLVM_UNWINDER=ON: This option name speaks for itself.

Remember to install libc++abi headers into the prefix as CMake doesn't generate libc++abi header install rules:

sudo cp -R ../include $PREFIX/include/libcxxabi

Libcxx

As discussed in this thread, LLVM HEAD at the time of writing uses NDK headers that are newer than the prebuilt NDK version (r16 vs r14). As a result, we have to rebase to remove commit 85a7702b4cc5d69402791fe685f151cf3076be71 from Libcxx repository:

pushd .. && \
    git fetch --unshallow && \
    git rebase -i 85a7702b4cc5d69402791fe685f151cf3076be71^ && \
    popd

Configure options to note:

  • LIBCXX_CXX_ABI="libcxxabi": Use libcxxabi as the C++ ABI library (instead of libcxxrt or libsupc++).
  • LIBCXX_CXX_ABI_INCLUDE_PATHS="$PREFIX/include/libcxxabi": Reference to libcxxabi headers (installed in the previous step).
  • LIBCXX_USE_COMPILER_RT=ON: This option name speaks for itself.

Note that Android by default combines libc++, libc++abi, and libunwind into a single libc++.so. We'll do this as well so that the executable does not contain stray dynamic link references.

pushd $TARGET/lib
sudo mv libc++.so libc++.so.old
sudo /usr/local/aarch64-linux-android/bin/clang -shared \
    -o libc++.so -Wl,--whole-archive libc++.a libc++abi.a libunwind.a \
    -Wl,--no-whole-archive
popd

Compiler-rt non-builtin (sanitizers, etc.)

Bionic headers as of commit a9713035baecf21f607ef81c8652eb344086966c misses definition for in_addr_t in its headers. It is possible that the Linux headers are expected to define this, but android_kernel_huawei_angler did not define this. Apply this patch on Bionic headers to continue.

Configure options to note:

  • CMAKE_INSTALL_PREFIX=$PREFIX/lib/clang/7.0.0: Install to Clang "resource path" so that libraries can be automatically found by Clang while compiling.
  • COMPILER_RT_BUILD_BUILTINS=OFF and COMPILER_RT_BUILD_*=ON: Build components other than builtins as we have libc++ now.

Testing

# C:
/usr/local/aarch64-linux-android/bin/clang hello.c -o hello
# C++:
/usr/local/aarch64-linux-android/bin/clang++ hello.cc -o hello \
    --stdlib=libc++ --rtlib=compiler-rt
# C++ with sanitizers (ubsan as an example):
/usr/local/aarch64-linux-android/bin/clang++ hello.cc -o hello --stdlib=libc++ \
    -fsanitize=undefined -static-libsan --rtlib=compiler-rt
Comment

Created on
21/07/18 01:00

Modified on
21/07/18 01:00

Filed under
Android

Tags
android toolchain gsoc

Preface

To build the Android Platform, we need a toolchain that can produce executables that link correctly against Android's libc, Bionic. To achieve this, a toolchain targeting aarch64-linux-android (and arm-linux-androideabi) is needed. This article aims to provide a step-by-step guide for reproducing the desired toolchain on all architecture that GCC …

Read More

Created on
16/07/18 00:00

Modified on
16/07/18 00:00

Filed under
Android

Tags
android toolchain

Disclaimer

This article is a stub. This means that it may only serve status report purposes; it may contain severe scientific fallacies and/or inappropriate language, or have missing sections of information. In case of disagreement on previous point, cease consumption/utilization of content in this webpage immediately.

Preface

Many …

Read More

Created on
15/07/18 12:00

Modified on
15/07/18 12:00

Filed under
Android

Tags
android toolchain build

Disclaimer

This article is a stub. This means that it may only serve status report purposes; it may contain severe scientific fallacies and/or inappropriate language, or have missing sections of information. In case of disagreement on previous point, cease consumption/utilization of content in this webpage immediately.

Preface

As …

Read More

Created on
05/07/18 04:00

Modified on
05/07/18 04:00

Filed under
Android

Tags
android gsoc

Preface

As the main target of the second period of my GSoC 2018 project, I have to take down Android build system and accomodating it into Portage, forming a modular building and updating mechanism. So, inevitably, I'll have to deal with the original AOSP build system (Lineage OS's is a …

Read More

Personal details (portrait, CV) © Pengcheng Xu All Rights Reserved; articles licensed under CC BY-SA 4.0.
Powered by Pelican, Bootstrap, and NixOS. Icons by Font Awesome. Generated from 8b4bf12.