Rockbox
Find a file
2010-11-28 18:25:39 +00:00
android Android: When the backlight goes off, the RockboxFramebuffer/View isn't made invisible. Force that in order to disable screen updates while backlight is off. 2010-11-12 22:09:27 +00:00
apps Reorder viewers.config entries so that test plugins come after the standard plugins for the same extension. The first defines the default action and the icon for the respective extension (if there is no core action for it). Group entries by extension so this is more visible. 2010-11-28 18:25:39 +00:00
backdrops Add a work-in-progress 320x400 touch enabled sbs. 2010-09-06 12:27:38 +00:00
bootloader MPIO HD300 - initial commit 2010-11-26 23:28:08 +00:00
docs thanks for admitting me to the team :) 2010-11-24 10:06:51 +00:00
firmware Accept FS#11774 by Michael Hohmuth (with some own modifications to #ifdef conditions) 2010-11-28 15:22:51 +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 Make the %tr (radio RSSI) tag work as a bar tag or as a conditional. 2010-11-18 11:47:42 +00:00
manual Fix all manuals that were broken in r28617 (targets that do not have \ButtonSelect) by using the respective \ActionStdOk macro which also matches the c code IIUC. 2010-11-26 19:29:50 +00:00
rbutil rbutil: r28687 touched too much. Restore some accelerator keys. 2010-11-28 13:15:40 +00:00
tools MPIO HD300 - initial commit 2010-11-26 23:28:08 +00:00
uisimulator Make the %tr (radio RSSI) tag work as a bar tag or as a conditional. 2010-11-18 11:47:42 +00:00
utils Initial version of sbinfo, a utility to analyse .sb files (used for the fuze+ for example) 2010-11-28 10:53:01 +00:00
wps Small improvements for the on screen popup on 320x480 cabbiev2 wps. 2010-11-14 19:20:25 +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!