Developer documentation

Official Code repository Subversion

• Web-interface by ViewVC: http://sourceforge.net/p/codeblocks/code/log/
• Subversion URL: svn://svn.code.sf.net/p/codeblocks/code/trunk or http://svn.code.sf.net/p/codeblocks/code/trunk

Mirror by biplab (Read-only; refreshed every 10 minutes.)

• Subversion URL: svn://cb.biplab.in/codeblocks/trunk
  
• Web-interface: http://cb.biplab.in/websvn/
• Git URL: git://cb.biplab.in/codeblocks.git
• Web-interface:http://cb.biplab.in/cgit/

Mirror by Jens (Read-only; refreshed every 10 minutes.)

• Web-interface: http://cgit.jenslody.de/
• the above link contains many mirrors such as wxWidgets trunk, git mirror, and git mirror of codeblocks.github

Mirror by Obf (Read-only; refreshed manually.)

• Web-interface: https://github.com/obfuscated/codeblocks_sf

Articles for Code::Blocks developers.

• Documentation

User's manual in various formats and languages.

Also see http://developer.berlios.de/projects/codeblocks/ (under the downloads section).

Checkout the SDK documentation at http://developer.berlios.de/project/showfiles.php?group_id=5358 as CHM file(s).

• Compile the complete Code::Blocks from sources on Windows and Linux

• Compile Code::Blocks plugins based on a nightly without the need to compile wxWidgets or the Code::Blocks core.

• Translation

Code::Blocks uses Launchpad to coordinate translation efforts.

• Coding style

The source code formatting style used in the Code::Blocks' source.

• Creating a custom lexer for Code::Blocks editor

How to add support for new syntax lighting schemes.

• Creating a patch to submit to BerliOS (Patch Tracker)

Creating a diff file and then submitting it to the patch tracker.

• Unicode Standards

Information about unicode standards and how unicode is handled in Code::Blocks' source code.

• Various development tips

List of various development tips for Code::Blocks.

• Scripting Code::Blocks

Information about scripting Code::Blocks with Squirrel.

• A short overview about Code::Blocks architecture

Information about the architecture of Code::Blocks.

• Code::Blocks SDK events

Information about the Code::Blocks SDK events and how to work with them.

• File formats description

Description of the format of each file Code::Blocks produces.

• Version control

Tips and trick for working with our version control system.

Plug-In development

• Creating a simple "Hello World" plugin
• Creating a Plug-in which modifies CB's Menus
• Creating a plugin that actually does something
• Linking the plugin to a Nightly Build
• Managing Plug-in Resources

• Research on doing a Plug-in for embedded help in CB

• wxSmith extensions
• Code::Completion Rewrite and Code Completion plugin and Code Completion Design

Scripting

Using scripting to extend Code::Blocks' functionality

• Creating a new project wizard

Debugging C::B

• When C::B crashed, it will generate a call-stack file "codeblocks.RPT", at the crash point, this is a text file, you can open it, if your C::B contains the debug information, it will have file and line information about each call. If it is a stripped version, but you have the debug version of C::B, you can try to run the [/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is a address2line UI interface works under Windows.
• You can debug C::B under C::B (with the debugger plugin), also, you can link C::B to the debug version of wxWidgets library, so you can see whether a bug is located in C::B source code or wxWidgets' source code, see here: [/index.php/topic,17316.msg130972.html#msg130972 patch to build C::B against wx debug library]