Rockbox General > Rockbox General Discussion

Seeking Profesional help.

<< < (2/3) > >>

Travis:
Oh yeah!  :-[ Sorry lol

kenshin:
I got started by looking through the feature request and bug report pages to find something that sounded relatively simple. After digging around for about two hours I discovered tree.c had what I wanted and 30 minutes later I had my first patch ready for upload to the tracker. And since I'm way outside the timezone most of the devs live in (they're asleep when I'm writing code) I just had to pludge through the code getting my hands (and feet!) dirty. Don't give up. It's incredibly rewarding when you see your patch(es) accepted...

XavierGr:
Road Runner.

I start coding similar to your way. First you must be ready and sure on how to apply and make patches and compile rockbox.
If you have mastered thi,s and you know to program a bit then you can contribute to the project.

Unfortunately the only way to understand part of the code is by the comments on the code /*""*/ and by making questions on the IRC channel.

The proccess of understanding the code is the most important and difficult step. If you manage to understand code bits then it should be easy to make your modifications.

Programming for Rockbox is time consuming especially for newbies like us. Keep trying and in the end you will succeed something (minor or major)

kenshin:
I also found the DEBUGF (I think it was the one) macro quite useful since I couldn't get the simulator to run in gdb for some reason.

Road Runner:
Thanks Guys!


--- Quote from: tucoz on September 26, 2005, 01:11:01 PM ---When you build rockbox, you would run ../tools/configure from your build-dir followed by make. If you make changes to a plugin for instance, make will notice that that file has been changed and will under normal circumstances only compile that one.

--- End quote ---

Wow! So I don't have to re-build every day from scratch  :P that's explains alot!

kenshin, I feel the same way [gmt+2:Israel]


--- Quote from: kenshin on September 27, 2005, 02:53:57 PM ---I also found the DEBUGF (I think it was the one) macro quite useful since I couldn't get the simulator to run in gdb for some reason.

--- End quote ---

Thanks I will also look for info about that. for now I don't understand how should you run and debug a code that you can't run on a pc. I mean, what procedure do you use to check if everything compiles properly, I guess debugf has something to do with it.

It will be nice to know what editor is good for that task/what do you use.

Navigation

[0] Message Index

[#] Next page

[*] Previous page