code block 官方使用手册

CodeBlocks

Manual

Version 1.1

Thanks to the CodeBlocks team:

Anders F. Bj¨orklund (afb), Biplab Kumar Modak (biplab), Bartomiej wiecki (byo), Paul

A. Jimenez (ceniza), Koa Chong Gee (cyberkoa), Daniel Orb (daniel2000), Lieven de Cock

(killerbot), Yiannis Mandravellos (mandrav), Mispunt (mispunt), Martin Halle (morten-

macfly), Jens Lody (jens), Jerome Antoine (dje), Damien Moore (dmoore), Pecan Heber

(pecan), Ricardo Garcia (rickg22), Thomas Denk (thomasdenk), tiwag (tiwag)

The below illustration shows the design of the CodeBlocks user interface.

Figure 1.1: IDE CodeBlocks

Management This window contains the interface ’Projects’ which will in the following

text be referred to as the project view. This view show all the projects opened in

CodeBlocks at a certain time. The ’Symbols’ tab of the Management window shows

symbols, variables etc..

Editor In the above illustration, a source named hello.c is opened with syntax high-

lighting in the editor.

Open files list shows a list of all files opened in the editor, in this example: hello.c.

CodeSnippets can be displayed via the menu ’View’ →’CodeSnippets’ . Here you can

• Row and column number of the current cursor position in the editor.

• The configured keyboard mode for inserting text (Insert or Overwrite).

• Current state of a file. A modified file will be marked with Modified otherwise this

entry is empty.

• The permission of a file. A file with read only settings will display Read only in the

status bar. In the window ’Open files list’ these files will be emphasised with a lock

as icon overlay.

Note:

In the active editor the user can select the context menu properties.

In the appearing dialog in the tab ’General’ the option ’File is read-

file <personality>.conf.

CodeBlocks offers a very flexible and comprehensive project management. The following

text will address only some of the features of the project management.

1.1 Project View

In CodeBlocks, the sources and the settings for the build process are stored in a project

file <name>.cbp. C/C++ sources and the corresponding header files are the typical

components of a project. The easiest way to create a new project is executing the command

’File’ →’Project’ and selecting a wizard. Then you can add files to the project via the

context menu ’Add files’ in the Management window.

CodeBlocks governs the project files in categories according to their file extensions. These

extensions of your own. For example, if you wish to list linker scripts with the *.ld

extension in a category called Linkerscript, you only have to create the new category.

Note:

If you deactivate ’Project tree’ →’Categorize by file types’ in the

context menu, the category display will be switched off, and the files

will be listed as they are stored in the file system.

1.2 Notes for Projects

In CodeBlocks, so-called notes can be stored for a project. These notes should contain

short descriptions or hints for the corresponding project. By displaying this information

during the opening of a project, other users are provided with a quick survey of the

specific switches etc. in templates. These templates will be stored in the Documents and

Settings\<user>\Application Data\codeblocks\UserTemplates directory. If the tem-

plates are to be open to all users, they have to be copied to a corresponding directory of

the CodeBlocks installation. These templates will then be displayed at the next startup

of CodeBlocks under ’New’ →’ Project’ →’User templates’ .

Note:

The available templates in the Project Wizard can be edited by se-

lection via right-click.

1.4 Create Projects from Build Targets

In projects it is necessary to have different variants of the project available. Variants are

contains debug information and one ’Release’ Target without this information. By adding

Virtual Targets via ’Project’ →’Properties’ →’Build Targets’ individual Build Targets

can be combined. For example, a Virtual Target ’All’ can create the Targets Debug and

Release simultaneously. Virtual Targets are shown in the symbol bar of the compiler under

Build Targets.

1.6 Pre- and Postbuild steps

CodeBlocks makes it possible to perform additional operations before or after compiling a

project. These operations are called Prebuilt or Postbuilt Steps. Typical Postbuilt Steps

are:

• Creating an Intel Hexformat from a finished object

Archiving a project can be another example for a Postbuilt Step. For this purpose, create

a Build Target ’Archive’ and include the following instruction in the Postbuilt Step: