Rockbox
Find a file
Dave Chapman da6c0a0e46 Fix channel-swapping bug in iriver recordings. Left and Right channels should now be correctly written to the WAV file.
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@7585 a1c6a512-1295-4272-9138-f99709370657
2005-10-06 21:19:18 +00:00
apps Replace SWAB16 and SWAB32 with a comprehensive set of byte-swap macros - letoh16, letoh32, htole16, htole32, betoh16, betoh32, htobe16 and htobe32 2005-10-06 19:27:43 +00:00
bootloader Added a dummy sys_poweroff() in the boot loader 2005-09-14 09:44:45 +00:00
CVSROOT bootbox is not a module 2005-06-22 20:07:45 +00:00
docs Workaround for ALAC files that previousy wouldn't play. Libalac now skips unknown chunk IDs. Time display and seeking is broken for those files (the ones that played before still work). Patch by Alyssa Milburn. 2005-09-24 02:12:42 +00:00
firmware Fix channel-swapping bug in iriver recordings. Left and Right channels should now be correctly written to the WAV file. 2005-10-06 21:19:18 +00:00
flash we have to use the new ROMbox link address here, too 2005-08-31 23:50:40 +00:00
fonts Nimbus-12: Minor adjustments, plus added a lot of missing characters 2005-09-13 09:06:55 +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 Modified the viewers.config syntax slightly. The name field should now include 2005-10-05 08:02:10 +00:00
uisimulator Properly stop the audio in the win32 simulated playback 2005-09-07 06:42:05 +00:00
www Rockbox 2.5 released. 2005-09-22 09:35:59 +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!