Rockbox
Find a file
Jonathan Gordon a395a34671 skin tags: fix the id3 track/disc numbers in conditionals
Fix the %in tag so %xd(a, %in) works as expected

Change-Id: I33dd3ae092a66b1363c9cf3afa08075e4534af7c
2013-02-21 21:14:58 +11:00
android android: Hopefully fix a rare hang of the UI. 2013-01-18 09:49:46 +01:00
apps skin tags: fix the id3 track/disc numbers in conditionals 2013-02-21 21:14:58 +11:00
backdrops cabbiev2 for rk27xx generic design target 2012-07-09 20:30:43 +02:00
bootloader Another optimization for the OF in the mi4 format. 2012-11-24 22:33:09 +01:00
debian Prepare new, unofficial maemo release 2012-12-26 19:59:29 +01:00
docs Created graphics for the numbers in Sudoku and fixed layout for Sansa Clip Zip. 2013-01-27 13:57:27 +01:00
firmware hm60x: Fix white screen bug. 2013-02-16 18:21:36 +04:00
flash Add KEEP() around vectors in linker scripts. 2011-12-18 06:43:08 +00:00
fonts Remove superfluous executable bits on a bunch of files. 2011-06-08 14:22:03 +00:00
gdb Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
icons wpsbuild: Rewrite to fix various issues and support .fms 2012-06-10 21:20:36 +02:00
lib Fix FSB#12826 - Mini-sound burp between track skips [with WMA]. 2013-02-18 02:43:07 +01:00
manual Manual: add missing plugin keymaps for Sansa Clip (all models) 2013-02-18 09:20:27 +01:00
packaging Fixes a typo in rockbox.desktop 2013-01-02 03:41:10 +01:00
rbutil mkimxtool: increase performance by compiling with O3 2013-02-17 12:47:01 +01:00
tools Clip Zip: promote to stable 2013-02-18 08:25:14 +01:00
uisimulator zenxfi2: forgot a simulator file 2013-01-15 22:49:43 +00:00
utils imxtools/sbtools: silence warning 2013-02-18 13:43:55 +01:00
wps fix typo 2012-12-04 18:49:29 +11:00
.gitattributes Add a gitattributes file for the migration. 2011-12-01 14:14:59 +00:00
.gitignore Add *.o and *.a to .gitignore 2012-05-16 11:26:22 +02: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!