Rockbox
Find a file
Andrew Ryabinin 978e506f1b HM-60x: Implement power off.
Change-Id: Ia3ae38bba09996e1d1e6043f340dbbc3a2ad68b5
2012-01-17 19:49:28 +04:00
android android: Add preliminary eclipse support for building the native code, disabled by default. 2012-01-03 23:44:51 +00:00
apps fuzeplus: update plugins keymaps (FS#12405) 2012-01-15 02:29:30 +01:00
backdrops Add missing cabbiev2 800x480 backdrop 2011-02-19 01:45:08 +00:00
bootloader Rework powermgmt to enable code re-use on appliation and sims. 2012-01-03 23:44:38 +00:00
debian Prepare new, unofficial maemo build 2011-12-10 18:34:07 +00:00
docs FS#12511 - Polish translation by Artur Juraszek 2012-01-09 21:19:14 +00:00
firmware HM-60x: Implement power off. 2012-01-17 19:49:28 +04:00
flash Add KEEP() around vectors in linker scripts. 2011-12-18 06:43:08 +00:00
fonts Remove superfluous executable bits on a bunch of files. 2011-06-08 14:22:03 +00:00
gdb Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
icons The new 12x12 iconset somehow got corrupted. Re-generate. 2011-11-26 16:16:25 +00:00
lib Use buflib for all skin engine allocations. 2011-11-15 14:11:08 +00:00
manual Fix install directions for the Clip Zip. 2012-01-14 16:48:58 -05:00
packaging Prepare new, unofficial pandora build 2011-12-10 19:25:21 +00:00
rbutil Add alternate firmware filenames for e200v2. 2012-01-15 23:32:15 +01:00
tools rbspeex: make local functions static. 2012-01-12 20:49:19 +01:00
uisimulator r31444 missed a file. make fuzeplus sim build again 2012-01-09 10:16:05 +00:00
utils Rockbox Utility: add missing folder to deployment script. 2012-01-05 10:51:57 +00:00
wps lcd_color/cabbiev2: New iconset in multiple sizes 2011-11-26 16:01:11 +00:00
.gitattributes Add a gitattributes file for the migration. 2011-12-01 14:14:59 +00:00
.gitignore Add a generic *.exe to .gitignore, and remove the specific ones. 2012-01-16 22:29:47 +01: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!