Rockbox
Find a file
Dave Chapman e0f8c31216 Move the S5L8700 (Meizu) crt0.S file up one level - it can be used as a generic ARM crt0.S (the uncommitted patch for the Sansa V2s uses it).
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@18775 a1c6a512-1295-4272-9138-f99709370657
2008-10-11 18:15:42 +00:00
apps Updated italian translation. 2008-10-11 15:09:43 +00:00
backdrops kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
bootloader lcd now shows things on the old-style Meizu M3. 2008-10-07 21:12:03 +00:00
docs Add Rockbox layout to plugin API documentation 2008-10-09 12:24:57 +00:00
firmware Move the S5L8700 (Meizu) crt0.S file up one level - it can be used as a generic ARM crt0.S (the uncommitted patch for the Sansa V2s uses it). 2008-10-11 18:15:42 +00:00
flash Clean up bootbox main file. 2008-09-24 22:03:20 +00:00
fonts Correct the number in the CHARS line to match the actual number of chars. 2008-09-04 17:32:06 +00:00
gdb Updated our source code header to explicitly mention that we are GPL v2 or 2008-06-28 18:10:04 +00:00
icons kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
manual Add mono mode recording setting to manual 2008-10-08 22:45:20 +00:00
rbutil Add Rafael Carre to the (C) message in the output of mkamsboot. This should be the last commit for a while... 2008-10-11 13:13:44 +00:00
tools Make the MIPS toolchain build on gcc 4.3+. 2008-10-11 10:16:50 +00:00
uisimulator Commit FS#9308: differentiate between TOUCHPAD & TOUCHSCREEN 2008-08-23 09:46:38 +00:00
utils Fix menu (update to newer one) 2008-10-09 12:28:09 +00:00
wps Font cleanup step 3 - The Big Shuffle: Renamed all fonts to a consistent naming scheme that allows easy selection of alternatives based on size, as discussed on IRC. Adjusted themes in SVN and Makefile for the sysfont. ** Attention **: Clean up your /.rockbox/fonts folder before installing the new release, and then install a new font pack as well. Adjust font names in your custom .cfg files. A reference table can be found in fonts/README. 2008-09-02 22:31:11 +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!