From Helix Community
Helix Player Platforms
The Helix Client is a cross-platform media engine. It already builds and works on a number of platforms. However, there are a few Unix platforms on which it hasn't been maintained and may require some porting. This section of the Helix Player website is dedicated to providing the status of the player on its supported platforms and information on how to port to unsupported platforms. Let us know if you'd like to help!
See http://alioth.debian.org/projects/helix/ for debian-specific player issues
|linux-2.2-libc6-gcc32-i586||working||this is our primary Linux platform (gcc 3.2)|
|linux-2.2-libc6-i386||working||this is our secondary Linux platform (gcc 2.95)|
|sunos-5.8-sparc||buggy||builds, some runtime errors preventing RA, rtsp, video playback|
|hpux-11-parisc-client||broken||client core building (?) codecs broken|
|linux-2.2-libc6-powerpc||unknown||this is the Linux PPC platform-- the client core reportedly builds|
|linux-2.0-libc6-mips-ps2||broken||client/core broken (missing symbol during link)|
|linux-2.2-libc6-sparc||unknown||client should mostly build, with some compiler errors|
|linux-2.4-libc6-ia64||unknown||client should mostly build, with some compiler errors|
|freebsd-4.0-i586||broken||client core, RA/RV datatypes broken|
|freebsd-5.0-i586||broken||client core, RA/RV datatypes, audio/device and audio/resampler broken|
|aix-4.3-powerpc||unknown||client should mostly build, with some compiler errors|
| symbian-61|| working|| Primary platform for the Symbian Helix Player|
RealPlayer for Linux is only available on the linux-2.2-libc6-gcc32-i586 platform.
If you are interested in adding support for a platform, here is a step-by-step guide on how to do it. The very first thing before you can even start is to make sure Ribosome has support for the platform. Look in ribosome/build/umakecf for a .cf file that matches your system. If you don't see one, you may have to come up with one yourself. Talk to the Ribosome and Helix Client dev teams for more details on how to do this, or use an existing .cf file as an example. Once you have identified (or created) the appropriate .cf, setup Ribosome and set your SYSTEM_ID environment variable appropriately.
- The first thing to do is build a minimal client core with only local mp3 support. Set your PROFILE_ID to helix-client-local-mp3 and build the splay_mp3 target. Fix any compile/link errors and make sure that splay can play back local mp3s. RealNetworks used to provide an unsupported RealPlayer on numerous Unix platforms, so hopefully the client core should build without too much effort on most of these same platforms.
- Next, start turning on features via the PROFILE_ID. If you want to dive right in, set it to helix-client-all-defines. Or if you prefer a more gradual approach try helix-client-local-net-ra-mp3 (or one of the other profiles that contains networking and/or RA & RV support.)
- Before a network, RA or RV profile will compile you will need either access to the proprietary RealNetworks RDT, RA and RV source code (available via the RCSL license) or else you will need pre-compiled libs (via the RPSL license.) For existing ports we should have libs available. For new ports you will need to work with the project maintainers to arrange to have these provided.
- Finally, start building the player_tar target. This will require GTK+ 2.0 (2.2 preferred) support, and also currently requires the pkg-config tool. Hopefully this portion of the player port should be very painless.
If you'd like to help out with any of these platforms, please let one of the project maintainers (Vikram Dendi or Nicholas Hart) know. Please let us know which platform(s) you're interested in and how you can help. Currently we need some folks to help with the following:
- build and test Solaris/Sparc
- build and test Linux/PPC
- build and test Linux/Sparc
- build and test Linux/IA64
- build and test Linux/PS2
- build and test HP-UX
- build and test AIX
- build and test FreeBSD