Difference between revisions of "Scripting Code::Blocks"

From Code::Blocks
m (moved under "Developer Documentation")
Line 15: Line 15:
  
 
'''[[Build scripts|Build]]'''
 
'''[[Build scripts|Build]]'''
: Extend the build system. Scripts can be attached to projects and/or build targets and are executed before and/or after each of these is built.
+
: Extend the build system. Scripts can be attached to projects and/or build targets and are executed before and/or after each of these is built.<br/>
 +
 
 +
'''[[Variable expansion]]'''
 +
:As a special case of [[variable expansion]], scripts can be run in place of a variable, expanding to the output generated by the script.
 +
 
  
 
More Code::Blocks parts may be exposed to scripting in the future.
 
More Code::Blocks parts may be exposed to scripting in the future.

Revision as of 14:14, 29 November 2006

Code::Blocks supports scripting to extend various parts of its functionality during runtime. The scripting language used is Squirrel.

Currently, Code::Blocks uses scripts for:

Startup

Run arbitrary commands on application startup.

Wizards

Register new wizards for generating projects, build targets, files or anything else. All wizards shipped with Code::Blocks are scripted.

Debugger

Extend the GNU Debugger (and others) to support arbitrary data types. Code::Blocks ships with scripts that add wxString, std::string and std::vector "knowledge" to the GNU Debugger.

Build

Extend the build system. Scripts can be attached to projects and/or build targets and are executed before and/or after each of these is built.

Variable expansion

As a special case of variable expansion, scripts can be run in place of a variable, expanding to the output generated by the script.


More Code::Blocks parts may be exposed to scripting in the future.

See also

External links