Rockbox
Find a file
Maurus Cuelenaere e39640352e Android port: allow moving application to SD card on Froyo targets
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@27834 a1c6a512-1295-4272-9138-f99709370657
2010-08-16 20:47:46 +00:00
android Android port: allow moving application to SD card on Froyo targets 2010-08-16 20:47:46 +00:00
apps Android port: add support for hardware keys 2010-08-16 20:12:06 +00:00
backdrops Cabbiev2 480x800 port, very similar to the 320x480 one. 2010-08-12 19:06:40 +00:00
bootloader Introduce NORETURN_ATTR wrapper for __attribute__((noreturn)), using this and a bit further cleanup in main gets rid of a warning when compiling for android. 2010-08-12 13:38:25 +00:00
docs Update portugues-brasileiro translation, FS #11521 by Rodrigo Barretto 2010-08-08 07:40:29 +00:00
firmware Android port: simplify sending touch events from Java->C 2010-08-16 20:12:10 +00:00
flash Move memset6() declaration to string-extra.h, kills a warning compiling for android since it ships a memory.h. 2010-08-12 13:55:01 +00:00
fonts Polish charset for 09-Nedore font, FS #11460 by Tomasz Kowalczyk 2010-07-05 11:54:03 +00:00
gdb Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
icons Revert hotkey bitmaps 2010-05-07 14:46:42 +00:00
lib/skin_parser A bunch of new features for the bar type tags (%pb, %pv, %bl, etc): 2010-08-15 14:13:36 +00:00
manual Manual: replace target options with the more appropriate button pad options in the 'Screen scroll out of view' key mapping description. 2010-08-16 10:03:00 +00:00
rbutil Update Brazilian Portuguese translation for Rockbox Utility 2010-08-12 08:32:54 +00:00
tools try again 2010-08-10 14:32:08 +00:00
uisimulator Rockbox as an application: Commit current Android port progress. 2010-08-02 20:34:47 +00:00
utils Theme Editor: Changed playlist rendering to match new syntax 2010-08-15 02:04:06 +00:00
wps The 128x96x2 cabbiev2.wps (Iaudio remote and M3) used more than one viewport but drew the progressbar in the default one where it wouldn't be updated with the new parser anymore. Put it into a viewport too and rearrange the rest of the code to the same order as displayed. 2010-08-14 07:27:59 +00:00

               __________               __   ___.
     Open      \______   \ ____   ____ |  | _\_ |__   _______  ___
     Source     |       _//  _ \_/ ___\|  |/ /| __ \ /  _ \  \/  /
     Jukebox    |    |   (  <_> )  \___|    < | \_\ (  <_> > <  <
     Firmware   |____|_  /\____/ \___  >__|_ \|___  /\____/__/\_ \
                       \/            \/     \/    \/            \/

Build Your Own Rockbox

1. Check out 'rockbox' from SVN (or extract a downloaded archive).

   $ svn co svn://svn.rockbox.org/rockbox/trunk rockbox

     or

   $ tar xjf rockbox.tar.bz2

2. Create a build directory, preferably in the same directory as the firmware/
   and apps/ directories. This is where all generated files will be written.

   $ cd rockbox
   $ mkdir build
   $ cd build

3. Make sure you have sh/arm/m68k-elf-gcc and siblings in the PATH. Make sure
   that you have 'perl' in your PATH too. Your gcc cross compiler needs to be
   a particular version depending on what player you are compiling for. These
   can be acquired with the rockboxdev.sh script in the /tools/ folder of the
   source, or will have been included if you've installed one of the
   toolchains or development environments provided at http://www.rockbox.org/

   $ which sh-elf-gcc
   $ which perl

4. In your build directory, run the 'tools/configure' script and enter what
   target you want to build for and if you want a debug version or not (and a
   few more questions). It'll prompt you. The debug version is for making a
   gdb version out of it. It is only useful if you run gdb towards your target
   Archos.

   $ ../tools/configure

5. *ploink*. Now you have got a Makefile generated for you.

6. Run 'make' and soon the necessary pieces from the firmware and the apps
   directories have been compiled, linked and scrambled for you.

   $ make
   $ make zip

7. unzip the rockbox.zip on your music player, reboot it and
   *smile*.

If you want to build for more than one target, just create several build
directories and create a setup for each target:

   $ mkdir build-fmrecorder
   $ cd build-fmrecorder
   $ ../tools/configure

   $ mkdir build-player
   $ cd build-player
   $ ../tools/configure

Questions anyone? Ask on the mailing list. We'll be happy to help you!