New CrystaX NDK 10 is available, offering numerous great features and improvements; perhaps you should check it out instead of using old one.
Improved Android NDK r4
Here are customized distribution of Android NDK r4b which I have rebuilt from official sources. Support of C++ exceptions, RTTI and Standard C++ Library added. There was no many modifications, you can see them in my patch
Update: New bug-fix release android-ndk-r4-crystax-2 ready! List of problems fixed:
- Snow Leopard ndk-gdb bug: ameabi instead of armeabi
- Snow Leopard ndk-gdb call gensub function not available in BSD awk
- ndk-gdb fail if both emulator and device attached
- Compiler error when including asm/byteorder.h
- ndk-build fails in case of parallel build
- Ability to download toolchain sources over http
- gdbserver binary incompatibility
- Build gcc with threads enabled
- ndk-build: problems with parameters containing spaces
Update 2: New bug-fix release android-ndk-r4-crystax-3 ready! One important fix included:
Update 3: New bug-fix release android-ndk-r4-crystax-4 ready! List of problems fixed:
- Install Failed
- Could not package toolchain source archive ?. See
- Build failed on Windows 7 with UAC enabled
- Mac OS X: Build failed if there is no gawk installed
We have plans for the further evolution of CrystaX NDK. We want to make it a comprehensive toolkit for native Android development, providing a solid basis for any POSIX-conforming software to be able run on Android without significant rewriting. To do that, we're asking for help from the community.
We've started a fundraising campaign on BountySource to continue the development of CrystaX NDK and keep it available free to all Android developers. We're asking everyone interested in the further evolution of native development for Android to help us. We would very much appreciate any kind of help - whether it is funding, contributions to the project by sending us patches, or helping to spread the news all over the world.
Please read more about CrystaX NDK’s history and our plans - and help us do that.
The content of the CrystaX NDK is covered by various open-source licenses. See the copyright disclaimers in each respective file for details.
Note that the CrystaX NDK release packages also contain prebuilt binaries for the compiler, linker, archiver, etc. The source codes for the toolchains are available at GitHub (you can use the build script to download it automatically).
The prebuilt GCC and companion binaries (GDB, binutils etc) are covered by either the GNU General Public License (GPL) or the GNU Lesser General Public License (LGPL). For details, see the files COPYING and COPYING.LIB under $NDK/toolchains/<toolchain>/prebuilt/<system>.
The prebuilt LLVM/Clang toolchains are covered by the LLVM "BSD" license.
Basically, licensing rules are the same as for Google's Android NDK - i.e., both commercial and non-commercial usage allowed. The only additions are regarding CrystaX parts, which are covered by a permissive BSD 2-clause license.
How to build
You can also build your own distribution if you don't want to use my prebuilt versions. To do it, follow instructions below.
Required development tools:
- For Windows, a recent release of Cygwin is required
- GNU Make 3.81 or later
- GNU Makeinfo (most recent version)
- GIT (for downloading toolchain sources)
- Most recent GNU Libtool packages (automake, autoconf etc)
- GNU C/C++ 3.x or later (for Windows, it should be exactly 3.x, not 4.x)
- ncurses library (for Cygwin, it should be ncurses-devel package)
- GNU flex (most recent version)
- patch utility. Most likely, it is already installed if you are using Linux or Mac OS X; however, in Cygwin it should be installed explicitly
- Download my patch and store it somewhere
- Download android-ndk-r4b for your platform from android web site
- Unpack downloaded file and go to directory android-ndk-r4b
- For Windows 7 and Vista users: fix permissions of the just unpacked folder. Type in terminal:
cmd /c "icacls . /grant Everyone:(F) /T"
- Apply my patch:
patch -p1 <path-to-my-patch
- Point environment variable ANDROID_NDK_ROOT to the current directory:
- For Windows users: point environment variable CC to the GCC 3:
- For Mac users: if you're planned to run built package on earlier versions of Mac OS X (say, you build it on
Snow Leopard but want to run it also on Leopard), environment variables CC and LDFLAGS should be specified.
If this is not case, just ignore this point. Otherwise, type in terminal:
CC="gcc -isystem /Developer/SDKs/MacOSX10.4u.sdk -mmacosx-version-min=10.4" LDFLAGS="-Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk" export CC LDFLAGSThis will result in binaries which could run on Tiger and later versions; change SDK to another if minimal target is not Tiger.
- Download android toolchain sources:
./build/tools/download-toolchain-sources.sh --release=myrelease --package --over-http --verbose --for-date=2010-07-15It will take some time depending on you network connectivity. Finally, it will download sources and pack them to the package /tmp/android-ndk-toolchain-myrelease.tar.bz2
- Run build script:
./build/tools/rebuild-all-prebuilt.sh --verbose --package --toolchain-src-pkg=/tmp/android-ndk-toolchain-myrelease.tar.bz2It will unpack android toolchain sources (including binutils, gcc and gdb), patch and compile them. It could take lot of time depending on your configuration so be patient.
- Finally, when build script finished, it will print name of the compiled toolchain (something like
/tmp/android-ndk-prebuilt-20100716-linux-x86.tar.bz2, actual name will depend on current date).
Run the commands:
rm -Rf ./build/prebuilt tar xjvf /tmp/android-ndk-prebuilt-20100716-linux-x86.tar.bz2
- Now you are ready to test it. Try to compile application hello-jni (I've modified it, so there are STL and exceptions in the code) using instructions from Android team