Nyaaori/rockbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
Rockbox
16306 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
Dave Chapman 9ce0261211 Oops, I should try compiling things before committing... 
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@16394 a1c6a512-1295-4272-9138-f99709370657
2008-02-23 20:50:26 +00:00
apps When starting playback, prevent the codec from starting to decode too early, which would cause rebuffering (slowing things down) and incorrect playlist index. Hopefully fixes a bunch of playback-related bugs, such as FS#8520, FS#8525, FS#8555 and possibly FS#8511. 2008-02-23 17:46:33 +00:00
backdrops Add backdrops/, icons/ and utils/ as well as some missing rwpses to the tarballs. 2008-01-23 23:31:04 +00:00
bootloader Give the Gigabeat S bootloader the ability to untar a tarball. 2008-02-17 23:17:08 +00:00
docs FS#8613 Update the bulgarian translation by Nicolay Jordanov and add him to the credits. 2008-02-16 19:32:35 +00:00
firmware Identify info endianness is already handled in the ATA driver. 2008-02-23 08:22:12 +00:00
flash Include some more stuff in the tarballs. 2007-09-04 21:53:33 +00:00
fonts Binary font committed by mistake? 2008-01-24 00:00:10 +00:00
gdb Renamed 'archos' to 'modelname' in the configure script and the Makefiles 2008-01-23 10:59:17 +00:00
icons Add backdrops/, icons/ and utils/ as well as some missing rwpses to the tarballs. 2008-01-23 23:31:04 +00:00
manual Accept FS#8612 by Alexander Levin include 2008 in the manual copyright notice 2008-02-17 09:36:19 +00:00
rbutil When building a static linux binary link libusb static. 2008-02-21 19:55:42 +00:00
tools Significantly speed up SAPI4 voice file creation. Still rather slow compared to SAPI5, but doesn't take hours anymore. 2008-02-20 23:08:00 +00:00
uisimulator UI Simulator for Gigabeat S. 2008-02-08 08:33:17 +00:00
utils Oops, I should try compiling things before committing... 2008-02-23 20:50:26 +00:00
wps Third time's the charme - even if it's just in comments, no mention of the weather etc. necessary. 2008-02-23 13:25:43 +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!