Rockbox
Find a file
2010-07-02 05:17:57 +00:00
apps Fix red. 2010-07-02 04:40:24 +00:00
backdrops Remove svn:executable 2009-12-11 14:50:57 +00:00
bootloader sansa AMS bootloader: build if USE_ROCKBOX_USB isn't defined 2010-06-23 05:16:24 +00:00
docs add Martin Sägmüller to CREDITS 2010-06-24 09:27:49 +00:00
firmware i.MX31: Make DMA ISR call loop a bit more efficient. 2010-06-30 07:08:10 +00:00
flash Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
fonts Add the 'number sign' glyph to a couple more fonts 2010-06-30 09:30:25 +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 Theme Editor: Altered tag table entry for %pb to make image optional, implemented progress bar rendering in theme editor 2010-07-02 00:20:36 +00:00
manual Theme tags description: include the part about 'hold' for soft hold targets as well (available there since hm... r13716), put more universally to get rid of special casing. 2010-07-01 21:02:12 +00:00
rbutil FS#11439: Fix version comparison regression. 2010-06-30 21:59:47 +00:00
tools Fix a problem where multigcc.pl sometimes produces lines like "sh-elf-gcc: no input files", especially on systems with many cores and for builds with (relatively) few files. This happened because the slice size was rounded up, which meant that in some cases there werere leftover slices. 2010-06-30 16:39:28 +00:00
uisimulator sim_icons.c is actually only for charcell display simulation. 2010-06-22 23:22:31 +00:00
utils Theme Editor: Switched the last two parameters of the Vp tag back to their original orientation, made the playlist display the first half with ID3 info, the second half without, as if the list were mid-way through loading 2010-07-02 05:17:57 +00:00
wps update classic_statusbar to the new syntax 2010-06-13 13:16:41 +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!