This toolchain is optimized for:

• Hard-float ABI (-mfloat-abi=hard)
• Linux Kernel 4.2.X (with legacy support down to 2.6.X)

This toolchain uses:

• GNU GCC 5.2.X (latest)

ArchiToolchain is a minimalistic toolchain which should be used as "arm-eabi" alternative during compiling Linux kernels. It uses, and is possible, thanks to crosstool-NG

Exact config used for building each toolchain is always available in "bin/*-ct-ng.config" file, which can be then used for reproducing the build with latest crostool-NG.

Each ArchiToolchain is pre-optimized for specific target, which means that some options are always used as the default ones. You can still override them by specifying your own flags during compilation.

Check currently available toolchains for the one that suits you best. In case you can't find such, you can always use generic ArchiToolchain, which should work with all targets, but is not pre-optimized for any of them.

You can use ArchiToolchain also in AOSP trees (during compiling of an Android) by adding it in your local manifest. Local manifest for AOSP is located in $(SRCTREE)/.repo/local_manifests/roomservice.xml, where $(SRCTREE) is the root of your AOSP tree. Local manifest may not exist (yet), so you may need to create it firstly.

Example for using this ArchiToolchain with Lollipop AOSP tree:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- cut here -->
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" />
<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" remote="github" revision="architoolchain-5.2-arm-linux-gnueabihf" />
<!-- cut here -->
</manifest>

Example for using this ArchiToolchain with KitKat AOSP tree:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- cut here -->
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" />
<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" remote="github" revision="architoolchain-5.2-arm-linux-gnueabihf" />
<!-- cut here -->
</manifest>

After next repo sync, you should notice that ArchiToolchain repo is available in the path specified by your manifest.