Rockbox
Find a file
Dominik Riebeling 41ac7da18b The credits file now also has underscores, which need to be escaped in LaTeX.
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@13431 a1c6a512-1295-4272-9138-f99709370657
2007-05-19 21:05:20 +00:00
apps More header and dead code cleanup. 2007-05-19 20:55:49 +00:00
bootloader add some code to dump the sansa hidden partition (commented out), usefull for when we need to figure out which byte to modify so the OF doesnt rebuild its DB after usb 2007-05-17 11:35:57 +00:00
docs we have code from ipod linux too 2007-05-19 20:44:23 +00:00
firmware Reset the pcm_paused flag in the PP FIQ as well to complement the fix for FS #7187. Now it also works on Mini G2. 2007-05-19 20:37:12 +00:00
flash Now charcell displays require lcd_update() for updating the main lcd content like bitmap displays. 2007-04-06 22:55:00 +00:00
fonts Additions to the nimbus font family: nimbus-13 made from nimbus-12 with additional spacing, initial commit of nimbus-10 and nimbus-11 (hopefully meeting the style of the other fonts enough) - feel free to improve. 2007-05-05 10:01:13 +00:00
gdb Adapted more Makefiles to the more efficient info printing. 2006-10-30 01:40:20 +00:00
manual The credits file now also has underscores, which need to be escaped in LaTeX. 2007-05-19 21:05:20 +00:00
rbutil sansapatcher needs _LARGEFILE64_SOURCE, so add this to the rbutil Makefile too. 2007-05-18 22:00:15 +00:00
tools Reverted my "xargs ls" thing since it broke the build in a way that I'm not 2007-05-19 18:06:34 +00:00
uisimulator Fix some errors 2007-05-04 15:39:01 +00:00
wps DancePuffDuo.wps and marquee.wps can use the nimbus-13 font now. Fixed the alignment issues that were there since the chicago-'12' font had been removed. 2007-05-05 10:05:14 +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*.

Whenever the tools/configure script gets updated, you can make your makefile
updated too by running 'tools/configure update'.

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!