FAQ: Rockbox Builds ... What's the difference?

[Kezza]

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.

[saab_rider]

Nice work Kezza.

1) It would be a good idea to put a definition for "patches" in the FAQ in the begining. Something like "What is a Patch?".
2) I beleive there shouldn't be two sections 'Difference between builds" and "Finer points or WHATS IN IT?". Just have a list of applied patches to each build under each one in "difference between builds".
3) Maybe have the names of the builds in bold
4) When the applied patches are listed, they should also be linked.
5) We need details on what version of the daily build was used to compile (date), and version of patch used.
6) last known version (date of update) of the build.
7) Link to archived versions.

[Kezza]

won't the the aurthors page/thread be enough for what patches are in the build? (we can all read and there is a link to each builds first page) this will be a never ending job, don't forget I have to update the archive as well.

[saab_rider]

Originally Posted by kezza

won't the the aurthors page/thread be enough for what patches are in the build?

I guess so, let's see what people think. I was hoping for one format of listing the patches/build details. Each build has had differnt ways on reporting the updates. Some have the first post updated (like in the old Optimized thread and in norbusan's new buld), some report updates in new posts (like paulheu IIRC). In the KOSH build, sometimes I don't know which patches are currently applied, because there isn't a complete list of applied patches with every release. Sometimes one patch is removed in one release, another is added in the next, and it would include patches from two releases back! Hard to follow sometime.

Please don't get me wrong. I'm very grateful to everyone who's volentarely providing these builds. I'd just like to have a clear side-by-side comparison.

[Kezza]

well I'll see if I can get everyone who makes a build to post me an email or PM with the details when making a new build this way I may be able to do what you want.

we will see!

Kezza

[Judge]

Seeing as this is (going to) incorporate H1xx Rockbox (experimental/user) builds as well, I would suggest posting this in the general Rockbox Lounge instead of just in the Rockbox for H3xx forum, or making two: one for the H1xx rockbox forum incorporating the H1xx experimental/user builds and the same for the H3xx rockbox forum with H3xx experimental/user builds. Good work btw.

[bagder]

this build should be the most stable but the last to get extra features.

I disagree with this description. When core developers add features, they mostly show up directly in this version and not as a patch, and then this version is in fact likely to contain the changes before the other builds.

Also, do note that we call it Rockbox no matter what the capsing is in the logo (which looks like "ROCKbox").

[Llorean]

Just as an example, the official version was the first to have TagCache.

[saab_rider]

No disrespect was intended to the devs. I think it boils down to the definition of the word "feature". I beleive the "features" ment in this context are non-core features (most of the time at least). Such as things that are available in patches (album art support, EQ tag, scrolling, among other non-WPS patches).

[Llorean]

You might want to clarify that then, as I think most people would think of TagCache as a feature. As well as "Backdrop image" which was in CVS first (and I think qualifies as your non-core definition).

Core developers can frequently work on new features (though not at the moment because of the feature freeze) so it's really an unrealistic expectation that Rockbox won't in some cases end up with new features first. Of course the unofficial builds will have them very quickly afterward.

[saab_rider]

We're not trying to start a cvs VS patches competition When kezza is back he can fix it.

It would help if you provide an explination which you find more suitable.

[Llorean]

Well, the words "last to get get extra features" seem questionable to me, since some features clearly appear there first.

Perhaps "last to get features from patches, but first to get features developed by the core team"?

[saab_rider]

Sounds right to me! now if kezza can come back from his dinner

[Kezza]

fixed ....... happy now?

anything else and thats not sarcasm.

[Llorean]

Looks good to me.
As I've said, my primary goal is to make sure there's as little confusion as possible about the official portions of the Rockbox project. I'd say that covers it pretty well.

Just as a small note, the CVS Builds and Daily Builds are two different things. CVS builds occur 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. Statistically speaking, the Daily is just as likely to contain major bugs as the Bleeding Edge / CVS build is. And in fact, sometimes it has, the bug has been shortly after, but people have spent 24 hours complaining that the Daily has a major issue simply because they didn't know that the Bleedin Edge build is always available, and that it had the fix in it.

I'm not sure if it's necessary to clear up the different between the two in the above post, but it's something for you to think about mentioning at least.

[badbrain88]

just a noob question here--whats the diff between builds (i.e kosh's specifically) from day to day. i noticed his 2.7.0 was almost double the size of his 2.7.1 (kb's). does this mean i lose features and what not if i use the newer one or is it meant ot be just flashed over the 2.7.0 one?? thanks if you can clarify. or maybe i should ask on kosh's thread?? ill do that aswell.

[Llorean]

I don't know when those two builds happened, but Rockbox stopped including fonts in the daily and CVS builds, since they almost never change anyway, and just posted them as a fonts zip instead.

It's possible the size halved when the fonts were removed.

[badbrain88]

thanks, ill look into it--he made them just a few days ago by the way. ill check when on my own pc tonight

[saab_rider]

As Llorean suggested, we could use a mention of the daily build and bleeding edge build.

Also, a mention that the fonts are in a seperate download.

[Kezza]

Ok added bits on CVS/BE vs in the Daily in the Q&A bit at the top.