Find a file
Jonathan Gordon f0acf02be7 First go at converting the inbuilt statusbar into a skin, right now its only perfect for 176pixel wide displays (and not liked to the build system so you have to copy things yourself if you want it) and needs RTC build.
Whats the easiest way to get this going for all displays/targets without doing 28+ .sbs files?


git-svn-id: svn://svn.rockbox.org/rockbox/trunk@23376 a1c6a512-1295-4272-9138-f99709370657
2009-10-28 05:07:49 +00:00
apps Initial touchscreen support for mini2440. Based on D2 touchscreen driver 2009-10-27 20:25:40 +00:00
backdrops Add CabbieV2 for Onda VX747 2009-03-24 22:05:28 +00:00
bootloader Many more drivers for mini2440. Now the main binary compiles and runs. 2009-10-26 18:16:58 +00:00
docs "No code in .h files or #defines" 2009-10-23 07:26:48 +00:00
firmware remove accidentally commited spaces. 2009-10-27 20:59:26 +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 Correct Id keyword and add svn:keywords property. 2009-10-25 13:40:24 +00:00
rbutil Show status about downloading build information in the status bar. 2009-10-27 19:28:51 +00:00
tools Don't rely on {} expansion since not all shells have that. 2009-10-27 23:40:46 +00:00
uisimulator FS#10700 - Add --noremote option to simulator. 2009-10-26 09:58:39 +00:00
utils Move mknkboot.[ch] to beastpatcher folder. 2009-10-27 21:15:21 +00:00
wps First go at converting the inbuilt statusbar into a skin, right now its only perfect for 176pixel wide displays (and not liked to the build system so you have to copy things yourself if you want it) and needs RTC build. 2009-10-28 05:07:49 +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!