Rockbox
Find a file
Dominik Riebeling e2b69ddffb rbutil fixes for OpenBSD (FS#9340 by Brian Waichunas).
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@19417 a1c6a512-1295-4272-9138-f99709370657
2008-12-13 10:09:13 +00:00
apps Some plugins need to yield under heavy user input especially with a scrollwheel. 2008-12-13 07:36:44 +00:00
backdrops kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
bootloader Meg-FX: Enable a real tick in the bootloader. Do cleanups before switching to firmware and cache handling. Put proper main return address in lr. 2008-12-08 23:31:05 +00:00
docs Language updates: 2008-12-13 01:53:20 +00:00
firmware Keyclick fixup take two. It is only 88 samples (2msec) long so keep a small static buffer around for beeps less than or equal to keyclick duration. This way it operates no matter the buffer state and still won't interfere with alternate PCM operations like recording or plugin playback. 2008-12-13 06:01:08 +00:00
flash Added 'keywords' and 'eol-style' properties. 2008-11-25 19:54:23 +00:00
fonts revert my previous commit since 5.1.20080820 was already committed in r18342 with some useless glyphs removed 2008-10-20 10:39:07 +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 Use caps macro instead of textsc to prevent the heavy HTML issue. 2008-12-10 21:40:55 +00:00
rbutil rbutil fixes for OpenBSD (FS#9340 by Brian Waichunas). 2008-12-13 10:09:13 +00:00
tools m200v4: rename Keys, so they match better other targets with similar key-layout. Enable plugins, add keymaps for plugins. More keymap improvements needed. 2008-12-12 19:50:49 +00:00
uisimulator Bring consistency to pcm implementation and samplerate handling. Less low-level duplication. A small test_sampr fix so it works on coldfire again. 2008-12-12 11:01:07 +00:00
utils Fix array sizes 2008-12-12 20:13:50 +00:00
wps Accept FS#9579 by Bartosz Fabianowski, fixing make zip when your build dir is not inside the source tree 2008-11-26 09:36:34 +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!