Files
android_development/ndk
David 'Digit' Turner 69eeb8a22f Update the build-toolchain.sh script.
This patch modifies the script to be able to build all prebuilt toolchain
binaries in a single call. I.e. if passed a recent toolchain source package
generated with download-toolchain-sources.sh, then it will build both
GCC 4.2.1 and GCC 4.4.0 and place them in the final prebuilt tarball.

We need this because, while we're going to switch to gcc 4.4.0 by default
in a new version of the NDK, the 4.4.0 C++ compiler is more strict about
various constructs and might refuse to build certain sources. An option
will be given to application developers to use 4.2.1 instead, to keep their
sources building.

Other changes include:

Move all builds into a random temporary directory under /tmp by default,
unless you use --build-out=<path>.

Cleanup the build out directory on succesful build

The generated tarball is now named android-ndk-prebuilt-<date>-<host>.tar.bz2
by default, unless you use the new --release=<name> option which will replace
<date> with <name> instead.

Removal of un-needed files (e.g. info or man pages, libiberty static library,
etc..) to reduce the size of the final tarball.
2009-11-19 13:43:11 -08:00
..
2009-05-07 21:56:40 +02:00

            Android Native Development Kit (NDK)


Welcome, this NDK is designed to allow Android application developers
to include native code in their Android application packages, compiled
as JNI shared libraries.

See docs/CHANGES.TXT for a list of changes since the previous release.

A high-level overview of the NDK's features and limitations can be found
in docs/OVERVIEW.TXT. Please read this document as it contains crucial
information for correct usage.

See docs/STABLE-APIS.TXT for the list of frozen binary APIs exposed by
this NDK, as well as the corresponding system image versions that support
them.

Before using the NDK, you will need to follow the steps described by
docs/INSTALL.TXT which lists the NDK pre-requisites and the steps needed
to set it up properly on your machine.

We recommend developers to make themselves familiar with JNI concepts. Also
note that the NDK is *not* a good way to write non-JNI native code for the
Android platform.

See docs/HOWTO.TXT for a few useful tips and tricks when using the NDK.

See docs/SYSTEM-ISSUES.TXT for a list of important issues related to
the Android system images that all NDK developers should be aware of.

Finally, discussions related to the Android NDK happen on the public
"android-ndk" forum located at the following address:

    http://groups.google.com/group/android-ndk