Rockbox
Find a file
Bertrik Sikken bf679fa4ac Enable tea5767 tuner detection for Philips GoGear HDD63x0 too (HDD6320 does not have a tuner, HDD6330 does)
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@28496 a1c6a512-1295-4272-9138-f99709370657
2010-11-05 18:21:20 +00:00
android Android port: add a CLI APK install+launch script, useful for quick installation 2010-11-05 16:17:25 +00:00
apps Android port: NewStringUTF() JNI call doesn't need freeing, these will get garbage collected. 2010-11-05 18:17:23 +00:00
backdrops Add a work-in-progress 320x400 touch enabled sbs. 2010-09-06 12:27:38 +00:00
bootloader MPIO HD200: fix red (I missed bootloader and simulator when renaming buttons) 2010-11-02 10:51:04 +00:00
docs Another (hopefully final) fix for FS#11453 (AMSv2 powerdown fails sometimes when wakeup timer set) by Fabian Vogel. 2010-11-01 18:58:40 +00:00
firmware Enable tea5767 tuner detection for Philips GoGear HDD63x0 too (HDD6320 does not have a tuner, HDD6330 does) 2010-11-05 18:21:20 +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 Add 20-Artwiz-Snap. 2010-11-05 10:19:26 +00:00
gdb
icons
lib Correct spelling of 'seperate' in the skin parsing code - FS#11724 by Alexander Levin 2010-11-05 09:51:19 +00:00
manual Manual: Bring the opts in the manual in line with ifdefs in the code 2010-11-03 18:02:26 +00:00
rbutil Fix crash on proxy detection on OS X (FS#11654). 2010-10-05 19:53:48 +00:00
tools Reflect the Philips GoGear HDD63x0 series as being Unstable 2010-11-03 14:38:20 +00:00
uisimulator MPIO HD200: fix red (I missed bootloader and simulator when renaming buttons) 2010-11-02 10:51:04 +00:00
utils Replace parse_testcodec.pl with a bit more powerful script. 2010-10-18 18:55:31 +00:00
wps FS#11669 - extra > in the skin 2010-10-12 09:45:11 +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!