Nyaaori/rockbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
Rockbox
28909 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
Andree Buschmann c940811ade Introduce CPU dependent IRAM configuration for libgme. Use ICODE_ATTR for an emu2413-function to speed up PP5022 by up to 6%. 
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@30379 a1c6a512-1295-4272-9138-f99709370657
2011-08-30 12:35:12 +00:00
android Android tools: Allow discovery of download URLs 2011-08-20 11:11:49 +00:00
apps Introduce CPU dependent IRAM configuration for libgme. Use ICODE_ATTR for an emu2413-function to speed up PP5022 by up to 6%. 2011-08-30 12:35:12 +00:00
backdrops Add missing cabbiev2 800x480 backdrop 2011-02-19 01:45:08 +00:00
bootloader Initial framework for the Sandisk Sansa Clip Zip 2011-08-27 16:21:19 +00:00
debian Forgot to update the short log for (unofficial) maemo build 2011-06-28 18:01:29 +00:00
docs Add Nick Peskett to CREDITS 2011-08-16 19:30:23 +00:00
firmware sansa clipzip: correct GPIO used for backlight 2011-08-29 21:08:24 +00:00
flash Move memset6() declaration to string-extra.h, kills a warning compiling for android since it ships a memory.h. 2010-08-12 13:55:01 +00:00
fonts Remove superfluous executable bits on a bunch of files. 2011-06-08 14:22:03 +00:00
gdb
icons Add script to create iconset (FS#11982). 2011-05-31 21:08:29 +00:00
lib New skin tags: %Vs() to set the text style and %Vg() to get the viewports gradient colours 2011-08-14 13:50:07 +00:00
manual Manual: add %Vg and %Vs tags. Closes FS#12230. 2011-08-19 11:43:51 +00:00
packaging Prepare new, unofficial pandora build 2011-06-28 17:33:04 +00:00
rbutil Initial framework for the Sandisk Sansa Clip Zip 2011-08-27 16:21:19 +00:00
tools Initial framework for the Sandisk Sansa Clip Zip 2011-08-27 16:21:19 +00:00
uisimulator Dircache: Don't expose struct dircache_entry and pointers into the cache, use IDs instead. 2011-06-20 20:12:42 +00:00
utils Fix free on wrong variable 2011-08-25 20:40:28 +00:00
wps Fix mistaken changes in r30219 2011-08-14 13:14: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!