Rockbox
Find a file
Daniel Stenberg b285076925 Remade the menu system slightly. All functions invoked from menus now use
the Menu typedef as return type, and *ALL* menus that intercept USB connect
can then return MENU_REFRESH_DIR so that the parent (any parent really) that
do file or dir-accesses knows that and can do the refresh. If no refresh
is needed by the parent, MENU_OK is returned.

Somewhat biggish commit this close to 1.3, but we need to sort out this
refresh-after-usb-connected business.


git-svn-id: svn://svn.rockbox.org/rockbox/trunk@1948 a1c6a512-1295-4272-9138-f99709370657
2002-08-23 12:32:52 +00:00
apps Remade the menu system slightly. All functions invoked from menus now use 2002-08-23 12:32:52 +00:00
CVSROOT Removed cvs@haxx.se again 2002-06-07 11:14:47 +00:00
docs typo 2002-08-22 07:03:17 +00:00
firmware Missing break in the SYS_USB_CONNECTED case 2002-08-23 09:36:49 +00:00
gdb Fixed scramble path and main target 2002-06-19 12:04:21 +00:00
tools we like each line less than 80 characters wide please 2002-08-21 16:34:41 +00:00
uisimulator removed backlight-win32.c as it is not needed any more 2002-08-22 17:59:20 +00:00
www added some people 2002-08-22 20:42:49 +00:00

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

Build your own archos.mod.

1. Check out 'firmware', 'apps' and 'tools' from CVS (or possibly from a
   downloaded archive). You may possibly want 'uisimulator' too (for trying
   out things on host before making target tests).  If you haven't already
   done so, we advise you pull down the 'docs' directory as well.

   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. 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. Make sure you have sh-elf-gcc and siblings in the PATH.

6. *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.

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