rockbox/docs
Mustapha Senhaji 29b1156d86 Add Sei Aoyumi to credits for FS#9915 commited in r20030.
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@20038 a1c6a512-1295-4272-9138-f99709370657
2009-02-18 04:23:38 +00:00
..
API
BATTERY-FAQ Convert the whole codebase to UTF-8, except docs/COMMITTERS and tools/creative.c, which need checking. 2008-05-05 10:32:46 +00:00
BATTERY-FAQ-LIION
CHARGING_ALGORITHM
COMMITTERS Welcome me - hello all! 2009-02-16 19:21:06 +00:00
CONTRIBUTING fix layout so it actually looks consistent. Nothing worse than bad looking style guides! 2009-02-12 20:49:53 +00:00
COPYING
COPYING-MANUAL
CREDITS Add Sei Aoyumi to credits for FS#9915 commited in r20030. 2009-02-18 04:23:38 +00:00
CREDITS-MANUAL Fix up the iPod install section of the manual to bring it 2008-12-19 16:36:47 +00:00
CUSTOM_CFG_FORMAT
CUSTOM_WPS_FORMAT Document the database WPS tags. 2008-03-08 08:19:42 +00:00
HISTORY Convert to UTF-8 and a few tweaks. 2008-02-07 00:56:07 +00:00
KNOWN_ISSUES
LICENSES
MAINTAINERS Updated Tagalog translation by Melba Sitjar (FS#9289). Added as Tagalog maintainer as well. 2008-08-16 21:38:13 +00:00
NODO
PLUGIN_API
PLUGIN_API.new remove align_buffer from firmare/general.c, replacing with ALIGN_BUFFER macro, and replace all uses of it (only resize.c in core, and pictureflow and mpegplayer plugins), remove it from plugin_api, 2009-01-13 13:48:26 +00:00
profontdoc.txt Convert the whole codebase to UTF-8, except docs/COMMITTERS and tools/creative.c, which need checking. 2008-05-05 10:32:46 +00:00
README configure update hasn't worked in ages... 2008-01-21 22:21:28 +00:00
sample.colours
sample.icons
TECH Convert the whole codebase to UTF-8, except docs/COMMITTERS and tools/creative.c, which need checking. 2008-05-05 10:32:46 +00:00
UISIMULATOR FS#9808 by Ori Avtalion: Update simulator documentation with new 'simdisk' directory 2009-01-18 19:30:28 +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!