Find a file
Dominik Riebeling 1e12990ba9 rbutil: Rename libbzip2.a to libbz2.a.
When cross compiling for Windows (at least mxe) links bz2, causing both
our copy and the system one getting linked, resulting in symbol clashes.
Make sure we use the same name as the system one, so the linker can pick
one of both.

Change-Id: I16213a20f48d4e192cd0b756931f9ccb449fd1c0
2020-10-22 19:20:48 +02:00
android android: Fix configure script for "newer" versions of the NDK 2020-04-13 16:51:58 +02:00
apps nwza860: fix simulator build 2020-10-19 03:39:33 +00:00
backdrops Add Cabbiev2 port for 128x96x16 targets (Samsung YH-820), made by me. 2014-03-27 19:50:48 +00:00
bootloader fiiom3k: Temporarily disable filter rolloff programming 2020-10-15 07:43:14 -04:00
debian Prepare new maemo release 2013-03-10 12:12:38 +01:00
docs utils: Add (partial) libtomcrypt. 2020-10-18 19:08:32 +02:00
firmware fiio: Another bugfix in the mute code. 2020-10-22 13:16:20 -04:00
fonts Remove superfluous executable bits on a bunch of files. 2011-06-08 14:22:03 +00:00
gdb [1/4] Remove SH support and all archos targets 2020-07-24 21:20:13 +00:00
icons Updated 8x8 tango icons 2020-05-23 09:23:53 -05:00
lib Build: Bump all toolchains to GCC 4.9.4 + Binutils 2.26.1 2020-10-13 16:27:07 +00:00
manual SVG image of the xDuoo X3 and other formats for the manual. 2020-10-11 02:30:53 +00:00
packaging Prepare unofficial pandora release 2013-03-10 14:09:30 +01:00
rbutil rbutil: Rename libbzip2.a to libbz2.a. 2020-10-22 19:20:48 +02:00
tools rbutil: Fix native Windows build for tools. 2020-10-21 21:33:39 +02:00
uisimulator Add UI Simulator for Eros Q / K series 2020-10-21 13:24:01 +00:00
utils rbutil: Fix native Windows build for tools. 2020-10-21 21:33:39 +02:00
wps New port: AIGO EROS Q / EROS K 2020-10-11 16:37:17 -04:00
.gitattributes Add a gitattributes file for the migration. 2011-12-01 14:14:59 +00:00
.gitignore Update .gitignore 2020-08-10 17:52:27 +00:00

               __________               __   ___.
     Open      \______   \ ____   ____ |  | _\_ |__   _______  ___
     Source     |       _//  _ \_/ ___\|  |/ /| __ \ /  _ \  \/  /
     Jukebox    |    |   (  <_> )  \___|    < | \_\ (  <_> > <  <
     Firmware   |____|_  /\____/ \___  >__|_ \|___  /\____/__/\_ \
                       \/            \/     \/    \/            \/

Build Your Own Rockbox

1. Clone 'rockbox' from git (or extract a downloaded archive).

   $ git clone git://git.rockbox.org/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!