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/
• Git URL: git://jenslody.de/git/codeblocks
• the above Web-interface link contains many other 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
• Git URL: see the above page.

Articles for Code::Blocks developers.

• Documentation

User's manual in various formats and languages.

Browse SDK documentation at http://alpha0010.github.io/cb-docs/ as html.

• 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.

Code::Blocks uses Launchpad to coordinate translation efforts.

• Old Translation page
• New Translation page

See also [/index.php/topic,1022.msg159075.html#msg159075 Code::Blocks' translation]

• 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 (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

• Plugin structure of C::B
• 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

Developing C::B with Git

For devs who want to use Git to develop C::B, here are some steps to follow, especially you need to correctly set the SVN and GIT properties so that you can make your local git commits back to the official SVN repo. See [/index.php/topic,16096.msg128152.html#msg128152 Re: Read-only Git, SVN Repo for Code::Blocks], also stahta01 has a nice instruction about how to use git, see [/index.php/topic,19533.msg133422.html#msg133422 Development How to use a Code::Blocks Git Repo].

If you want to create a SVN style patch from git, see: [/index.php/topic,19391.msg132530.html#msg132530 This forum post].

Debugging C::B

• When C::B crashes, it will generate a call-stack file "codeblocks.RPT", at the crash point (see this for more information). This is a text file that you can open; if your C::B contains the debug information, it will have file and line information about each call. If your C::B is a stripped version, but you have the debug version of C::B, you can try to run the Debugging made easier, this is an address2line UI interface that 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: patch to build C::B against wx debug library