History log of /ndk/build/core/add-toolchain.mk
Revision Date Author Comments
ed6927f25557b71183800a69c82cfe730b2648b9 23-Dec-2011 David 'Digit' Turner <digit@google.com> Remove hard-coded ABI names from build scripts.

This patch removes some of the hard-coded ABI names from our build
scripts. Now, each toolchain's config.mk is expected to provide a
TOOLCHAIN_ARCH definition corresponding to the target architecture
it supports.

This makes it easier to add support for new architectures or ABIs
in the NDK, just write a config.mk for your toolchain like:

TOOLCHAIN_ARCH := myarch
TOOLCHAIN_ABIS := myabi [myabi2]

Change-Id: Ib2f89102b343390fb16f66f63ee7e26f852701c2
ea573da2c3f1a8379f4344d023035fdf795c768d 24-Jul-2010 David 'Digit' Turner <digit@google.com> Update toolchain to arm-linux-androideabi-4.4.3

You can still use the old one with NDK_TOOLCHAIN=arm-eabi-4.4.0
defined in your environment.

Removed support for arm-eabi-4.2.1

+ Add --mingw option to build/tools/build-gcc.sh

Change-Id: I03f6b7cb67b1110e5794da9c4e9b6b8d1e029bb9
a1d764b5d215601e007e01186de0be0db51df900 09-Apr-2010 The Android Open Source Project <initial-contribution@android.com> NDK snapshot from development/ndk/

Change-Id: I154f2fd3828ffd937c82410f5f9995402d7be15e
85459717ff102979c1b98f65d23a37538d177d22 05-Apr-2010 David Turner <digit@dhcp-172-28-237-78.par.corp.google.com> Properly select the toolchain based on the ABIs we want to build for.

Before this patch, it was not possible to use the x86-4.2.1 toolchain
without explicitely selecting it with NDK_TOOLCHAIN. Now if all toolchains
are installed, a simple line like the following just works:

APP_ABI := armeabi armeabi-v7a x86

Change-Id: I58ff6dda09a6d1406a83a45af542bba35a3caa40
48ef1859ef0bb25547e5aceeedb9b175c6193bc5 07-May-2009 David 'Digit' Turner <digit@google.com> Initial import of new NDK into donut tree