Nyaaori/rockbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
Rockbox
16568 commits 17 branches 142 tags 291 MiB
C 89.9%
C++ 4.3%
Assembly 2%
TeX 1.5%
Lua 0.7%
Other 1.3%
Find a file
Brandon Low 7b1de20544 Fix FS 8753, JdGordon started it, I finished it. 
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@16692 a1c6a512-1295-4272-9138-f99709370657
2008-03-18 07:01:23 +00:00
apps Fix FS 8753, JdGordon started it, I finished it. 2008-03-18 07:01:23 +00:00
backdrops
bootloader Cosmetic fixes for the iAudio bootloader: Don't display 'Hold switch on' if the reason for getting there was a spurious ON event. Don't disable the multi-colour LED in the M3 bootloader. 2008-03-18 00:17:21 +00:00
docs Keep those two empty lines. 2008-03-11 19:47:49 +00:00
firmware Commit the ADC changes (fix red M3 builds). 2008-03-18 06:55:59 +00:00
flash Fix Red 2008-03-13 04:03:55 +00:00
fonts Commit FS#8626 by Frank Otto. Fixes character glitch in helvR10. 2008-03-04 18:16:02 +00:00
gdb move the ifp7xx usb serial driver files to more specific names, to make the "usb_serial" name available for more general usb class driver use 2008-03-02 18:16:24 +00:00
icons Small fix for the default colour icon set - the equalizer showed one pink line, use pure magic magenta there to make this line transparent. 2008-03-13 21:47:11 +00:00
manual m:robe 100 - fix screenshots 2008-03-14 20:06:23 +00:00
rbutil rbutil: fix a debug output, so it compiles again on windows. 2008-03-15 14:50:42 +00:00
tools In order to disable building plugins for a target, 'plugin' must be set to empty in configure. 2008-03-14 09:22:30 +00:00
uisimulator More M3 work: Rockbox logo, keymap, sim definitions, sim bitmap. Simulator builds and works now, but for some reason it tries to build plugins even though they're deactivated through configure... The keymap probably needs further refinement. 2008-03-14 00:17:59 +00:00
utils Oops, I should try compiling things before committing... 2008-02-23 20:50:26 +00:00
wps ignore carriage returns in WPS files to avoid problems with cygwin/tortoisesvn 2008-03-10 17:47:58 +00:00

docs/README 

               __________               __   ___.
     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!