1
0
Fork 0
forked from len0rd/rockbox
Fork of rockbox tailored for ipod classic
Find a file
2010-06-11 22:45:18 +00:00
apps Build h10 GB with EABI toolchain. Remove some pointless ICODE attributes from mp3_enc.codec and, to make it build, move one function out of IRAM there since it really shouldn't matter. 2010-06-11 21:21:36 +00:00
backdrops Remove svn:executable 2009-12-11 14:50:57 +00:00
bootloader Update Samsung YP-S3 bootloader demo 2010-05-30 21:43:14 +00:00
docs FS#11353 - Fix all errors in islenska.lang by Hinrik Örn Sigurðsson 2010-06-04 20:39:00 +00:00
firmware Port greylib blitting optimisation to MPIO HD200. ISR speedup is ~10%; further speedup should be possible by using line transfers for accessing the greylib buffers. Thanks to Marcin Bukat for testing. 2010-06-11 19:53:17 +00:00
flash Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
fonts Fix some accented glyphs in 35-Nimbus 2010-06-08 20:56:14 +00:00
gdb Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
icons Revert hotkey bitmaps 2010-05-07 14:46:42 +00:00
manual Enable the IAUDIO_RC_PAD macro for the M5 and X5 too, so that tables using this instead of the platform files' actions can be filled too. Complete the table in the quick start section mentioning how to start and shut down Rockbox for the Iaudio remote while at it. 2010-06-11 22:45:18 +00:00
rbutil deploy-release: Make upx part optional and disable it. 2010-06-11 20:02:59 +00:00
tools Build iPod Video with EABI toolchain. 2010-06-11 22:13:59 +00:00
uisimulator Fix remaining reds. 2010-06-06 10:55:15 +00:00
utils Theme Editor: Made errors display in status bar when cursor is on error'd line 2010-06-11 21:24:38 +00:00
wps SKIN BREAK: %pb, %bl and %pv (bar types) changed so the image is the last param instead of the first. skin updater, skins and manual all updated. 2010-06-09 16:15:01 +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!