CONSTRUCTION AREA
Go to file
Robert Menes 872852639f A man who is long due for credit: added Christophe "toffe"
Nicolas to the credits for all of his Gigabeat findings.


git-svn-id: svn://svn.rockbox.org/rockbox/trunk@23300 a1c6a512-1295-4272-9138-f99709370657
2009-10-20 21:05:23 +00:00
apps usb_keypad_mode shouldn't depend on SIMULATOR 2009-10-20 17:30:42 +00:00
backdrops Add CabbieV2 for Onda VX747 2009-03-24 22:05:28 +00:00
bootloader Initial mini2440 port. 2009-10-19 18:14:27 +00:00
docs A man who is long due for credit: added Christophe "toffe" 2009-10-20 21:05:23 +00:00
firmware D2: Remove the hardcoded driver-level touchscreen calibration, since it's done at apps level as well now. 2009-10-20 20:57: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 Add beastpatcher download location to the Gigabeat S manual, and add dual-boot bootloader install instructions. 2009-10-19 18:15:10 +00:00
rbutil rbutil: Updated Hebrew translation 2009-10-19 19:29:33 +00:00
tools wps_screen is still needed for the HAVE_REMOTE_LCD case 2009-10-20 17:15:12 +00:00
uisimulator Working Nano2G UI sim. UI-ipodnano2g.bmp courtesy of Marianne Arnold, based on her SVG for the manual. 2009-10-14 21:40:28 +00:00
utils Make beastpatcher build with VS2005 again. 2009-09-24 20:46:19 +00:00
wps Initial custom statusbar commit. 2009-10-19 15:28:15 +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!