1
0
Fork 0
forked from len0rd/rockbox
Fork of rockbox tailored for ipod classic
Find a file
Daniel Stenberg e07b0bb1e0 Made the script more generic to allow other package creation tools to get
passed to it using the command line. Note that this makes the script use
'xargs'.


git-svn-id: svn://svn.rockbox.org/rockbox/trunk@8227 a1c6a512-1295-4272-9138-f99709370657
2005-12-13 10:20:23 +00:00
apps Patch #1379076 by Stephan Wezel - reduce the ticking problem a bit 2005-12-13 00:38:53 +00:00
bootloader H300 bootloader USB mode 2005-12-06 12:12:29 +00:00
CVSROOT Added the wps module to the rockbox module 2005-11-21 17:05:16 +00:00
docs Patch #1377879 by Anders Kagerin - faster lcd_update_rect() for h300 2005-12-11 00:30:15 +00:00
firmware Add interrupt handler for iPod. Add timer tick support. Remove temporary thread sleep solution. Remove temporary iPod current_tick solution. 2005-12-12 13:53:22 +00:00
flash Support for a colon-separated path in APPEXTRA 2005-10-27 14:39:00 +00:00
fonts These fonts were replaced by fonts of the wrong size, reported by Martin Scarratt 2005-12-10 11:31:02 +00:00
gdb Port A inits for cold-start capability 2003-06-29 21:57:20 +00:00
songdbj javazoom converter, not the tritonus one.. 2005-07-11 15:43:44 +00:00
tools Made the script more generic to allow other package creation tools to get 2005-12-13 10:20:23 +00:00
uisimulator Fix red sim builds - add rtc_read_datetime and rtc_write_datetime functions for the simulator 2005-12-11 02:00:28 +00:00
wps adjust *wps-files to new loader. 2005-12-07 20:50:08 +00:00
www recent changes 2005-12-06 19:18:00 +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!