Variable expansion - Revision history

Bluehazzard: Add $(PLATFORM) information

2019-07-18T21:53:49Z

Add $(PLATFORM) information

Bluehazzard: Add documentation for the expansion of common command line commands

2019-07-15T21:07:26Z

Add documentation for the expansion of common command line commands

LETARTARE: use in code

2018-03-11T15:33:40Z

use in code

Bluehazzard: Add a section about macro functions

2017-02-27T00:04:58Z

Add a section about macro functions

Bluehazzard: Restructure the paragraph

2017-02-26T23:54:14Z

Restructure the paragraph

Bluehazzard: Update some macro names, add === Standard path === and some other missing macro names

2016-06-14T10:49:17Z

Update some macro names, add === Standard path === and some other missing macro names

Alpha: Altered link to avoid redirect.

2011-09-24T14:40:40Z

Altered link to avoid redirect.

Ollydbg: /* Syntax */

2011-08-25T05:40:10Z

Syntax

Ollydbg: /* Syntax */ when searching key word "macro" will find this wiki page

2011-08-25T05:38:15Z

Syntax: when searching key word "macro" will find this wiki page

Mariocup: /* Files and directories */

2010-02-15T21:39:36Z

Files and directories

← Older revision		Revision as of 21:53, 18 July 2019
Line 160:		Line 160:
	:The number of the days passed since an arbitrarily chosen day zero (January 1, 2010). Useful as last component of a version/build number.		:The number of the days passed since an arbitrarily chosen day zero (January 1, 2010). Useful as last component of a version/build number.

		+	=== Platform dependence ===
		+	<code>$(PLATFORM)</code>
		+	: Expands to <code>msw</code> on windows and <code>unix</code> on linux and mac (Since revision r11793)

	=== Command line expansions ===		=== Command line expansions ===

@@ Line 159: / Line 159: @@
 <code>$(DAYCOUNT)</code>
 :The number of the days passed since an arbitrarily chosen day zero (January 1, 2010). Useful as last component of a version/build number.
 === Random values ===
@@ Line 205: / Line 227: @@
 <code>$TO_NATIVE_PATH{}</code>
 :convert to native path form the codeblocks instance is running on
 === Usage ===
@@ Line 213: / Line 234: @@
 </code>
 :returns the current target output file as unix path
 == Conditional Evaluation ==

← Older revision		Revision as of 15:33, 11 March 2018
Line 13:		Line 13:

	Variables which are neither global user variables nor builtin types are replaced with a value provided in the project file, or with an environment variable if the latter should fail.		Variables which are neither global user variables nor builtin types are replaced with a value provided in the project file, or with an environment variable if the latter should fail.
		+
		+	The use of these variables can follow the following example for the date :
		+
		+	<code>#include "include/manager.h"
		+
		+	wxString strdate = Manager::Get()->GetMacrosManager()->ReplaceMacros(_T("$TODAY"));</code>

	'''Per-target definitions have precedence over per-project definitions.'''		'''Per-target definitions have precedence over per-project definitions.'''

@@ Line 186: / Line 186: @@
 <code>$(GET_TEMP_DIR)</code>
 :ALL platforms: A writable, temporary directory
 == Conditional Evaluation ==

@@ Line 187: / Line 187: @@
 :ALL platforms: A writable, temporary directory
-=== Conditional Evaluation ===
+== Conditional Evaluation ==
 <code>$if(condition){true clause}{false clause}</code>
@@ Line 201: / Line 201: @@
 Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.
-=== Script expansion ===
+== Script expansion ==
 :For maximum flexibility, you can embed scripts using the <tt>[[</tt> <tt>]]</tt> operator as a special case of variable expansion. Embedded scripts have access to all standard functionality available to scrips and work pretty much like <tt>bash</tt> backticks (except for having access to Code::Blocks' namespace). As such, scripts are not limited to producing text output, but can also manipulate Code::Blocks state (projects, targets, etc.). Although this is technically possible, it is generally bad design and a very stupid idea to do so. Manipulating Code::Blocks state from a pre-build script is a much better solution.<br/>

@@ Line 33: / Line 33: @@
 === Files and directories ===
-<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code>
+<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code>, <code>$(PROJECTFILENAME)</code>, <code>$(PROJECT_FILE_NAME)</code>
 :The filename of the currently compiling project.
-<code>$(PROJECT_NAME)</code>
+<code>$(PROJECT_NAME)</code>, <code>$(PROJECTNAME)</code>
 :The name of the currently compiling project.
-<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code>
+<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code>, <code>$(PROJECTDIRECTORY)</code>
-:The common top-level directory of the currently compiling project.
+:The common directory of the currently compiling project.
 <code>$(ACTIVE_EDITOR_FILENAME)</code>
@@ Line 59: / Line 62: @@
 <code>$(ACTIVE_EDITOR_EXT)</code>
 :Currently active file's extension.
 <code>$(ALL_PROJECT_FILES)</code>
@@ Line 79: / Line 85: @@
 === Build targets ===
 <code>$(FOOBAR_OUTPUT_FILE)</code>
@@ Line 88: / Line 95: @@
 <code>$(FOOBAR_OUTPUT_BASENAME)</code>
 :A ''specific'' target's output file's base name (no path, no extension).
 <code>$(TARGET_OUTPUT_DIR)</code>
@@ Line 100: / Line 110: @@
 <code>$(TARGET_OUTPUT_FILE)</code>
 :The ''current'' target's output file.
 <code>$(TARGET_OUTPUT_BASENAME)</code>
@@ Line 106: / Line 119: @@
 <code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code>
 :The ''current'' target's build tool executable (compiler, linker, etc).
 === Language and encoding ===
@@ Line 136: / Line 152: @@
 <code>$(DAYCOUNT)</code>
-:The number of the days passed since an arbitrarily chosen day zero (January 1, 2009). Useful as last component of a version/build number.
+:The number of the days passed since an arbitrarily chosen day zero (January 1, 2010). Useful as last component of a version/build number.
 === Random values ===
@@ Line 145: / Line 161: @@
 <code>$(RANDOM)</code>
 :A 16bit positive random number (0-65535)
 === Conditional Evaluation ===

@@ Line 9: / Line 9: @@
 * <code>%VARIABLE%</code>
-Variable names must consist of alphanumeric characters and are not case-sensitive. Variables starting with a single hash sign (<code>#</code>) are interpreted as [[global user variables]].
+Variable names must consist of alphanumeric characters and are not case-sensitive. Variables starting with a single hash sign (<code>#</code>) are interpreted as [[global compiler variables]].
 The names listed below are interpreted as builtin types.

@@ Line 16: / Line 16: @@
 '''Per-target definitions have precedence over per-project definitions.'''
-Those buildin variables are much like pre-defined macros in C preprocessor as they will be text replaced when processed.
+Buildin variable expansion is much like pre-defined macro expansion in C preprocessor as it will be text replaced when processed.
 == List of available builtins ==

← Older revision		Revision as of 05:38, 25 August 2011
Line 15:		Line 15:

	'''Per-target definitions have precedence over per-project definitions.'''		'''Per-target definitions have precedence over per-project definitions.'''
		+
		+	Those buildin variables are much like pre-defined macros in C preprocessor as they will be text replaced when processed.

	== List of available builtins ==		== List of available builtins ==

@@ Line 42: / Line 42: @@
 <code>$(ACTIVE_EDITOR_FILENAME)</code>
 :The filename of the file opened in the currently active editor.
 <code>$(ACTIVE_EDITOR_DIRNAME)</code>