Support and General Use > Plugins/Viewers

prebuilt patches

<< < (2/3) > >>

bluebrother:
a patch in the open source world is usually a source patch, which means it contains the changes to the source needed to change or implement something. Binary patches are uncommon; they are also mostly unneeded as you can distribute the source form. Binary patches are always dependent on a specific binary which makes it quite problematic for certain distribution forms.

You can't just add some binary bit. Even for binary patches, you would always need to use everything or nothing. If you want to control every single bit you need to compile yourself...

drumthrasher109:
all i wanted was the chopper game. now i have it cause of someone elses build.

mlind:
Would there be any problems using PLUGINS from one build in another - assuming the difference is only in the plugin code?

drumthrasher109:
?
all i was wondering was if i could just get the .rock file for whatever patch i want instead of making a whole new build.
i tried making my own build before but it didn't work...half the plugins wouldn't go in and i couldn't actually compile into a zip.

nls:
If your patch is just a _plugin_ that doesn't modify the plugin API (or any other part of the core of rockbox) a prebuilt .rock (for your specific player) will most likely work.
The reason you're told you have to compile to use patches is that most of them modify the rockbox core.

Navigation

[0] Message Index

[#] Next page

[*] Previous page