Best way to become familar with the source code

[jimbo]

Bit of a vague question, but having written the basis of a New Project Wizard I now want to look in to the actual code base in more detail, with a view to adding stuff for our purposes. Had a read through the Wiki, but it's a bit vague in places, so was wonder how other new developers approach learning the Codeblocks source and venturing in to writing new stuff for it. I am currently interested in being able to set up the debugger from the New Project wizard stuff.

Ta

Jimbo.

[stahta01]

I read the source code; but, you might try the SDK document file, first.

That was on the sf.net website; no idea if it is up to date.

Tim S.

[oBFusCATed]

Reading the source is the best way.
Start with the src/include and src/sdk folders.

I am currently interested in being able to set up the debugger from the New Project wizard stuff.

Search the tickets page on sf.net there is an issue about it and we've discussed it I think.

[jimbo]

Reading the source is the best way.
Start with the src/include and src/sdk folders.

I am currently interested in being able to set up the debugger from the New Project wizard stuff.

Search the tickets page on sf.net there is an issue about it and we've discussed it I think.

Checked out the tracker, and also this forum thread,http://forums.next.codeblocks.org/index.php/topic,16852.0.html

There were some patches flying around, but woudl be interested to know what the status of this is. Where the patches applied? We need to be able to set up OpenOCD automagically in the Wizard, looks like this will mostly do it if the patches are there. It appears there will still be some work required to ensure the debugger plugin itself does not overwrite the wizardly additions?

[oBFusCATed]

If I remember correctly I expressed several concerns with the patches. I don't think they are in master/trunk.