1. Introduction
-----------------------------------------------------------------------------
-We currently recommend Ubuntu Natty (11.04) or later. Current work has been
-done here. Additionally, building from OSX Snow Leopard is working.
+We currently recommend Ubuntu "Precise Pangolin" (12.04) 64Bit. This is what our continuous
+integration system "jenkins" is using.
+Additionally, building from OSX Snow Leopard is working.
NOTE TO NEW USERS: All lines that are prefixed with the '#'
character are commands that need to be typed into a terminal window /
If you run a 64bit operating system you will also need to get ia32-libs
# sudo apt-get install ia32-libs
+
+The following versions are used on our continuous integration system "jenkins". Other (newer)
+versions might work as well.
+
+JDK: openjdk-6-jdk (java version "1.6.0_27")
+JRE: openjre-6-jre (java version "1.6.0_27")
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To develop XBMC for Android the Android SDK and NDK are required.
-Because the Android NDK is lacking support for wide characters (wchar_t)
-which XBMC relies on for Unicode implementation, a third-party NDK
-from Crystax is being used.
--------------------------------------------------------------------
3.1. Getting the Android SDK and NDK
--------------------------------------------------------------------
To get the Android SDK, go to http://developer.android.com/sdk and
-download the latest version for your operating system. The Crystax NDK
-can be downloaded from http://www.crystax.net/en/android/ndk
-
-[NOTICE] Compiling XBMC for Android requires at least Crystax Android NDK
- Revision 7b. Crystax Android NDK Revision 7 and earlier do not work
- properly for our cause. The corresponding Crystax NDK version
- is android-ndk-r7-crystax-5.beta3 Do not use the standard Android NDK.
-
-[NOTICE] We previously used android-ndk-r7-crystax-5.beta2, but it produced
- binaries that would NOT run on Jellybean 4.2. At this time,
- android-ndk-r7-crystax-5.beta3 is required.
-
+download the latest version for your operating system. The NDK
+can be downloaded from http://developer.android.com/tools/sdk/ndk/
+
+[NOTICE] Compiling XBMC for Android requires Android NDK
+ Revision r9. For the SDK just use the latest available.
+ It will work.
+
After downloading the SDK and NDK extract the files contained in the
-archives to your harddisk.
+archives to your harddisk. For our example we are extracting in the following
+directories (this matches the example from tools/depends/README aswell):
+
+NDK (referenced as <android-ndk> from now on):
+/opt/android-ndk-r9
+
+TOOLCHAIN (arm) (referenced as <android-toolchain-arm> from now on):
+/opt/arm-linux-androideabi-4.8-vanilla/android-14
+
+TOOLCHAIN (x86) (referenced as <android-toolchain-x86> from now on):
+/opt/x86-linux-4.8-vanilla/android-14
+
+SDK (referenced as <android-sdk> from now on):
+/opt/android-sdk-linux
Make sure you have a recent JRE and JDK installed otherwise the
-Android SDK will not work.
+Android SDK will not work. (see point 2.)
--------------------------------------------------------------------
3.2. Installing Android SDK packages
the Android NDK which you earlier extracted to <android-ndk>. The
following commands will create a toolchain suitable for the most
common scenario.
-The --install-dir option (and therefore the <android-toolchain> value)
-specifies where the resulting toolchain should be installed (your choice).
+The --install-dir option (and therefore the <android-toolchain-arm>/<android-toolchain-x86> value)
+specifies where the resulting toolchain should be installed (your choice).
+
+[NOTICE] XBMC uses the android API Version 14 and gcc version 4.8!
+
+Building for arm architecture:
# cd <android-ndk>
# ls platforms
# cd build/tools
# ./make-standalone-toolchain.sh --ndk-dir=../../ \
- --install-dir=<android-toolchain>/android-14 --platform=android-14
-
-ATTENTION FOR X86 BUILDS - THIS DOES NOT APPLY TO 99% OF BUILDS:
-If you want to build for the x86 platform there is a flaw in the mentioned
-NDK. See http://code.google.com/p/android/issues/detail?id=19851 which results
-in linker errors mentioning "sigsetjmp and siglongjmp".
-In that case you have to download the libc.tar.bz2 from that google issue
-entry:
+ --install-dir=<android-toolchain-arm>/android-14 --platform=android-14 \
+ --toolchain=arm-linux-androideabi-4.8
+
+Building for x86 architecture:
-http://android.googlecode.com/issues/attachment?aid=198510003000&name=libc.tar.bz2&token=6uNpHc1v8ixmVOTq3y6-ohUfb0o%3A1341156659947
+ # cd <android-ndk>
+ # ls platforms
+ # cd build/tools
+ # ./make-standalone-toolchain.sh --ndk-dir=../../ \
+ --install-dir=<android-toolchain-x86>/android-14 --platform=android-14 \
+ --toolchain=x86-4.8 --arch=x86 --system=linux-x86_64
-And extract it to <android-toolchain>/android-<x>/sysroot/usr/lib/ and overwrite
-the libc.so there. (where <android-toolchain>/android-<x>/ is the path you have given on the
---install-dir option above)
+Make sure to pick a toolchain for your desired architecture.
--------------------------------------------------------------------
3.4. Create a (new) debug key to sign debug APKs
# ./configure --help
Run configure with the correct settings for you local configuration.
+ See tools/depends/README for examples.
Anyone working on the dependencies themselves will want to set the
environment variables specified in ~/.bashrc or similar, to avoid
give it a 'make -j20' or so.
Verify that all deps built correctly (it will tell you so) before
- continuing. You will get crazy build errors otherwise.
+ continuing. You will get crazy build errors otherwise. If in doubt
+ run another 'make' (single threaded) until the message
+ "Dependencies built successfully." appears.
--------------------------------------------------------------------
5.2. Building XBMC
GDB can be used to debug, though the support is rather primitive. Rather than
using gdb directly, you will need to use ndk-gdb which wraps it. Do NOT trust
-the -p/--project switches, as of ndk7b they do not work. Instead you will need
+the -p/--project switches, as they do not work. Instead you will need
to cd to tools/android/packaging/xbmc and execute it from there.
# ndk-gdb --start --delay=0
ndk-build to do the actual packaging, but for now its behavior is emulated.
ABI:
-Presently we are targeting armv7a+neon for arm, and i686 for x86. Note that x86
-builds successfully but has not been tested.
+Presently we are targeting armv7a+neon for arm, and i686 for x86.
--------------------------------------------------------------------
9. Useful Commands
-Enable CheckJNI (BEFORE starting the application)
# adb shell setprop debug.checkjni 1
+
projects / vuplus_xbmc / blobdiff