Rockbox
Find a file
Nils Wallménius 2dda258f99 Remove STATICIRAM hack
It was only needed by the old arm toolchain that we no longer use or support.

Change-Id: Id0e6c67477f8834a637079b03cde5fbf9da68b1c
Reviewed-on: http://gerrit.rockbox.org/233
Reviewed-by: Nils Wallménius <nils@rockbox.org>
2012-05-08 22:46:12 +02:00
android Add codecs to librbcodec. 2012-04-25 22:13:20 +02:00
apps fix yellow introduced in 10829b2 2012-05-08 21:59:01 +02:00
backdrops Add missing cabbiev2 800x480 backdrop 2011-02-19 01:45:08 +00:00
bootloader remove debug-target.h 2012-05-07 00:55:59 -04:00
debian Prepare new, unofficial maemo build 2011-12-10 18:34:07 +00:00
docs Fix Rockblox plugin display issues on Clip Zip 2012-04-22 12:33:12 +02:00
firmware Remove STATICIRAM hack 2012-05-08 22:46:12 +02: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
icons The new 12x12 iconset somehow got corrupted. Re-generate. 2011-11-26 16:16:25 +00:00
lib Remove STATICIRAM hack 2012-05-08 22:46:12 +02:00
manual Update Fuze+ manual (main files) FS#12492 2012-05-01 20:19:25 +02:00
packaging Prepare new, unofficial pandora build 2011-12-10 19:25:21 +00:00
rbutil Bootloader installation: set file filter. 2012-05-01 10:49:48 +02:00
tools thumb-cc.py: fix for python 3.2 2012-05-07 00:19:03 -04:00
uisimulator Refactor and unify objcopy calls in the build system. Also now properly handles DEBUG builds on hosted targets to keep debug symbols if necessary. 2012-04-04 21:48:19 +02:00
utils gitscraper: Provide way to get timestamps for files. 2012-04-29 11:48:07 +02:00
wps skin_engine: Clean up %x() handling - beware theme issues 2012-02-28 23:51:01 +11:00
.gitattributes Add a gitattributes file for the migration. 2011-12-01 14:14:59 +00:00
.gitignore ignore ipodpatcher binary 2012-03-25 11:45:31 -04: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!