Difference between revisions of "Developer documentation"

From CodeBlocks
Jump to: navigation, search
(add git urls.)
(Plug-In development: add a new page about the plugin structure)
 
(5 intermediate revisions by 3 users not shown)
Line 27: Line 27:
 
* '''<u>Documentation</u>'''
 
* '''<u>Documentation</u>'''
 
:[http://www.codeblocks.org/manual.shtml User's manual] in various formats and languages.
 
:[http://www.codeblocks.org/manual.shtml User's manual] in various formats and languages.
:Also see http://developer.berlios.de/projects/codeblocks/ (under the downloads section).
+
:Browse SDK documentation at http://alpha0010.github.io/cb-docs/ as html.
: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 '''[[Installing Code::Blocks from source on Windows|Windows]]''' and '''[[Installing Code::Blocks from source on Linux|Linux]]'''
 
* Compile the complete Code::Blocks from sources on '''[[Installing Code::Blocks from source on Windows|Windows]]''' and '''[[Installing Code::Blocks from source on Linux|Linux]]'''
Line 36: Line 35:
 
* '''[http://launchpad.net/products/codeblocks/ Translation]'''
 
* '''[http://launchpad.net/products/codeblocks/ Translation]'''
 
:Code::Blocks uses Launchpad to coordinate translation efforts.
 
:Code::Blocks uses Launchpad to coordinate translation efforts.
 +
:See also [http://forums.codeblocks.org/index.php/topic,1022.msg132499.html#msg132499 Code::Blocks' translation]
  
 
* '''[[Coding style]]'''
 
* '''[[Coding style]]'''
Line 43: Line 43:
 
:How to add support for new syntax lighting schemes.
 
:How to add support for new syntax lighting schemes.
  
* '''[[Creating a patch to submit to BerliOS (Patch Tracker)]]'''
+
* '''[[Creating a patch to submit (Patch Tracker)]]'''
 
:Creating a diff file and then submitting it to the patch tracker.
 
:Creating a diff file and then submitting it to the patch tracker.
  
Line 69: Line 69:
 
== Plug-In development ==
 
== Plug-In development ==
  
 +
* [[Plugin structure of C::B]]
 
* [[Creating a simple "Hello World" plugin]]
 
* [[Creating a simple "Hello World" plugin]]
 
* [[Creating a Plug-in which modifies CB's Menus]]
 
* [[Creating a Plug-in which modifies CB's Menus]]

Latest revision as of 16:02, 5 October 2015

Official Code repository Subversion

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

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

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


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