Difference between revisions of "Android development"
|Line 215:||Line 215:|
Revision as of 10:32, 2 August 2012
XBMC for Android has been announced on July 13th, 2012: http://xbmc.org/theuni/2012/07/13/xbmc-for-android/
| THIS PAGE IS OUTDATED:
This page or section has not been updated in a long time, no longer applies, refers to features that have been replaced/removed, and/or may not be reliable.
This page is only kept for historical reasons, or in case someone wants to try updating it.
You should read the Development Notes before reading this page.
XBMC is a huge open source project and it takes loads of people working together to maintain it for all platforms, that is why Team-XBMC is always on the lookout for C/C++ programmers to volunteer in assisting us with the development of XBMC. Whether you have contributed to The XBMC Project in the past or not, please consider doing so now.
1 Skill requirements and where to start
Proficiency in C/C++ programming language and, though not required, knowledge of OpenGL and/or multimedia programming is a plus, as well as prior cross-platform or porting development experience. Familiarity with the Android SDK and NDK is also a bonus.
A good understanding of JNI is highly recommended, since many operations in the Android environment require specific actions from the developers, that are not necessarily common in typical native code. These include:
- Not being able to directly access the content of VM objects through direct native pointers. E.g. you cannot safely get a pointer to a String object's 16-bit char array to iterate over it in a loop.
- Requiring explicit reference management when the native code wants to keep handles to VM objects between JNI calls.
1.1 Where do I start on Android?
1.1.1 Supported Development Platforms
- Windows XP (32-bit), Vista (32/64-bit), or Windows 7 (32/64-bit)
- Mac OS X 10.5.8 or later (x86 only)
- Linux (tested on Ubuntu Linux 8.04 or later, Lucid Lynx)
After obtaining the code repository, follow the compilation/development guide in the new repository to setup the required packages and so on. Team-XBMC developers opinion is that the best thing to start with is just to take a look through the source code and try to understand how it all fits together. Test things out, find what works and what does not, then try and track down why.
1.1.2 Hardware requirements
- x86-based computer. No other special hardware is required for development. For Android devices, either a virtual or hardware device can be used for development.
- If using Mac OS-X, this library from Intel is likely to be very helpful for hardware acceleration of a virtual Android environment.
2 Development Progress
Many things need to happen prior to the Android port becoming available.
2.1 Porting Libraries
The following is a list of libraries which XBMC relies upon. Each one will need to be ported to be able to be compiled on the Android platform.
|ffmpeg||100||See here, here and many other sources including Play|
|libUPnP||100||See here and here|
2.2 Developing Audio, Video and Image Renderers
A renderer for audio, video and image processing will need to be developed. Ideally, this can be accomplished by taking advantage of AudioEngine, OpenMAX AL, OpenGL ES, and OpenSL ES.