3 Variable Expansion

CodeBlocks

previous page next page

[Contents] CodeBlocks Manual [Search] Search

3 Variable Expansion

CodeBlocks differentiates between several types of variables. These types serve the purpose of configuring the environment for creating a program, and at the same of improving the maintainability and portability. Access to the CodeBlocks variables is achieved via $<name>.

Envrionment Variable

are set during the startup of CodeBlocks. They can modify system environment variables such as PATH. This can be useful in cases where a defined environment is necessary for the creation of projects. The settings for environment variables in CodeBlocks are made at ’Settings’ /’Environment’ /’Environment Variables’ .

Builtin Variables

are predefined in CodeBlocks, and can be accessed via their names (see section 3.2 for details).

Command Macros

This type of variables is used for controlling the build process. For further information please refer to section 3.4.

Custom Variables

are user-defined variables which can be specified in the build options of a project. Here you can, for example define your derivative as a variable MCU and assign a corresponding value to it. Then set the compiler option -mcpu=$(MCU), and CodeBlocks will automatically replace the content. By this method, the settings for a project can be further parametrised.

Global Variables

are mainly used for creating CodeBlocks from the sources or developments of wxWidgets applications. These variables have a very special meaning. In contrast to all others if you setup such a variables and share your project file with others that have *not* setup this GV CodeBlocks will ask the user to setup the variable. This is a very easy way to ensure the ’other developer’ knows what to setup easily. CodeBlocks will ask for all path’s usually necessary.

[Previous] 2.15 Symbol Table Plugin
[Next] 3.1 Syntax

previous page start next page