1
0
Fork 0
forked from len0rd/rockbox
Fork of rockbox tailored for ipod classic
Find a file
2010-08-03 08:42:30 +00:00
android Rockbox as an application: Commit current Android port progress. 2010-08-02 20:34:47 +00:00
apps Rockbox as an application: Commit current Android port progress. 2010-08-02 20:34:47 +00:00
backdrops Rockbox as an application: Commit current Android port progress. 2010-08-02 20:34:47 +00:00
bootloader Rockbox as an application: Commit current Android port progress. 2010-08-02 20:34:47 +00:00
docs FS#11490 - Viewportify most of the shipped cabbiev2 wps' By Hayden Pearce. Spot a mistake? mention in the tracker page 2010-07-26 12:07:48 +00:00
firmware Rockbox as an application: Commit current Android port progress. 2010-08-02 20:34:47 +00:00
flash Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
fonts Polish charset for 09-Nedore font, FS #11460 by Tomasz Kowalczyk 2010-07-05 11:54:03 +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
lib/skin_parser skinparser lib: even more const correctness, should fix checkwps, again 2010-07-31 16:33:34 +00:00
manual Manual: Fix typo 2010-08-02 21:38:37 +00:00
rbutil rbutil: c200v2 2010-07-29 23:35:42 +00:00
tools Rockbox as an application: Commit current Android port progress. 2010-08-02 20:34:47 +00:00
uisimulator Rockbox as an application: Commit current Android port progress. 2010-08-02 20:34:47 +00:00
utils Theme Editor: Removed markup comments from CodeEditor files (it was originally a Nokia example, so it was marked up with comments for their documentation), implemented the beginnings of drag and drop editing. Viewports are now movable, but don't invoke code generation yet 2010-08-03 08:42:30 +00:00
wps Rockbox as an application: Commit current Android port progress. 2010-08-02 20:34:47 +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!