Rockbox
Find a file
Jack Halpin d8f420a48d Sansa AMS: Add read/write and drive info to panic message for SD transfer errors.
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@23829 a1c6a512-1295-4272-9138-f99709370657
2009-12-03 17:21:56 +00:00
apps rockblox: Correct wrong access to array of highscores. 2009-12-03 15:00:54 +00:00
backdrops
bootloader make mini2440 bootloader compile again, and remove a few warnings from sd driver. 2009-10-31 16:48:08 +00:00
docs Updated hungarian translation. 2009-12-02 14:34:57 +00:00
firmware Sansa AMS: Add read/write and drive info to panic message for SD transfer errors. 2009-12-03 17:21:56 +00:00
flash
fonts
gdb
icons
manual Fix FS#10826 - Typo in fmradio.tex 2009-12-02 12:35:28 +00:00
rbutil Add support for OS X. 2009-11-29 21:09:21 +00:00
tools sims.pl - Do not create zip if build fails. This should prevent working simulator builds being overwritten by failed builds when uploaded to the hosting server. 2009-12-03 14:55:22 +00:00
uisimulator UISimulator - prevent multiple definition of usb_inserted when USB_NONE is defined 2009-11-23 17:43:42 +00:00
utils Adjust mknkboot sources path to recently changed location. 2009-11-01 10:47:58 +00:00
wps Make the classic_statusbar.sbs more classic. Icons, position of numbers, charging animation (only tested on a colour display so far), volume as before but gets a 'clipping' icon on targets that allow more than 0dB, add channels indicator in the rec screen. The only difference on swcodec should be the disk activity indicator on flash targets (for now). On hwcodec there are small differences in the recording screen - quality display is simply using the system font (no wasting another bitmap on a slightly less taller Q), frequency uses icons now (keeping the differences between the sbs files smaller and with the small 'k' it's easier to understand, but debateable). Since the animation makes use of the viewport colour (shades) parameters, a classic_statusbar.grey.sbs was needed - reusing the colour one didn't work correctly anyways. The difference between Recorders (RTC) and Ondios (disk activity) is achieved through the 112x64x1.sbs file itself. 2009-11-28 16:37: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*.

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!