1
0
Fork 0
forked from len0rd/rockbox
Fork of rockbox tailored for ipod classic
Find a file
2010-03-20 12:30:18 +00:00
apps Revert r22171 (+r22186) for pacbox, given that it doesn't work, and causes crashes on COP targets, and we in fact already had an open unresolved issue against this app (FS#8226) that would need to be resolved before being able to do this 2010-03-19 23:24:22 +00:00
backdrops Remove svn:executable 2009-12-11 14:50:57 +00:00
bootloader Clip+ : make the bootloader not verbose by default 2010-03-15 11:47:50 +00:00
docs Sansa Clipv2: use similar button driver to Clipv1 2010-03-15 23:01:45 +00:00
firmware Submit FS#9746 by Boris Gjenero. Set PP502x IDE pins low for iPod Video when IDE power is off. Done by OF the same way, might be used by other targets as well. 2010-03-20 12:30:18 +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 Try to improve the English for the text viewer plugin. Only the English has been changed, the actual content still needs some work. 2010-03-17 21:58:41 +00:00
rbutil mkamsboot: update README for Clip+/Fuzev2 2010-03-16 15:24:56 +00:00
tools Recognise (open)solaris as a valid simulator host OS. 2010-03-20 08:57:47 +00:00
uisimulator UIsimulator: iAudio M3 remote keys add. 2010-03-15 12:51:53 +00:00
utils amsinfo: do not assume library blocks always have the same size 2010-03-14 23:35:01 +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!