FAQ: Rockbox Builds ... Whats the difference?
Have you asked yourself this question and not been able to find the answer, Well lets try and sort this out then.
first some questions and answers for the basic stuff in case your a noob to all this.
Q. Rockbox what is it
A. Rockbox is an open source firmware for your MP3 player/Jukebox/music player/what ever you want to call it, it is the operating system for the player.
Q. Who makes rockbox and why should I use it etc.
A. look here
www.rockbox.org or here
Rockbox Frequently Asked Questions for lots more info on Rockbox.
Q. What is a build
A. A build is the package (zip file) you download and unzip onto your players harddrive.
Q. What does CVS mean?
A. Concurrent Versions System
(this is in the rockbox FAQ) link above
Q. What is a Patch?
A. When we speak of 'patches' in the Rockbox project, we mean a set of changes to one or more source files.
taken from rockbox FAQ
Q. What is the difference between CVS/Bleeding Edge Builds vs Daily Builds
A. The CVS Build or Bleeding Edge Build and Daily Build are two different things. CVS/BE build occurs every time a change is made from the source, while the Daily Build is just a copy of whatever the last CVS build was right before a certain time each day.
Q. How do I make my own build
A. Start by looking here
How To Patch and Compile Tutorial (From WINDOWS)
Q. I want to find out "how to" make a WPS/add album art/etc
A. This is a great FAQ
CURRENT [HOWTO] ROCKBOX GUIDES
The Official Rockbox Builds (H100 and H300)
(Official ROCKBox Daily Build by the ROCKBox team) Most important, the CVS/Bleeding Edge/Daily builds are Rockbox in its raw form, with no patches. Patches become part of the CVS after testing, but only when developers think the patches are stable enough. This build should be the most stable. It is the last to get features from patches, but first to get features developed by the core team.
Unofficial Builds (H100)
(unofficial) "
ROCKbox H100 Experimental build" (compiled by pilot000 link to his homepage
here) It includes patches, will be unstable from time to time depending on what patches are inculded, is one of the first builds to add in extra features from patches.
Unofficial Builds (H300)
(unofficial) Experimental build by KOSH was aka Optimized build (was compiled by needle boy - now by Paulheu) most new patches are added, will be unstable from time to time depending on what patches are in and so on, is one of the first builds to add in extra features from patches.
(unofficial) Currently titled "
New build for h300" (compiled by norbusan) rediffed patches added (not to sure what rediffing is but it seems he rebuilds patches to fit the build and seems to make it a little more stable) has patches so will be unstable from time to time, has patches so will have new features from patches.
(unofficial) In my opinion the best name "
H3xx "halfway" build" (compiled by drippydonut) only 2-3 patches added (patches needed for most WPSs to display correctly) 2nd most stable build as it has less patches than the rest, 2nd to last to get new features from patches.
(unofficial) The newest build to date and one of the simplest "
Minimal build" (compiled by kin242) only 1 patch added but this is not what makes it simple taken alot of stuff out (All language files except english removed; All wps, rwps & themes removed, DGT Vista & rockbox default themes & wps only; All plugins removed; and the only font left in is nedore-9.fnt) other than the official build this one would be the most stable build as it has only one patch at the moment and only one wps, not many new features from patches.
Depending on which build you download the font packs and some extras may be a separate download from the build.
Fonts can be downloaded from www.rockbox.org/download/
All builds old and new and extras/font packs for the H3xx can be found here
Rockbox Experimental Archive For The H3xx
Now that you know a bit more here are some suggestions and links.
Reporting bugs
If someone faced problems with a user build, we urge him/her to try out the official build. Instructions on what to do exactly are available in this FAQ. If the problem doesn't re-occur in the official build, the bug can be isolated as a problem with a certain patch. It would be best in that situation to contact the writer of the problematic patch to fix it. However, If the problem still persisted on the official build, the bug should be reported in the following order:
1. Ask if it's known in the
RB IRC channel, just to see if anyone knows.
2. Ask if it's an actual bug, or just something you're doing wrong at the
RB forums.
3. If nobody responds at either of those (or if someone says it's a bug, but not a known one) put it up at
the bug tracker.
Please post any questions we have not answered below, so they may be added to the FAQ.