CONSTRUCTION AREA
Go to file
Amaury Pouly 27433076e9 tcctool: fix Makefile
The version.sh tool tries to locate the repository root if no argument is
given but it doesn't really work. Instead explicitely give it the path to
the root.

Change-Id: Ie3a35cb3d41bbd8819823358763f714ad045527e
2013-09-18 13:14:20 +02:00
android android: Rewrite PCM playback without OnPlaybackPositionUpdateListener. 2013-04-01 11:26:12 +02:00
apps fuze+/keymaps: define Cancel over Menu in EQ context 2013-09-18 12:40:47 +02:00
backdrops cabbiev2 for rk27xx generic design target 2012-07-09 20:30:43 +02:00
bootloader fix copyright 2013-09-05 23:16:13 +02:00
debian Prepare new maemo release 2013-03-10 12:12:38 +01:00
docs Add Roman Poltoradnev to the CREDITS file. 2013-07-09 18:49:37 +02:00
firmware imx233: implement mmc card info 2013-09-07 00:53:21 +02:00
flash Make fixepoint.c as a shared library (libfixedpoint.a). 2013-04-26 00:11:04 +02:00
fonts Remove superfluous executable bits on a bunch of files. 2011-06-08 14:22:03 +00:00
gdb Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
icons wpsbuild: Rewrite to fix various issues and support .fms 2012-06-10 21:20:36 +02:00
lib Opus: delete two files that were moved into a subdir 2013-09-01 18:36:12 +02:00
manual [Fuze+][Keymaps] Application and viewer keymaps update 2013-07-18 20:24:06 +02:00
packaging Prepare unofficial pandora release 2013-03-10 14:09:30 +01:00
rbutil mkimxboot: fix crash 2013-08-22 17:49:50 +02:00
tools bmp2rb: Data was written with an incorrect offset. 2013-09-08 12:52:48 +02:00
uisimulator fix red 2013-09-05 20:35:51 +02:00
utils tcctool: fix Makefile 2013-09-18 13:14:20 +02:00
wps cabbiev2: fix a snafu in cabbiev2.240x320x16.wps 2013-07-15 23:38:40 +02:00
.gitattributes Add a gitattributes file for the migration. 2011-12-01 14:14:59 +00:00
.gitignore Add *.o and *.a to .gitignore 2012-05-16 11:26:22 +02:00

docs/README

               __________               __   ___.
     Open      \______   \ ____   ____ |  | _\_ |__   _______  ___
     Source     |       _//  _ \_/ ___\|  |/ /| __ \ /  _ \  \/  /
     Jukebox    |    |   (  <_> )  \___|    < | \_\ (  <_> > <  <
     Firmware   |____|_  /\____/ \___  >__|_ \|___  /\____/__/\_ \
                       \/            \/     \/    \/            \/

Build Your Own Rockbox

1. Clone 'rockbox' from git (or extract a downloaded archive).

   $ git clone git://git.rockbox.org/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!