Rockbox General > Rockbox General Discussion

A beginner's overview to applying a patch (just because people have been asking)

(1/4) > >>

Mikerman:
Because many people have been asking how to apply patches recently, I offer this overview.  Note that the basic instructions for the various steps already are listed in the Rockbox Documentation (see the banner at left, and use the index); they are linked to below. Of great value is the Rockbox Simple Guide to Compiling (http://www.rockbox.org/twiki/bin/view/Main/SimpleGuideToCompiling), which should be your overall reference.

Most importantly, note that you have to apply a patch as against the Rockbox source code, not the already compiled code that you download at the Downloads page (the code that you simply unzip to install). In the end, then, you need to:

1. Download and set up a source code "compiler" (Cygwin, or as part of the VMWare environment), to compile the Rockbox source code that you download and then patch.  

Cygwin:

http://www.rockbox.org/tw...winInstallWithScreenShots
http://www.rockbox.org/tw...ew/Main/CygwinDevelopment

VMWare:

http://www.rockbox.org/tw...VMwareDevelopmentPlatform

2. Download the source code.

See the Simple Guide.

http://www.rockbox.org/tw...in/SimpleGuideToCompiling

3. Patch the source code.

See the Simple Guide (towards the middle of the instructions).

4. Compile the code.

See the Simple Guide.

http://www.rockbox.org/twiki/bin/view/Main/HowToCompile

This takes real time to do the first time (especially to set up the compiler). But it is much faster thereafter: if you originally used the SVN system to download the source code, just use the SVN source code update system (as explained in the Simple Guide, towards the end) to update your current (and patched, if applicable) version of the source code with the Rockbox source code revisions since your last download, and if there are no major changes affecting your patch(es), you don't have to re-patch; and then compile (hence, the great benefit of using the SVN system to begin with). If the code update conflicts with your patched version of the source code, see the Simple Guide for means by which to try to handle that, potentially manually (but eminently do-able--really!).

I hope this helps.

Llorean:
Again: The forums are NOT for static information. They're for discussion. The wiki is for tutorials and other things.

Why not improve the SimpleGuideToCompiling page, or create a new wiki page for a patching tutorial?

I'll be removing this post in a couple days.

Mikerman:
The reason I placed this here is because beginners are asked in the forums how to do patch, without getting to the Documentation to begin with (or really understanding what patching involves).  The "how-to" section here got a bit carried away, granted; I guess I really could have just said, see the Simple Guide, but that's static information in and of itself ...

Llorean:
If people can't get to the documentation, they're not going to read other posts either, probably. If they searched posts, then they would surely see the many redirections to SimpleGuideToCompiling as it's brought up in nearly every post asking about patching.

soap:
cough
coLinux

Navigation

[0] Message Index

[#] Next page