Find a file
2009-03-17 20:53:02 +00:00
apps Sansa Fuze: Fix bubbles controls (scrollwheel didn't work). 2009-03-17 04:49:55 +00:00
backdrops kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
bootloader FS#10018 general pp bootloader: start the OF if loading rockbox fails. Resolves a bug where the c200 bootloader would loop flashing the logo if loading rockbox failed and drop support for loading old .e200 and .h10 rockbox main binaries for the e200 resp h10, affects e200, c200, h10 (both kinds) and mrobe 100. 2009-03-17 20:05:03 +00:00
docs Rework lcd_enabled and lcd_set/call_enable hook 2009-03-17 02:43:47 +00:00
firmware Make USB on sansas more reliable (FS#10026). Both fixes by Toni Hellmann 2009-03-17 20:24:55 +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 Correct the BBX clause (no visual changes) 2009-03-01 10:22:14 +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 Update the manual to reflect recent strnatcmp changes. 2009-03-17 20:11:40 +00:00
rbutil Add md5 for clip OF version 1.01.32 to mkamsboot (verified to work) 2009-03-16 18:55:39 +00:00
tools When rockboxdev.sh temporarily adds $bindir to the PATH (so the gcc build can find the matching binutils), put it at the start, just in case the user has an old (and incompatible) target-binutils around. 2009-03-17 20:53:02 +00:00
uisimulator Actually do the renaming of the stub. 2009-03-17 03:45:55 +00:00
utils Cosmetic fix: remove duplicate semicolons 2009-03-04 18:15:06 +00:00
wps FS#9763 - Sansa Clip modified WPS. This modified wps avoids wps elements getting split over the yellow/cyan 2009-01-31 12:23:35 +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!