Rockbox
Find a file
Jens Arnold b6213bbf98 Optimise line drawing calls.
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@17082 a1c6a512-1295-4272-9138-f99709370657
2008-04-12 08:57:28 +00:00
apps Optimise line drawing calls. 2008-04-12 08:57:28 +00:00
backdrops kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
bootloader sync with key list with mi4code and add the single mi4 key it had but this 2008-04-11 21:11:55 +00:00
docs FS#8871 by Tomasz Wasilczyk, avoid negative runtime estimation (that would later be cast to an unsigned giving huge values 2008-04-12 07:14:13 +00:00
firmware LCD drivers: * Automatically optimise horizontal and vertical lines drawn via _drawline(), with debug message to show possible optimisations in the caller. * Get rid of the extra ICODE function declarations by putting the attribute into the definition. 2008-04-12 07:53:33 +00:00
flash kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
fonts kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
gdb kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
icons kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
manual FS#8861 - More Rockbox friendly MazezaM (by Malcolm Tyrrell) 2008-04-10 23:28:19 +00:00
rbutil rbutil: another misplaced connect call. 2008-04-06 20:29:26 +00:00
tools decrease the risk of an overflow due to typecase from unsigned to signed 2008-04-10 21:49:40 +00:00
uisimulator Best use C, not C++ 2008-04-07 17:27:56 +00:00
utils kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
wps A tiny bit of cleanup afterwards... save a few bytes by storing the 'Rockboxed' greyscale bitmaps as 4-bit. 2008-04-11 21:08:56 +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!