Rockbox
Find a file
Aidan MacDonald ad66c3b807 touchscreen: use repeat acceleration for button input
Touch devices have physical buttons too, and these should be
subject to repeat acceleration. That feature was disabled for
the sake of better touch event responsiveness (apparently).

So, re-enable the acceleration feature & add a special case
to exempt BUTTON_TOUCHSCREEN from acceleration.

Change-Id: I9e097e27457fbd6b824f098e8b325ff35c59dde4
2021-11-21 20:26:20 +00:00
android android: Fix configure script for "newer" versions of the NDK 2020-04-13 16:51:58 +02:00
apps Revert "Pictureflow: Update for tag_virt_canonicalartist." 2021-11-21 12:44:57 -05:00
backdrops New port: Shanling Q1 native 2021-07-13 22:01:33 +01:00
bootloader Sansa E200v1 Bootloader ensure USB unplug is detected 2021-10-04 16:42:36 -04:00
debian Prepare new maemo release 2013-03-10 12:12:38 +01:00
docs usb: introduce new control request API 2021-10-16 15:58:43 -04:00
firmware touchscreen: use repeat acceleration for button input 2021-11-21 20:26:20 +00:00
fonts
gdb Nuke the never-functional iriver ifp-7xx port 2021-04-26 07:42:58 -04:00
icons Revert Non-Alpha Updated 8x8 tango icons 2020-10-25 16:21:58 +00:00
lib metadata/mp3data.c init vars & add sanity checks 2021-08-11 22:40:09 -04:00
manual Add setting for disabling wrap-around lists 2021-11-11 17:31:10 -05:00
packaging Prepare unofficial pandora release 2013-03-10 14:09:30 +01:00
rbutil Revert "rbutil: Remove done() signal from Themes Install window." 2021-08-04 19:10:34 +02:00
tools x1000: Merge makefiles used for the bootloader 2021-11-18 14:14:54 -05:00
uisimulator uisimulator: add keyboard mappings for M3K scrollstrip 2021-11-12 19:51:23 +00:00
utils x1000: fix broken OST2 timer prescaler 2021-10-16 16:58:19 -04:00
wps New port: Shanling Q1 native 2021-07-13 22:01:33 +01:00
.gitattributes
.gitignore jztool: New utility for installing a bootloader on FiiO M3K 2021-04-17 20:23:19 +00:00
.gitreview misc: Add a .gitreview file for better gerrit integration 2021-06-24 07:22:19 -04: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 mips/m68k/arm-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 generated using the rockboxdev.sh script in the /tools/ folder of the
   source.

   $ which arm-elf-eabi-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-fuzeplus
   $ cd build-fuzeplus
   $ ../tools/configure

   $ mkdir build-xduoox3
   $ cd build-xduoox3
   $ ../tools/configure

Questions anyone? Ask on the mailing list or on IRC. We'll be happy to help you!