Rockbox
Find a file
Thomas Martitz 48016d5e07 Reduce excessive debug output during mp3 parsing.
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@29191 a1c6a512-1295-4272-9138-f99709370657
2011-02-02 18:27:31 +00:00
android Android/Java: Disable implicit compilation of dependecies to make the life easier for make. 2011-02-02 13:57:01 +00:00
apps Reduce excessive debug output during mp3 parsing. 2011-02-02 18:27:31 +00:00
backdrops Commit part of FS#10937: CabbieV2 port for the Philips GoGear 2011-01-09 22:10:29 +00:00
bootloader i.MX31: Now that it matters because there's a debug screeen that allows changing things while running, some DVFS/DPTC stuff has to be done more carefully. Trim out some stuff and group functions better as well. 2011-01-23 20:21:35 +00:00
docs Added myself to COMMITTERS 2011-01-28 22:10:08 +00:00
firmware Fix red. Replace remaining MEM's mit MEMORYSIZE. 2011-02-02 17:55:04 +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 Fix the eogonek glyph in 14-Nimbus (the credit goes to the author of FS#11785) 2010-12-11 21:05:20 +00:00
gdb Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
icons
lib fix build 2011-01-27 11:33:33 +00:00
manual Manual: Correct the description of the Time/Date menu and make it look nicer. 2011-02-01 21:52:24 +00:00
rbutil Fix sansac200v2 not showing up in device selection. 2011-02-01 22:12:07 +00:00
tools Clean up multiple definitions of RAM size. Remove -DMEM (make) and MEM (code), use the already defined MEMORYSIZE instead. 2011-02-02 17:43:32 +00:00
uisimulator Make sim build compilable under Cygwin. Fixes FS#11832. 2010-12-25 22:17:02 +00:00
utils Fix red. Replace remaining MEM's mit MEMORYSIZE. 2011-02-02 17:55:04 +00:00
wps Add progress bar graphic for CabbieV2 for 128x160x16 LCDs. 2011-01-10 02:53:36 +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!