Rockbox
Find a file
Martin Arver 48a336851e Added screenshots for some of the plugins for the 112x64x1 and 220x176x16 players
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@8937 a1c6a512-1295-4272-9138-f99709370657
2006-03-06 21:20:48 +00:00
apps Wrong ifdefing of the loader plugin caused an empty chessbox.rock to be included in the CVS builds (iPod, possibly iriver too). MEM is called MEMORYSIZE in SOURCES. D'oh 2006-03-06 19:23:58 +00:00
bootloader Patch #3060 from Andrew Scott - iPod mini button driver 2006-02-27 12:35:05 +00:00
CVSROOT Added manual 2006-02-12 12:58:51 +00:00
docs Archos V1 recorder charging path #2927 by Alun Thomas 2006-03-04 09:48:53 +00:00
firmware Make the ipod ADC driver more generic, preparing to share code between it and the iRiver 2006-03-06 15:25:26 +00:00
flash Support for a colon-separated path in APPEXTRA 2005-10-27 14:39:00 +00:00
fonts add the Adobe Helvetica font. 2006-02-13 10:56:21 +00:00
gdb Mapped iFP DRAM to 0xc00000 and enabled caching in this area. 2006-02-12 23:16:05 +00:00
manual Added screenshots for some of the plugins for the 112x64x1 and 220x176x16 players 2006-03-06 21:20:48 +00:00
songdbj javazoom converter, not the tritonus one.. 2005-07-11 15:43:44 +00:00
tools build a tar.bz2 file as well at it compresses a lot better than tar.gz 2006-03-05 11:46:43 +00:00
uisimulator Simulators: Fix pointer size vs. int size problems (64bit hosts) in plugin loader and codec loader. 2006-03-02 01:08:38 +00:00
wps add these files to the source archive as well 2006-02-02 21:43:11 +00:00
www changed ages ago 2006-01-30 09:56:08 +00:00

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

Build Your Own Rockbox

1. Check out 'rockbox' from CVS (or extract a downloaded archive). You
   want to check out 'rockbox-devel' instead if you want the simulator
   code too (for trying out things on host before making target tests).

   (For more information about the simulator, read UISIMULATOR.)

   $ cvs -d:pserver:anonymous@www.rockbox.org:/cvsroot/rockbox login 
   $ cvs -z3 -d:pserver:anonymous@www.rockbox.org:/cvsroot/rockbox co rockbox

     or

   $ tar xzf rockbox.tar.gz

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

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. Make sure you have sh-elf-gcc and siblings in the PATH. Make sure that you
   have 'perl' in your PATH too.

   $ which sh-elf-gcc
   $ which perl

7. Run 'make' and soon the necessary pieces from the firmware and the apps
   directories have been compiled, linked and scrambled for you.

   $ make

8. Copy the archos.mod or ajbrec.ajz file to your archos, reboot it and
   *smile*.  Recent Rockbox versions need no reboots, just PLAY a new rockbox
   version and that'll be loaded and replace the currently running version.

   $ mount /dev/sda1 /mnt/archos
   $ cp ajbrec.ajz /mnt/archos
   $ umount /mnt/archos

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!