Rockbox Technical Forums
Rockbox Development => Starting Development and Compiling => Topic started by: greatjack on February 25, 2017, 07:40:06 PM
-
Hello everyone,
I have always been a long time user of rockbox and in the past 5 years have gotten very involved in the programming world and have learned java, .net and most recentely c. I have followed the development guide that has been posted and I have a clone of the rockbox repository sitting on my computer ready to tweak, however I am totally confused with the structure of the git repository and how it knows which files to compile for each device.
Would anyone be able to point me to a guide that discusses the structure of the repository and how to make changes to all targets, or just to one.
Im a relative noob, so the clearer the better.
Thanks in advance
-
There are some links here, mostly for things like plugins, codecs or new devices:
https://www.rockbox.org/wiki/ContributingToRockbox
Most files will change all builds, or at least a lot of them, unless they're somehow specific to a single device. The makefiles decide what files to compile by parsing the SOURCES and SUBDIRS folders in the repo.
-
About the repository layout, most high-level stuff such as plugins and UI code goes in apps/, while firmware/ holds most of the target-specific code and drivers.
-
What do you want to work on?
-
Thanks all for responding.
As for your question saratoga.
I dont think I would be good at embedded work such as reverse engineering drivers etc, however I have pretty solid code cleanup and organization skills.
I also have a interest in writing high level plugins using the plugin api which I allready started working on
-
Another thing that I would like to work on is since I have andorid experiance, although not so much jni/ndk, would be to improve the android port as well get it to work on art. I have allready started working on it, and will report progress soon (if there is) ;)