Rockbox
Find a file
2009-07-06 23:15:46 +00:00
apps Adding support for rm playback. Only cook codec is supported for now and no seeking. 2009-07-06 22:40:45 +00:00
backdrops Add CabbieV2 for Onda VX747 2009-03-24 22:05:28 +00:00
bootloader Update initialisation and display of debug info in meizu M3 bootloader 2009-07-05 19:14:46 +00:00
docs fs#10290: Sansa AMS language fixes by Bertrik Sikken and Hilton Shumway 2009-06-30 21:15:19 +00:00
firmware Sansa AMS: display the virtual led icon on disk transfers 2009-07-06 16:44:57 +00:00
flash Simplify powermgmt thread loops so it calls functions turn (no more power_thread_sleep). Do other target-friendly simplifications, generic battery switch handling and split sim-specific code. Whoever can, please verify charging on the Archos Recorder (due to change in the charger duty cycle code). 2008-12-24 16:58:41 +00:00
fonts Forgot emdash and endash for 19-Nimbus 2009-05-19 22:03:16 +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 More cleanup and rearrangement for three column button tables in the manual. Most importantly: move the recently added IRIVER_RC_H100_PAD opt - including the additional column seperator - below everything that belongs to the first column. This way every column is grouped and it also allows to combine different remote control pads if they use the same button. Use HAVEREMOTEKAYMAP if the line refers to an ActionSomething. While at it, add or change some white space to make the tables more readable (there is still a lot to be desired there...) and remove a few tabs in random_folder_advance_config.tex. Also fix sliding.tex to make it show all buttons in an M5 manual by using the appropriate _PAD opt and not simply 'x5'. Finally, remove the one overlooked reference to the H100 remote pad in split_editor.tex. 2009-07-06 23:15:46 +00:00
rbutil fix bin2c.c path 2009-07-05 18:45:12 +00:00
tools A script to create a source tarball of rbutil. Does a complete checkout and removes everything that isn't needed. 2009-06-29 20:51:25 +00:00
uisimulator Remove int_prio argument from timer_register, and move the only use for it into alpine_cdc plugin, since this plugin is only built on SH7034 2009-06-29 14:29:46 +00:00
utils utils/analysis/find_addr.pl: also add support for plugins & codecs 2009-07-01 12:25:24 +00:00
wps Onda VX747: 'touchscreenize' the play button on the cabbiev2 theme 2009-06-07 20:29:48 +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!