212e7808d5
As well as using an index, which breaks when a file is added or removed, use the crc32 of the filename. When the crc32 check passes the index is used directly. When it fails, the slow path is taken checking each file name in the playlist until the right crc is found. If that fails the playlist is started from the beginning. See http://www.rockbox.org/tracker/6411 Bump plugin API and nvram version numbers Change-Id: I156f61a9f1ac428b4a682bc680379cb6b60b1b10 Reviewed-on: http://gerrit.rockbox.org/372 Tested-by: Jonathan Gordon <rockbox@jdgordon.info> Reviewed-by: Jonathan Gordon <rockbox@jdgordon.info> |
||
---|---|---|
.. | ||
logo | ||
API | ||
BATTERY-FAQ | ||
BATTERY-FAQ-LIION | ||
CHARGING_ALGORITHM | ||
COMMITTERS | ||
CONTRIBUTING | ||
COPYING | ||
COPYING-MANUAL | ||
CREDITS | ||
gpl-2.0.html | ||
HISTORY | ||
KNOWN_ISSUES | ||
LICENSES | ||
MAINTAINERS | ||
NODO | ||
PLUGIN_API | ||
profontdoc.txt | ||
README | ||
sample.colours | ||
sample.icons | ||
TECH | ||
UISIMULATOR |
__________ __ ___. 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!