Difference between revisions of "Developer documentation"

From Code::Blocks
m (→‎Developing C::B with Git: Make links to the forum absolute)
m (Some mirrors were dead)
Line 6: Line 6:
 
* Subversion URL: <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki> or <nowiki>http://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>
 
* Subversion URL: <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki> or <nowiki>http://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>
  
'''Mirror by biplab''' (Read-only; refreshed every 10 minutes.)
+
'''Mirror by biplab''' (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)
 
* Subversion URL: <nowiki>svn://cb.biplab.in/codeblocks/trunk</nowiki><br/>
 
* Subversion URL: <nowiki>svn://cb.biplab.in/codeblocks/trunk</nowiki><br/>
 
* Web-interface: http://cb.biplab.in/websvn/
 
* Web-interface: http://cb.biplab.in/websvn/
Line 12: Line 12:
 
* Web-interface:http://cb.biplab.in/cgit/
 
* Web-interface:http://cb.biplab.in/cgit/
  
'''Mirror by Jens''' (Read-only; refreshed every 10 minutes.)
+
'''Mirror by Jens''' (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)
 
* Web-interface: http://cgit.jenslody.de/
 
* Web-interface: http://cgit.jenslody.de/
 
* Git URL: git://jenslody.de/git/codeblocks
 
* 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
 
* 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.)
+
'''Mirror by Obf''' (Read-only; refreshed manually. As 2022-09-12, it looks dead.)
 
* Web-interface: https://github.com/obfuscated/codeblocks_sf
 
* Web-interface: https://github.com/obfuscated/codeblocks_sf
 
* Git URL: see the above page.
 
* Git URL: see the above page.

Revision as of 04:40, 12 September 2022

Official Code repository Subversion

Mirror by biplab (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)

Mirror by Jens (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)

Mirror by Obf (Read-only; refreshed manually. As 2022-09-12, it looks dead.)


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
Code::Blocks uses Launchpad to coordinate translation efforts.
See also [/index.php/topic,1022.msg159075.html#msg159075 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.

Plug-In development

Scripting

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.

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