Linux development

NOTE! This article documents a current event. Information may change rapidly as the event progresses.

Currently, a few developers on Team-XBMC have begun porting XBMC to Linux (and OpenGL using the SDL toolkit). The plan is for this to become a full port of XBMC with all the same features and functions that are available on the Xbox version of XBMC. This is a huge task which is why we are now making this public request, seeking C/C++ programmers who may or may not yet have already contributed to The XBMC Project in the past to volunteer in assisting us with this Linux porting development project. Those unfamiliar to XBMC can get a good overview of what XBMC is capable of by reading the XBMC article on wikipedia.org

Note to XBMC end-users! Please understand that this XBMC Linux port project is not yet mature enough for you to play with. No media can even be played back yet and we can not give you an ETA when it will be useful for end-users. Respect that we can not yet accept any bug reports or feature/function requests for this Linux port. If you as an end-users have any questions or need to get something of your chest about this then please direct that towards the existing XBMC Linux port end-user discussion topic-thread in our community-forum

What is XBMC and why port it to Linux?

For those who does not know; XBMC (short for XBox Media Center, not to confused with Microsoft's Windows Media Center Extender for the Xbox) is an award-winning free and open source media player, originally designed to run on the Xbox game-console. The GPL/LGPL licensed source code basically consist of a GUI framework that has been written from scratch by Team-XBMC, this GUI acts as a front-end control interface for several audio/video players designed for specific purposes (and those are loaded when needed as DLLs), the GUI is also the interface to all of XBMC multimedia handling functions such as databases and sorting, etc.. The XBMC Project, (who's members maintain XBMC source code), is a non-profit open source hobby project that is developed by volunteers in their spare-time without any monetary gain. The team of developers working on XBMC have always encouraged anyone to submit your own source code patches for new features or functions, improve on existing ones, or fix bugs.

The difference this time is that we are not asking for new features/functions, what we are asking is for the existing code to be ported so it will compile and run under a Linux operating-system (with the same features/functions that are already available on the Xbox version of XBMC). The main reasons for porting XBMC to Linux are non-technical, (so it is not that the Xbox hardware is too slow or to old for the XBMC GUI or its existing features/functions), the real reasons are that we want XBMC to get a larger end-user and developer-base, because the more people who use XBMC and help maintain the code (and skins) the longer the project will grow and stay alive. The main reason from an end-user point of view is that the Xbox can not playback native high-definition video (at 720p and 1080i/1080p), especially not if the video is encoded with a H.264 or VC-1 codec. Nevertheless, note that we will still keep the old Xbox as the reference platform for standard-definition resolution video for a few more years, meaning that the same GUI (and skins) that runs smooth under Linux on a relativly new computer must also run just as smooth on the old Xbox hardware (or a old computer that matches the Xbox hardware).

Skill requirements

Proficient in C/C++ programming language, and though not required knowledge of DirectX and/or OpenGL is a plus, as well as prior cross-platform development experience. You do not need to have access to an Xbox in order to take part - XBMC development is well underway on Linux (Ubuntu 7.04), and also on and for Win32 (Microsoft Windows) operating-systems

Where do I start?

The recommended Linux development platform is currently Ubuntu 7.04 (Feisty Fawn). There is a Kdevelop project file available in SVN. After you done a SVN checkout, follow the install guide in the SVN to setup the required packages and so on.

Technical summery of XBMC

The basics

The XBMC code structure uses a fairly modular design (with libraries and DLLs), and we think that there are enough modules/libraries to keep a wide skill-level range of developers busy for a while in the porting of them all. So please, take a look at the source code, then with the help of our To-Do list (futher down in this article) assess where the porting stage is today and think about where and how you can try to help out. Note that we are not planning on completly abandoning the Xbox hardware any time soon - XBMC will be a cross-platform software application, using the same code on multiple hardware platforms, (the old Xbox do have a good amount of years left to live).

Detailed technical information

For more details please visit the Development Notes section on this manual.

The XBMC source code

The XBMC source code is in our SVN repository on sourceforge.net. Full instructions for installing under Linux or Win32 (Microsoft Windows) operating-systems will be available here:

• HOW-TO compile a XBMC for Linux from source code (to come soon!)
• HOW-TO compile a XBMC for Win32 from source code (to come soon!)

Linux porting

The Linux port plan

To come.

What has already been done

• Kdevelop] project file available in SVN
  • Linux development and debug enviroment
• Initial implementation of SDL
  • OpenGL for SDL
  • ?
  • ?
• X11
• More stuff to come.

To-Do

This is a To-Do list of thing that still need to be done, you are more than welcome to help out with any of these tasks:

• [MAJOR - HIGH PRORITY] Audio output modules (ALSA and OSS via SDL).
• [MAJOR - HIGH PRORITY] PAPlayer porting to Linux (so that same DLL runs on both Linux and Xbox?).
• [MAJOR - HIGH PRORITY] MPlayer porting to Linux (so that same DLL runs on both Linux and Xbox?).
• [MAJOR - HIGH PRORITY] DVDplayer porting to Linux (so that same DLL runs on both Linux and Xbox?).
• [MAJOR - HIGH PRORITY] Pixel Shader video renderer(s) (Xv and hardware overlay are outdated technology and bad?)
• [MAJOR - HIGH PRIORITY] Development of a platform-independent wrapper interface to DirectX / OpenGL / SDL graphics interfaces, particularly with respect to how this interface should be exported to visualisations (.vis) and screensavers (.xscr), etc.
• [MAJOR - LOW PRORITY] XvMC and/or Pixel Shader (Shader Model 3.0) or Cg video hardware acceleration.
  • [NVIDIA PureVideo technology] support via XvMC will be great using NVIDIA's closed-source device driver as NVIDIA GPUs have a dedicated programable video acceleration core, however those closed-source device driver only support MPEG-2 video acceleration even though NVIDIA GeForce 7 GPU hardware and later support hardware acceleration of H.264 and VC-1 (WMV9) as well. So unless you have the skill/knowledge to add full XvMC support to the open source NVIDIA deveice drivers then we either have to wait for NVIDIA to support XvMC for MPEG-4 under Linux, or we can add hardware acceleration support by writting shaders or Cg code for the decoding processes we can to offload some of the decoding onto the GPU, (which even though not as effective as using the NVIDIA PureVideo will be better than nothing).
• [MINOR - HIGH PRORITY] Port all PAPlayer codecs DLLs so they will also run under Linux.
• [MINOR - HIGH PRORITY] Fix hacks which might not work on some platforms
• [MINOR - LOW PRORITY] Lirc or alternative implementation for IR/IrDA (infrared) remote support under Linux
  • Also add Wlirc for IR/IrDA (infrared) remote support under Win32 for consistency.
  • Though probably not possible, it would be great if could be added via SDL for platform-independence.
• [CLEANUP - ALWAYS AN ONGOING PROCESS] Document all of the the current/existing code (doxygen, DocBook, or rst, preferably the first)
• [CLEANUP - ALWAYS AN ONGOING PROCESS] Valgrid debugging under Linux (and back-port any fixes to the Xbox and Win32 code)

XBMC programming and code formatting convention guidelines

More to come based on this ongoing discussion => Proposed code formatting conventions for XBMC

• Code documentation (DocBook, rst, or doxygen for the code documentation steps)
• Modular design (independent modules made upp by localized/isolated code libraries without dependcies)
• XBMC should still compile and run if a module is disabled/removed
• Cross-platform / cross-compiling; aim to compile and run on at least, Xbox, Win32 (Windows XP) and Linux
• Aim for the GUI/interface to run smoothly on a low spec computer (less than 1Ghz)
• Avoid harddisk trashing (excess read/write/erase cycles), utilize RAM memory, no harddrive paging. Aim to run on Solid-State (CompactFlash)
• Fast load and boot times for end-user perception (other thing can still run/start in the background without the user knowledge)
  • 15-seconds or less from when the end user press the power-button on the computer til he/she can browse the GUI

Mentors

Mentors are developers on Team-XBMC and members of The XBMC Project that have volunteered to assist and mentor non-official XBMC developers helping them by checking, commenting and commiting your code patches to our SVN source code tree. The mentors have chosen an area they prefer to specialize in, usually the area in which they have most knowledge and expertise. Initial patches are welcome, and can and will be merged by the team. If you wish to join the team in an official capacity, please let us know.

• Yuvalt: Everything Linux
• Elupus: DllLoader, Mplayer and DVDPlayer
• Spiff: Anything other than DllLoader/Mplayer/DVDPlayer internals.
• JMarshall: Anything GUI related, Music Library, Video Library, PAPlayer, etc.

Contact methods

• IRC: #xbmc on freenode
• Development XBMC Development Forum
  • Developers forum for XBMC development. Programmers/Coders only!
  • Not for posting Feature Requests or end-user support requests!