Rockbox
Find a file
Alexander Levin b085ccd309 Fix typo in comment
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@25681 a1c6a512-1295-4272-9138-f99709370657
2010-04-19 19:48:10 +00:00
apps Fix typo in comment 2010-04-19 19:48:10 +00:00
backdrops Remove svn:executable 2009-12-11 14:50:57 +00:00
bootloader FS#11199: ipod bootloader: reboot to disk mode on cable insert, following a fatal error 2010-04-13 22:17:42 +00:00
docs Add Marcin Bukat for FS #11151 and FS #11153 2010-04-11 20:55:21 +00:00
firmware Sansa as3525: Add missing lcd-clip.h header file to sansa clip lcd drivers. Set svn:keywords on scrollwheel-as3525.c. 2010-04-18 16:58:33 +00:00
flash Simplify powermgmt thread loops so it calls functions turn (no more power_thread_sleep). Do other target-friendly simplifications, generic battery switch handling and split sim-specific code. Whoever can, please verify charging on the Archos Recorder (due to change in the charger duty cycle code). 2008-12-24 16:58:41 +00:00
fonts Set the default character in 08-Atadore font to an existing glyph 2010-03-19 21:50:26 +00:00
gdb Updated our source code header to explicitly mention that we are GPL v2 or 2008-06-28 18:10:04 +00:00
icons kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
manual Manual update to document pitchscreen info saved in bookmarks on swcodec targets 2010-04-19 17:52:21 +00:00
rbutil mkamsboot: accept Clip+ OF v01.02.13 2010-04-17 12:17:01 +00:00
tools Clipv2 and Clip+ builds are still unusable 2010-04-13 13:52:03 +00:00
uisimulator Use API call instead of accessing a global variable for receiving the current thread. 2010-04-16 22:01:59 +00:00
utils Add simple bootchart -> gnuplot shell script 2010-04-05 19:58:51 +00:00
wps Fix wpsbuild to properly generate "-" for theme related settings (to get the default values/no file for filename settings). 2010-02-21 19:10:57 +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!