rockbox

History

Björn Stenberg 4b422aaa36 Fixed tighter looping scroll. git-svn-id: svn://svn.rockbox.org/rockbox/trunk@977 a1c6a512-1295-4272-9138-f99709370657		2002-06-12 15:15:51 +00:00
..
common	Added check for open-for-write	2002-06-07 15:15:10 +00:00
drivers	Fixed tighter looping scroll.	2002-06-12 15:15:51 +00:00
malloc	realloc takes a void * as first argument	2002-05-27 07:25:30 +00:00
test	Now uses librockbox.a	2002-05-17 08:07:23 +00:00
API	Added some kernel docs	2002-06-04 12:48:08 +00:00
app.lds	New section for reset vectors	2002-05-29 09:12:34 +00:00
chartables.c	Removed compiler warnings	2002-06-11 10:35:28 +00:00
CONFIG	documented HAVE_NEW_CHARCELL_LCD	2002-04-25 15:22:58 +00:00
config-player.h	Added HAVE_NEW_CHARCELL_LCD	2002-04-25 15:09:32 +00:00
config-playerold.h
config-recorder.h
config.h	removing #define CRT_DISPLAY ;)	2002-04-30 20:16:44 +00:00
CONTRIBUTING
CREDITS	Added Stefan Meyer	2002-05-08 12:46:13 +00:00
crt0.S	New section for reset vectors	2002-05-29 09:12:34 +00:00
debug.c	output debugf() nicely for simulator builds too	2002-06-04 22:03:21 +00:00
debug.h	output debugf() nicely for simulator builds too	2002-06-04 22:03:21 +00:00
FILES	add the FILES file itself	2002-05-29 08:56:30 +00:00
gdb.lds	New section for reset vectors	2002-05-29 09:12:34 +00:00
id3.c	NOTE! the 'mp3entry' struct grew quite a bit now, as the previously static	2002-06-04 22:05:00 +00:00
id3.h	NOTE! the 'mp3entry' struct grew quite a bit now, as the previously static	2002-06-04 22:05:00 +00:00
kernel.c	Added init_threads function	2002-06-07 14:56:10 +00:00
kernel.h	Clarified the mutex code, renamed the NUM_TICK_TASKS macro	2002-06-04 12:47:39 +00:00
Makefile	.S files should be compiled with gcc, not gas	2002-05-24 16:20:49 +00:00
mpeg.c	mpeg_stop now calls close only if the file handle is valid	2002-06-10 10:46:12 +00:00
mpeg.h	First version	2002-05-24 12:22:14 +00:00
panic.c	do the lcd_puts() properly for the recorder too	2002-05-24 09:02:35 +00:00
panic.h	Changed debug to DEBUGF and panic to panicf.	2002-05-02 14:05:51 +00:00
README	building instructions as was just posted to the mailing list	2002-05-23 15:00:44 +00:00
rockbox-mode.el	Added bool font coloring	2002-05-13 13:15:38 +00:00
settings.c	Removed a warning	2002-06-07 15:30:37 +00:00
settings.h	header for user settings	2002-04-30 19:17:03 +00:00
system.c	New system_init function	2002-05-29 09:11:04 +00:00
system.h	Changed frequency for Recorder	2002-06-07 10:29:14 +00:00
thread.c	Removed a warning	2002-06-07 15:03:19 +00:00
thread.h	Added init_threads function	2002-06-07 14:56:10 +00:00

README

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

Build your own archos.mod.

1. Check out 'firmware' and 'apps' from CVS (or possibly form a downloaded
   archive). You probably want to check out 'tools' too (to get the configure
   script if nothing else) and possibly the 'uisimulator' too (for trying out
   things on host before making target tests).

2. Create your own build directory. This is where all generated files will be
   put.

3. 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. 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.

4. *ploink*. Now you have got a Makefile generated for you. Run 'make' and
   soon the necessary pieces from the firmware and the apps directories have
   been compiled and linked.

5. Copy the archos.mod file to your archos, reboot it and *smile*.

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!