Nyaaori/rockbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
Rockbox
3600 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
Daniel Stenberg 8fd7828148 Don't pass in TOOLSDIR to the simulator Makefile until we've made the path 
absolute. Using a relative path is not wise, since we use make -C when we
build the simulator and the relative path to the tools dir is not the same
from the build dir as from the simulator's main source dir...


git-svn-id: svn://svn.rockbox.org/rockbox/trunk@3615 a1c6a512-1295-4272-9138-f99709370657
2003-04-25 12:50:25 +00:00
apps Added version to created .cfg file (Johan Vromans) 2003-04-25 10:33:38 +00:00
CVSROOT Added module 'shortcuts' for simpler checkout. 2002-12-12 12:22:44 +00:00
docs Better power calculations 2003-04-23 11:52:01 +00:00
firmware use size_t and not int as the prototype says so 2003-04-25 12:43:44 +00:00
gdb Fixed scramble path and main target 2002-06-19 12:04:21 +00:00
tools Don't pass in TOOLSDIR to the simulator Makefile until we've made the path 2003-04-25 12:50:25 +00:00
uisimulator use size_t instead 2003-04-25 12:43:10 +00:00
www added link to the digest 2003-04-23 13:09:07 +00:00

docs/README 

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

Build Your Own Rockbox

1. Check out 'rockbox' from CVS (or possibly from a downloaded archive). You
   may possibly want to check out 'rockbox-devel' instead, since that includes
   the simulator code (for trying out things on host before making target
   tests).

   If you do want to play with the simulator, read UISIMULATOR.

2. Build the tools by running 'make' in the tools/ directory.

3. Create your own build directory, preferably in the same directory as the
   firmware/ and apps/ directories. This is where all generated files will be
   put.

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.

5. *ploink*. Now you have got a Makefile generated for you.

6. Make sure you have sh-elf-gcc and siblings in the PATH. Make sure that you
   have 'perl' in your PATH too.

7. Run 'make' and soon the necessary pieces from the firmware and the apps
   directories have been compiled, linked and scrambled for you.

8. Copy the archos.mod or ajbrec.ajz file to your archos, reboot it and
   *smile*.  Recent Rockbox versions need no reboots, just PLAY a new rockbox
   version and that'll be loaded and replace the currently running version.

Whenever the tools/configure script gets updated, you can make your makefile
updated too by running 'tools/configure update'

If you want to build for more than one target, just create a new build
directory and create a setup for another target combination in there.

Questions anyone? Take them to the mailing list. We'll be happy to help you
out!