CONSTRUCTION AREA
Go to file
Steve Bavin abf3435ca7 Slightly less hacky sim queue_send(), fixes simulator crashes FS#7051 and FS#7245.
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@14113 a1c6a512-1295-4272-9138-f99709370657
2007-08-01 09:07:09 +00:00
apps Oops again 2007-08-01 09:05:42 +00:00
bootloader Get the last errors? 2007-07-28 08:58:05 +00:00
docs Accept FS#7437 - add the delete option to the wps context menu so the currently playing file can be deleted. tested with a 130mb file on my sansa and it didnt cause problems 2007-07-31 12:26:01 +00:00
firmware Disable 'Disk spindown' and 'Anti skip buffer' settings and some related stuff for flash storage targets as they make no sense 2007-08-01 08:50:44 +00:00
flash Now charcell displays require lcd_update() for updating the main lcd content like bitmap displays. 2007-04-06 22:55:00 +00:00
fonts removed as FS#6031 points out it being messed up 2007-07-30 08:43:41 +00:00
gdb Adapted more Makefiles to the more efficient info printing. 2006-10-30 01:40:20 +00:00
manual Use the dap macro, rather than explicitly writing Ipod. 2007-07-31 19:08:08 +00:00
rbutil don't show the proxy password in configuration dialog as cleartext. 2007-08-01 07:10:10 +00:00
tools FS#4955 - convbdf segfaults on very large fonts was simply due to a too small 2007-07-31 09:42:50 +00:00
uisimulator Slightly less hacky sim queue_send(), fixes simulator crashes FS#7051 and FS#7245. 2007-08-01 09:07:09 +00:00
wps iCatcher updates: 1) Add APE icon for Monkey's Audio files; 2) Use a backdrop on greyscale targets to free some image tags (thanks to Marianne Arnold for the suggestion). However, there are still five codecs without icons (SID, ADX, NSF, Speex and SPC), and only two free image slots left... 2007-06-06 17:53:33 +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*.

Whenever the tools/configure script gets updated, you can make your makefile
updated too by running 'tools/configure update'.

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!