Articles for Code::Blocks developers.
- 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).
- Browse SDK documentation at http://alpha0010.github.io/cb-docs/ as html.
- 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.
- See also Code::Blocks' translation
- The source code formatting style used in the Code::Blocks' source.
- How to add support for new syntax lighting schemes.
- Creating a diff file and then submitting it to the patch tracker.
- Information about unicode standards and how unicode is handled in Code::Blocks' source code.
- List of various development tips for Code::Blocks.
- Information about scripting Code::Blocks with Squirrel.
- Information about the architecture of Code::Blocks.
- Information about the Code::Blocks SDK events and how to work with them.
- Description of the format of each file Code::Blocks produces.
- Tips and trick for working with our version control system.
- 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
Using scripting to extend Code::Blocks' functionality
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 Re: Read-only Git, SVN Repo for Code::Blocks, also stahta01 has a nice instruction about how to use git, see Development How to use a Code::Blocks Git Repo.
If you want to create a SVN style patch from git, see: This forum post.
- 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 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: patch to build C::B against wx debug library