https://wiki.codeblocks.org/api.php?action=feedcontributions&feedformat=atom&user=Thomas
Code::Blocks - User contributions [en]
2026-05-10T23:59:56Z
User contributions
MediaWiki 1.35.0
https://wiki.codeblocks.org/index.php?title=Coding_style&diff=7441
Coding style
2012-11-11T16:42:19Z
<p>Thomas: </p>
<hr />
<div>[[Category:Developer Documentation]]<br />
The following are guidelines for the code formatting to use in Code::Blocks source code. Anyone writing code or a [[Creating a patch to submit to BerliOS (Patch Tracker)|patch]] for Code::Blocks, is required to follow these.<br />
<br />
== General coding style ==<br />
<br />
The general coding style is the ANSI one:<br />
<br />
Example:<br />
<pre><br />
namespace FooSpace<br />
{<br />
int Foo()<br />
{<br />
if (isBar)<br />
{<br />
Bar();<br />
return 1;<br />
}<br />
else<br />
return 0;<br />
}<br />
}<br />
</pre><br />
<br />
== Variables naming ==<br />
<br />
Class names do not start with 'C' (as in CObject, CWindow, etc). Only abstract base classes (interfaces) should start with 'I'.<br />
But they all have to start with a capital letter.<br />
<br />
Class member variables should start with <tt>m_</tt>. If the variable is a pointer, use <tt>m_p</tt> as a prefix.<br />
Following the prefix is the variable's name. Use descriptive names and use capital letters at the start of each word (the first too). So a fictious variable holding a value for position would be named as <tt>m_ValueForPosition</tt>.<br />
<br />
Non-class member variables should not start with a capital letter.<br />
<br />
Function names should always start with a capital letter.<br />
<br />
Examples:<br />
<pre>// Good<br />
int aLocalVar;<br />
int m_SomeInt;<br />
void* m_pSomePointer;<br />
bool SomeFunc();<br />
<br />
// Bad<br />
int SomeInt; // either no m_ prefix if it's a class variable, <br />
// or capital first letter if it's a local variable<br />
int m_someInt; // no capital letter 'S'<br />
void* m_SomePointer; // no m_p prefix<br />
bool someFunc(); // function with non-capital first letter<br />
</pre><br />
<br />
Parameters that are not absolutely required to be used in an interface or base class should preferrably be tagged with the <tt>cb_optional</tt> macro so users of the interface realize this, and as a side effect no compiler warnings are generated.<br />
<br />
Parameters that are ''actually not used'' should be tagged <tt>cb_unused</tt> both to suppress a compiler warning and indicate that this is happening intentionally.<br />
<br />
If the caller of a function takes ownership of the object referenced by the return value, tag the function as <tt>cb_must_consume_result</tt>.<br />
<br />
== Variables declaration ==<br />
<br />
One variable declared each time on a different line.<br />
For pointer/reference variables, the '*' or '&' is part of the type.<br />
<br />
Examples:<br />
<pre>// Good<br />
int& someInt;<br />
void* pPtr;<br />
<br />
// Bad<br />
int &someInt; // & not after type<br />
void* pPtr, pSomeOther; // multiple declarations in one line<br />
</pre><br />
<br />
== Spacing ==<br />
<br />
Prefer spaces over tabs. If you want to use tabs you won't be prosecuted (!) but please use a tab size of 4 spaces.<br><br />
Code indentation should be 4 spaces.<br><br />
In class declarations, the keywords <tt>public:</tt>, <tt>protected:</tt>, and <tt>private:</tt> should be indented. The same goes for all the class members.<br />
<br />
Examples:<br />
<pre><br />
// Good<br />
class AClass<br />
{<br />
public:<br />
AClass(){ ... }<br />
protected:<br />
int m_Member;<br />
};<br />
<br />
// Bad<br />
class AClass<br />
{<br />
public:<br />
AClass(){ ... }<br />
protected:<br />
int m_Member;<br />
};<br />
</pre><br />
<br />
== Commenting ==<br />
<br />
* All three types of comments are used in Code::Blocks. C++ style ('//'), C style ('/* */'), and the Doxygen style ('/** */').<br />
* The C++ style is used for just about everything. Use this style to describe what your code does.<br />
* The C style is used only for very long comments (paragraphs), or for a license or description at the top of a C++ file.<br />
* The Doxygen style is used for documenting functions only. These functions would be public, and protected class functions, and global helper functions.<br />
* Comments should clearly describe what the code does. Comments should be concise, but coherent.<br />
<br />
== Header file include and Precompiled header rule ==<br />
The NON-PCH compilation (I mean with NOPCH switch, that's different from simply disabling PCH!) will be helpful to detect missing includes. Keep in mind that no matter what we do - wx will do and use PCH unless we declare NOPCH at the compile time. So even if we disable our PCH, the patches won't stop unless we do it properly in the first place.<br />
<br />
The rules are plain simple:<br />
PCH file:<br />
- include all rarely changing header files<br />
- do the PCH macro vodoo (we have that already)<br />
Header:<br />
- If you access or define an object, include the header<br />
- If you use pointers/references, use forward decl<br />
- Put headers you need to include into such a section if they are part of your PCH file:<br />
Code:<br />
<br />
<source lang = "cpp"><br />
#ifndef USE_PCH<br />
#include <wx/dialog.h><br />
#endif<br />
</source><br />
<br />
- Include headers you need to include that are not part of your PCH file as normal<br />
Implementation:<br />
- include the PCH file first<br />
- same thing for headers needed as in the header file.<br />
<br />
I do it that way in my own projects and i works flawlessly for ages! Of course, whenever I change code and use new classes, I need to check the above rules.<br />
<br />
But (nevermind) if we decide to get rid of this because these rules are too hard - go ahead.<br />
<br />
Here comes a simple small class:<br />
Header:<br />
<br />
<source lang = "cpp"><br />
<br />
#ifndef USE_PCH<br />
#include <wx/dialog.h> // is in wx_pch.h!<br />
#endif<br />
<br />
#include <wx/busyinfo.h> // NOT in wx_pch.h and used as object<br />
<br />
class MyClass; // forward decsl due to pointer usage<br />
<br />
class MyDlg: public wxDialog<br />
{<br />
MyDlg() { ; };<br />
void Func(MyClass* c); // used as pointer<br />
wxBusyInfo bi; // used as object<br />
}<br />
</source><br />
Implementation:<br />
<br />
<source lang = "cpp"><br />
<br />
#include <wx_pch.h> // our PCH file, may include the WX PCH file (if needed)<br />
<br />
#include "MyDlg.h"<br />
<br />
#ifndef USE_PCH<br />
#include "MyClass.h" // is in wx_pch.h, but now used as object / accessed<br />
#endif<br />
<br />
#include "MyOhterClass.h" // NOT in wx_pch.h and used as object<br />
<br />
void MyDlg::Func(MyClass* c)<br />
{<br />
MyOtherClass moc;<br />
c->DoSomething(moc);<br />
}<br />
</source><br />
See some disscussion in our forum: [/index.php/topic,16028.msg108172.html#msg108172 Morten's comments on include file rules]<br />
<br />
Also: [/index.php/topic,3321.msg26184.html#msg26184 include rules (by killerbot)]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=5824
Variable expansion
2009-02-20T19:15:28Z
<p>Thomas: /* Time and date */</p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Code::Blocks workspace ===<br />
<br />
<code>$(WORKSPACE_FILENAME)</code>, <code>$(WORKSPACE_FILE_NAME)</code>, <code>$(WORKSPACEFILE)</code>, <code>$(WORKSPACEFILENAME)</code><br />
:The filename of the current workspace project (.workspace).<br />
<br />
<code>$(WORKSPACENAME)</code>, <code>$(WORKSPACE_NAME)</code><br />
:The name of the workspace that is displayed in the tab Projects of the Management panel.<br />
<br />
<code>$(WORKSPACE_DIR)</code>, <code>$(WORKSPACE_DIRECTORY)</code>, <code>$(WORKSPACEDIR)</code>, <code>$(WORKSPACEDIRECTORY)</code><br />
:The location of the workspace directory.<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_OBJECT_DIR)</code><br />
:The ''current'' target's object directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
<code>$(DAYCOUNT)</code><br />
:The number of the days passed since an arbitrarily chosen day zero (January 1, 2009). Useful as last component of a version/build number.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.<br />
<br />
=== Script expansion ===<br />
<br />
: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/><br />
<br />
:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.<br />
<br />
:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.<br />
<br />
:<u>Example:</u><br/><br />
:<tt><nowiki>[[ print(GetProjectManager().GetActiveProject().GetTitle()); ]]</nowiki></tt><br/><br />
:inserts the active project's title into the command line.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4310
Variable expansion
2006-12-08T08:51:08Z
<p>Thomas: /* Script expansion */</p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_OBJECT_DIR)</code><br />
:The ''current'' target's object directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.<br />
<br />
=== Script expansion ===<br />
<br />
: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/><br />
<br />
:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.<br />
<br />
:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.<br />
<br />
:<u>Example:</u><br/><br />
:<tt><nowiki>[[ print(GetProjectManager().GetActiveProject().GetTitle()); ]]</nowiki></tt><br/><br />
:inserts the active project's title into the command line.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4309
Variable expansion
2006-12-08T08:46:46Z
<p>Thomas: /* Script expansion */</p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_OBJECT_DIR)</code><br />
:The ''current'' target's object directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.<br />
<br />
=== Script expansion ===<br />
<br />
: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/><br />
<br />
:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.<br />
<br />
:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.<br />
<br />
:<u>Example:</u><br/><br />
:<tt>[[ print(GetProjectManager().GetActiveProject().GetTitle()); ]]</tt><br/><br />
:inserts the active project's title into the command line.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4308
Variable expansion
2006-12-08T08:38:39Z
<p>Thomas: /* Script expansion */</p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_OBJECT_DIR)</code><br />
:The ''current'' target's object directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.<br />
<br />
=== Script expansion ===<br />
<br />
: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/><br />
<br />
:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.<br />
<br />
:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.<br />
<br />
:<u>Example:</u> adding <tt>[[ local p=GetProjectManager().GetActiveProject(); print(p.GetTitle()); ]]</tt> to compiler options inserts the active project's title into the command line.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4259
Variable expansion
2006-12-04T11:54:11Z
<p>Thomas: /* Build targets */</p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_OBJECT_DIR)</code><br />
:The ''current'' target's object directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.<br />
<br />
=== Script expansion ===<br />
<br />
: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/><br />
<br />
:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.<br />
<br />
:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.<br />
<br />
:<u>Example:</u> adding <tt>[[ print(5+3); ]]</tt> to compiler options inserts <tt>8</tt></div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4237
Variable expansion
2006-11-29T14:31:19Z
<p>Thomas: </p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.<br />
<br />
=== Script expansion ===<br />
<br />
: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/><br />
<br />
:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.<br />
<br />
:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.<br />
<br />
:<u>Example:</u> adding <tt>[[ print(5+3); ]]</tt> to compiler options inserts <tt>8</tt></div>
Thomas
https://wiki.codeblocks.org/index.php?title=Scripting_Code::Blocks&diff=4236
Scripting Code::Blocks
2006-11-29T14:14:25Z
<p>Thomas: </p>
<hr />
<div>[[Category:Developer Documentation]]<br />
[[Category:Scripting Code::Blocks]]<br />
Code::Blocks supports '''scripting''' to extend various parts of its functionality during runtime. The scripting language used is [http://www.squirrel-lang.org Squirrel].<br />
<br />
Currently, Code::Blocks uses scripts for:<br />
<br />
'''[[Startup script|Startup]]'''<br />
: Run arbitrary commands on application startup.<br />
<br />
'''[[Wizard scripts|Wizards]]'''<br />
: Register new wizards for generating projects, build targets, files or anything else. All wizards shipped with Code::Blocks are scripted.<br />
<br />
'''[[Debugger scripts|Debugger]]'''<br />
: 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.<br />
<br />
'''[[Build scripts|Build]]'''<br />
: 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/><br />
<br />
'''[[Variable expansion]]'''<br />
:As a special case of [[variable expansion]], scripts can be run in place of a variable, expanding to the output generated by the script. <br />
<br />
<br />
More Code::Blocks parts may be exposed to scripting in the future.<br />
<br />
== See also ==<br />
* [[Scripting commands]]<br />
<br />
== External links ==<br />
* [http://www.squirrel-lang.org/#doc Squirrel documentation]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Builtin_variables&diff=4235
Builtin variables
2006-11-29T14:10:39Z
<p>Thomas: Builtin variables moved to Variable expansion</p>
<hr />
<div>#REDIRECT [[Variable expansion]]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4234
Variable expansion
2006-11-29T14:10:38Z
<p>Thomas: Builtin variables moved to Variable expansion</p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.<br />
<br />
=== Path manipulation ===<br />
<br />
<s><code>$relative(path), $absolute(path)</code><br />
:Replaces the argument <tt>path</tt> (which may be a variable) with its normalised absolute path/filename equivalent or with a path relative to the project directory, respectively.<br />
<br />
:Keep in mind that functions <tt>$relative()</tt> and <tt>$absolute()</tt> are considerably more computionally expensive than any other builtin variable or function. Thus, if performance matters, do not use them "just for good", but only when you really need them. Also, please note that neither the variable syntax variants <tt>%relative(...)</tt> nor <tt>$(relative)(...)</tt> are supported for this construct.</s></div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4233
Variable expansion
2006-11-29T12:34:00Z
<p>Thomas: /* Path manipulation */</p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.<br />
<br />
=== Path manipulation ===<br />
<br />
<s><code>$relative(path), $absolute(path)</code><br />
:Replaces the argument <tt>path</tt> (which may be a variable) with its normalised absolute path/filename equivalent or with a path relative to the project directory, respectively.<br />
<br />
:Keep in mind that functions <tt>$relative()</tt> and <tt>$absolute()</tt> are considerably more computionally expensive than any other builtin variable or function. Thus, if performance matters, do not use them "just for good", but only when you really need them. Also, please note that neither the variable syntax variants <tt>%relative(...)</tt> nor <tt>$(relative)(...)</tt> are supported for this construct.</s></div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4206
Variable expansion
2006-11-27T17:06:54Z
<p>Thomas: </p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.<br />
<br />
=== Path manipulation ===<br />
<br />
<code>$relative(path), $absolute(path)</code><br />
:Replaces the argument <tt>path</tt> (which may be a variable) with its normalised absolute path/filename equivalent or with a path relative to the project directory, respectively.<br />
<br />
:Keep in mind that functions <tt>$relative()</tt> and <tt>$absolute()</tt> are considerably more computionally expensive than any other builtin variable or function. Thus, if performance matters, do not use them "just for good", but only when you really need them. Also, please note that neither the variable syntax variants <tt>%relative(...)</tt> nor <tt>$(relative)(...)</tt> are supported for this construct.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4205
Variable expansion
2006-11-27T14:11:40Z
<p>Thomas: /* Build targets */</p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code><br />
:The ''current'' target's build tool executable (compiler, linker, etc).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4204
Variable expansion
2006-11-27T12:54:10Z
<p>Thomas: /* Conditional Evaluation */</p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=4203
Variable expansion
2006-11-27T12:53:05Z
<p>Thomas: </p>
<hr />
<div>[[Category:User Documentation]]<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
* <code>$VARIABLE</code><br />
* <code>$(VARIABLE)</code><br />
* <code>${VARIABLE}</code><br />
* <code>%VARIABLE%</code><br />
<br />
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]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
<br />
'''Per-target definitions have precedence over per-project definitions.'''<br />
<br />
== List of available builtins ==<br />
<br />
=== Files and directories ===<br />
<br />
<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code><br />
:The filename of the currently compiling project.<br />
<br />
<code>$(PROJECT_NAME)</code><br />
:The name of the currently compiling project.<br />
<br />
<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code><br />
:The common top-level directory of the currently compiling project.<br />
<br />
<code>$(ACTIVE_EDITOR_FILENAME)</code><br />
:The filename of the file opened in the currently active editor.<br />
<br />
<code>$(ACTIVE_EDITOR_DIRNAME)</code><br />
:Currently active file's containing directory (relative to the common top level path)<br />
<br />
<code>$(ACTIVE_EDITOR_STEM)</code><br />
:Currently active file's base name (without extension).<br />
<br />
<code>$(ACTIVE_EDITOR_EXT)</code><br />
:Currently active file's extension.<br />
<br />
<code>$(ALL_PROJECT_FILES)</code><br />
:A string containing the names of all files in the current project.<br />
<br />
<code>$(MAKEFILE)</code><br />
:The filename of the makefile.<br />
<br />
<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code><br />
:The path to the currently running instance of Code::Blocks<br />
<br />
<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code><br />
:The 'shared' directory of the currently running instance of Code::Blocks<br />
<br />
<code>$(PLUGINS)</code><br />
:The 'plugins' directory of the currently running instance of Code::Blocks<br />
<br />
=== Build targets ===<br />
<br />
<code>$(FOOBAR_OUTPUT_FILE)</code><br />
:A ''specific'' target's output file.<br />
<br />
<code>$(FOOBAR_OUTPUT_DIR)</code><br />
:A ''specific'' target's output directory.<br />
<br />
<code>$(FOOBAR_OUTPUT_BASENAME)</code><br />
:A ''specific'' target's output file's base name (no path, no extension).<br />
<br />
<code>$(TARGET_OUTPUT_DIR)</code><br />
:The ''current'' target's output directory.<br />
<br />
<code>$(TARGET_NAME)</code><br />
:The ''current'' target's name.<br />
<br />
<code>$(TARGET_OUTPUT_FILE)</code><br />
:The ''current'' target's output file.<br />
<br />
<code>$(TARGET_OUTPUT_BASENAME)</code><br />
:The ''current'' target's output file's base name (no path, no extension).<br />
<br />
=== Language and encoding ===<br />
<br />
<code>$(LANGUAGE)</code><br />
:The system language in human readable form.<br />
<br />
<code>$(ENCODING)</code><br />
:The character encoding in human readable form.<br />
<br />
=== Time and date ===<br />
<br />
<code>$(TDAY)</code><br />
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)<br />
<br />
<code>$(TODAY)</code><br />
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)<br />
<br />
<code>$(NOW)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)<br />
<br />
<code>$(NOW_L)</code><br />
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)<br />
<br />
<code>$(WEEKDAY)</code><br />
:Human-readable day of the week (for example "Wednesday")<br />
<br />
<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code><br />
:These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
=== Random values ===<br />
<br />
<code>$(COIN)</code><br />
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<code>$(RANDOM)</code><br />
:A 16bit positive random number (0-65535)<br />
<br />
=== Conditional Evaluation ===<br />
<br />
<code>$if(condition){true clause}{false clause}</code><br />
:Conditional evaluation will resolve to its <tt>true clause</tt> if<br />
::<tt>condition</tt> is a non-empty character sequence<br />
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)<br />
:Conditional evaluation will resolve to its <tt>false clause</tt> if<br />
::<tt>condition</tt> is empty<br />
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt><br />
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt><br />
<br />
Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Keyboard_Shortcuts&diff=4082
Keyboard Shortcuts
2006-11-03T20:36:06Z
<p>Thomas: </p>
<hr />
<div>[[Category:Code::Blocks Documentation]]<br />
<br />
::''Note: You can define your own keyboard shortcuts with the [[Keyboard Shortcuts plugin]]''<br />
<br />
== Editor ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"<br />
<br />
|- style="background: #ececec; border: 1px solid gray"<br />
!Function <br />
!Shortcut Key<br />
|-<br />
<br />
|-<br />
| Undo last action || Ctrl + Z<br />
|-<br />
<br />
|-<br />
| Redo last action || Ctrl + Shift + Z<br />
|-<br />
<br />
|-<br />
| Cut selected text || Ctrl + X<br />
|-<br />
<br />
|-<br />
| Copy selected text || Ctrl + C<br />
|-<br />
<br />
|-<br />
| Paste text from clipboard || Ctrl + V<br />
|-<br />
<br />
|-<br />
| Select all text || Ctrl + A<br />
|-<br />
<br />
|-<br />
| Swap header / source || F11<br />
|-<br />
<br />
|-<br />
| Comment highlighted code || Ctrl + Shift + C<br />
|-<br />
<br />
|-<br />
| Uncomment highlighted code || Ctrl + Shift + X<br />
|-<br />
<br />
|-<br />
| Duplicate line caret is on || Ctrl + D<br />
|-<br />
<br />
|-<br />
| Auto-complete / Abbreviations || Ctrl + Space / Ctrl + J<br />
|-<br />
<br />
|-<br />
| Show call tip || Ctrl + Shift + Space<br />
|-<br />
<br />
<br />
|-<br />
| Swap line caret is on with line above it || Ctrl + T<br />
|-<br />
<br />
|-<br />
| Toggle bookmark || Ctrl + B<br />
|-<br />
<br />
|-<br />
| Goto previous bookmark || Alt + PgUp<br />
|-<br />
<br />
|-<br />
| Goto next bookmark || Alt + PgDown<br />
|-<br />
<br />
|-<br />
| Toggle current block folding || F12<br />
|-<br />
<br />
|-<br />
| Toggle all folds || Shift + F12<br />
|-<br />
<br />
|}<br />
<br />
<br />
This is a list of shortcuts provided by the Code::Blocks' editor component. These shortcuts cannot be rebound.<br />
<br />
{| border="1" cellpadding="3" cellspacing="0" style="1px solid gray; border-collapse: collapse;"<br />
<br />
|- style="background: #ececec; border: 1px solid gray"<br />
!Function <br />
!Shortcut Key<br />
|-<br />
<br />
|-<br />
| Magnify text size. || Ctrl + Keypad "+"<br />
|-<br />
<br />
|-<br />
| Reduce text size. || Ctrl + Keypad "-"<br />
|-<br />
<br />
|-<br />
| Restore text size to normal. || Ctrl + Keypad "/"<br />
|-<br />
<br />
|-<br />
| Cycle through recent files. || Ctrl + Tab<br />
|-<br />
<br />
|-<br />
| Indent block. || Tab<br />
|-<br />
<br />
|-<br />
| Dedent block. || Shift + Tab<br />
|-<br />
<br />
|-<br />
| Delete to start of word. || Ctrl + BackSpace<br />
|-<br />
<br />
|-<br />
| Delete to end of word. || Ctrl + Delete<br />
|-<br />
<br />
|-<br />
| Delete to start of line. || Ctrl + Shift + BackSpace<br />
|-<br />
<br />
|-<br />
| Delete to end of line. || Ctrl + Shift + Delete<br />
|-<br />
<br />
|-<br />
| Go to start of document. || Ctrl + Home<br />
|-<br />
<br />
|-<br />
| Extend selection to start of document. || Ctrl + Shift + Home<br />
|-<br />
<br />
|-<br />
| Go to start of display line. || Alt + Home<br />
|-<br />
<br />
|-<br />
| Extend selection to start of display line. || Alt + Shift + Home<br />
|-<br />
<br />
|-<br />
| Go to end of document. || Ctrl + End<br />
|-<br />
<br />
|-<br />
| Extend selection to end of document. || Ctrl + Shift + End<br />
|-<br />
<br />
|-<br />
| Go to end of display line. || Alt + End<br />
|-<br />
<br />
|-<br />
| Extend selection to end of display line. || Alt + Shift + End<br />
|-<br />
<br />
|-<br />
| Expand or contract a fold point. || Ctrl + Keypad "*"<br />
|-<br />
<br />
|-<br />
| Create or delete a bookmark. || Ctrl + F2<br />
|-<br />
<br />
|-<br />
| Go to next bookmark. || F2<br />
|-<br />
<br />
|-<br />
| Select to next bookmark. || Alt + F2<br />
|-<br />
<br />
|-<br />
| Find selection. || Ctrl + F3<br />
|-<br />
<br />
|-<br />
| Find selection backwards. || Ctrl + Shift + F3<br />
|-<br />
<br />
|-<br />
| Scroll up. || Ctrl + Up<br />
|-<br />
<br />
|-<br />
| Scroll down. || Ctrl + Down<br />
|-<br />
<br />
|-<br />
| Line cut. || Ctrl + L<br />
|-<br />
<br />
|-<br />
| Line copy. || Ctrl + Shift + T<br />
|-<br />
<br />
|-<br />
| Line delete. || Ctrl + Shift + L<br />
|-<br />
<br />
|-<br />
| Line transpose with previous. || Ctrl + T<br />
|-<br />
<br />
|-<br />
| Line duplicate. || Ctrl + D<br />
|-<br />
<br />
|-<br />
| Find matching preprocessor conditional, skipping nested ones. || Ctrl + K<br />
|-<br />
<br />
|-<br />
| Select to matching preprocessor conditional. || Ctrl + Shift + K<br />
|-<br />
<br />
|-<br />
| Find matching preprocessor conditional backwards, skipping nested ones. || Ctrl + J<br />
|-<br />
<br />
|-<br />
| Select to matching preprocessor conditional backwards. || Ctrl + Shift + J<br />
|-<br />
<br />
|-<br />
| Previous paragraph. Shift extends selection. || Ctrl + [<br />
|-<br />
<br />
|-<br />
| Next paragraph. Shift extends selection. || Ctrl + ]<br />
|-<br />
<br />
|-<br />
| Previous word. Shift extends selection. || Ctrl + Left<br />
|-<br />
<br />
|-<br />
| Next word. Shift extends selection. || Ctrl + Right<br />
|-<br />
<br />
|-<br />
| Previous word part. Shift extends selection. || Ctrl + /<br />
|-<br />
<br />
|-<br />
| Next word part. Shift extends selection. || Ctrl + \<br />
|-<br />
<br />
|}<br />
<br />
== Files ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"<br />
<br />
|- style="background: #ececec; border: 1px solid gray"<br />
!Function <br />
!Shortcut Key<br />
|-<br />
<br />
|-<br />
| New file or project || Ctrl + N<br />
|-<br />
<br />
|-<br />
| Open existing file or project || Ctrl + O<br />
|-<br />
<br />
|-<br />
| Save current file || Ctrl + S<br />
|-<br />
<br />
|-<br />
| Save all files || Ctrl + Shift + S<br />
|-<br />
<br />
|-<br />
| Close current file || Ctrl + F4 / Ctrl + W<br />
|-<br />
<br />
|-<br />
| Close all files || Ctrl + Shift + F4 / Ctrl + Shift + W<br />
|-<br />
<br />
|}<br />
<br />
<br />
This is a list of shortcuts provided by the Code::Blocks' tab component. These shortcuts cannot be rebound.<br />
<br />
{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"<br />
<br />
|- style="background: #ececec; border: 1px solid gray"<br />
!Function <br />
!Shortcut Key<br />
|-<br />
<br />
|-<br />
| Activate next open file || Ctrl + Tab<br />
|-<br />
<br />
|-<br />
| Activate previous open file || Ctrl + Shift + Tab<br />
|-<br />
<br />
|}<br />
<br />
<br />
== View ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"<br />
<br />
|- style="background: #ececec; border: 1px solid gray"<br />
!Function <br />
!Shortcut Key<br />
|-<br />
<br />
|-<br />
| Show / hide Messages pane || F2<br />
|-<br />
<br />
|-<br />
| Show / hide Management pane || Shift + F2<br />
|-<br />
<br />
|-<br />
| Move project up (in Project tree) || Ctrl + Shift + Up<br />
|-<br />
<br />
|-<br />
| Move project down (in Project tree) || Ctrl + Shift + Down<br />
|-<br />
<br />
|-<br />
| Activate prior (in Project tree) || Alt + F5<br />
|-<br />
<br />
|-<br />
| Activate next (in Project tree) || Alt + F6<br />
|-<br />
<br />
|-<br />
| Zoom in / out || Ctrl + Roll Mouse Wheel<br />
|-<br />
<br />
|-<br />
| Focus editor || CTRL + Alt + E<br />
|-<br />
<br />
|}<br />
<br />
<br />
== Search ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"<br />
<br />
|- style="background: #ececec; border: 1px solid gray"<br />
!Function <br />
!Shortcut Key<br />
|-<br />
<br />
|-<br />
| Find || Ctrl + F<br />
|-<br />
<br />
|-<br />
| Find next || F3<br />
|-<br />
<br />
|-<br />
| Find previous || Shift + F3<br />
|-<br />
<br />
|-<br />
| Find in files || Crtl + Shift + F<br />
|-<br />
<br />
|-<br />
| Replace || Ctrl + R<br />
|-<br />
<br />
|-<br />
| Replace in files || Ctrl + Shift + R<br />
|-<br />
<br />
|-<br />
| Goto line || Ctrl + G<br />
|-<br />
<br />
|-<br />
| Goto file || Alt + G<br />
|-<br />
<br />
|-<br />
| Goto function || Ctrl + Alt + G<br />
|-<br />
<br />
|}<br />
<br />
<br />
== Build ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"<br />
<br />
|- style="background: #ececec; border: 1px solid gray"<br />
!Function <br />
!Shortcut Key<br />
|-<br />
<br />
|-<br />
| Build || Ctrl + F9<br />
|-<br />
<br />
|-<br />
| Compile current file || Ctrl + Shift + F9<br />
|-<br />
<br />
|-<br />
| Run || Ctrl + F10<br />
|-<br />
<br />
|-<br />
| Build and Run || F9<br />
|-<br />
<br />
|-<br />
| Rebuild || Ctrl + F11<br />
|-<br />
<br />
|}<br />
<br />
<br />
== Debug ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"<br />
<br />
|- style="background: #ececec; border: 1px solid gray"<br />
!Function <br />
!Shortcut Key<br />
|-<br />
<br />
|-<br />
| Debug || F8<br />
|-<br />
<br />
|-<br />
| Continue debugging || Ctrl + F7<br />
|-<br />
<br />
|-<br />
| Step over a code block || F7<br />
|-<br />
<br />
|-<br />
| Step into a code block || Shift + F7<br />
|-<br />
<br />
|-<br />
| Step out of a code block || Ctrl + Shift + F7<br />
|-<br />
<br />
|-<br />
| Toggle breakpoint || F5<br />
|-<br />
<br />
|-<br />
| Run to cursor || F4<br />
|-<br />
<br />
|-<br />
| Previous error || Alt + F1<br />
|-<br />
<br />
|-<br />
| Next error || Alt + F2<br />
|-<br />
<br />
|}</div>
Thomas
https://wiki.codeblocks.org/index.php?title=MinGW_installation&diff=3903
MinGW installation
2006-10-07T13:32:57Z
<p>Thomas: /* Other developer tools */</p>
<hr />
<div>[[Category:User Documentation]]<br />
==Using the MinGW installer==<br />
Note: At the present time, it is still preferrable to download the packages by hand, as the installers are not production quality (unless you really feel unsure unpacking a couple of archives).<br />
<br />
Also, the installer reportedly does not work on Windows Vista, follow the [[MinGW_installation#GCC_3.4.5_manual_install | manual installation instructions]].<br /><br />
(In general, MinGW is not confirmed to work for any Windows Vista betas or RCs)<br />
<br />
MinGW Installer 5.02 allows to choose the SF mirror while 5.03 does not (automatically picks one randomly).<br />
Either installer allows to downloads/installs "previous", "current" and "candidate" mingw packages.<br />
<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.2.exe MinGW Installer 5.0.2]<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.3.exe MinGW Installer 5.0.3]<br />
<br />
'''Note that the MinGW version number is not related to the actual compiler version.'''<br />
<br />
Please do note that the installer applications require an internet connection and will download the actual MinGW packages at the time of installation.<br />
<br />
==GCC 3.4.5 manual install==<br />
This is the "candidate" release of MinGW, so it is not considered "stable" officially.<br />Personally, I have not had any kind of problem with this release.<br />
<br />
To do a manual install, simply download the desired files and extract them all into the same directory. If you have WinZip, PowerArchiver, or any other similar program, this is as easy as selecting all the archives simultaneously and choosing "unpack here" from the context menu.<br />
<br />
For clarity, I recommend to put MinGW into C:\MinGW, but almost any other locations should do equally well. Avoid pathnames with spaces or exotic characters, as this may confuse some commandline tools (most notably <tt>gdb</tt>).<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download]<br />
<br />
===Optionally:===<br />
====Fortran77 compiler====<br />
*[http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz?download http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz?download]<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Other developer tools====<br />
=====UnxUtils=====<br />
Ports of the most often used Unix utilities. Note that some tools in UnxUtils are quite a bit outdated, so make sure you <u>do not</u> overwrite already existing MinGW files with their UnxUtils counterparts.<br />
*[http://unxutils.sourceforge.net/UnxUtils.zip UnxUtils]<br />
*[http://unxutils.sourceforge.net/UnxUpdates.zip UnxUtils-Latest-Updates]<br />
<br />
=====GnuWin32=====<br />
''More recent'' versions of commonly used Unix utilities. Also: utilities not found in UnxUtils at all.<br />
*[http://prdownloads.sourceforge.net/gnuwin32/coreutils-5.3.0-bin.zip?download coreutils-5.3.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/zip-2.3-3-bin.zip zip-2.3.3]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/tar-1.13-1-bin.zip?download tar-1.13-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gzip-1.3.5-3-bin.zip?download gzip-1.3.5]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bzip2-1.0.3-1-bin.zip?download bzip2-1.0.0-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/autoconf-2.59-bin.zip?download autoconf-2.59]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/automake-1.9.4-bin.zip?download automake-1.9.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bison-2.1-bin.zip?download bison-2.1 (includes m4)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/flex-2.5.4a-1-bin.zip?download flex-2.5.4a]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gperf-3.0.1-bin.zip?download gperf-3.0.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/diffutils-2.8.7-1-bin.zip?download diffutils-2.8.7]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/patch-2.5.9-6-bin.zip?download patch-2.5.9-6]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/grep-2.5.1a-bin.zip?download grep-2.5.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/sed-4.1.4-bin.zip?download sed-4.1.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/hextools-1.0-bin.zip?download hextools-1.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/findutils-4.2.20-2-bin.zip?download findutils-4.2.20]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/less-394-bin.zip?download less 3.94]<br />
*[http://prdownloads.sourceforge.net/mingw/wget-1.9.1-mingwPORT.tar.bz2?download wget-1.9.1]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip gettext-0.14.5]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-dev-0.14.5.zip gettext-dev-0.14.5]<br />
<br />
Dependencies:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/pcre-6.4-1-bin.zip?download pcre-6.4.1 (needed by grep and less)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libintl-0.14.4-bin.zip?download libintl-0.14.4 (needed by most tools)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libiconv-1.9.2-1-bin.zip?download libiconv-1.9.2-1 (needed by most tools)]<br />
<br />
==Resulting Folder Layout==<br />
[[Image:Lay.png]]<br />
<br />
<br />
==GCC 3.4.4 manual install==<br />
Some people have reported various problems with gcc version 3.4.4, so it may be worth a consideration to use the either the 3.4.5 or 3.4.2 releases until a build from the 4.x branch is available.<br />Personally, I have not had any kind of problem with either 3.4.4 or 3.4.5.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download]<br />
<br />
<br />
==GCC 3.4.2 manual install==<br />
Installing MinGW can be quite intimidating the first time because it is not obvious what you have to do. Luckily, it is actually pretty simple.<br /><br />
To do a manual install, simply download the required files and extract them all into the same directory. For simplicity, I recommend <tt>C:\MinGW</tt>.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download]<br />
====Fortran77 compiler====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download]<br />
<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=MinGW_installation&diff=3902
MinGW installation
2006-10-07T13:21:23Z
<p>Thomas: /* Other developer tools */</p>
<hr />
<div>[[Category:User Documentation]]<br />
==Using the MinGW installer==<br />
Note: At the present time, it is still preferrable to download the packages by hand, as the installers are not production quality (unless you really feel unsure unpacking a couple of archives).<br />
<br />
Also, the installer reportedly does not work on Windows Vista, follow the [[MinGW_installation#GCC_3.4.5_manual_install | manual installation instructions]].<br /><br />
(In general, MinGW is not confirmed to work for any Windows Vista betas or RCs)<br />
<br />
MinGW Installer 5.02 allows to choose the SF mirror while 5.03 does not (automatically picks one randomly).<br />
Either installer allows to downloads/installs "previous", "current" and "candidate" mingw packages.<br />
<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.2.exe MinGW Installer 5.0.2]<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.3.exe MinGW Installer 5.0.3]<br />
<br />
'''Note that the MinGW version number is not related to the actual compiler version.'''<br />
<br />
Please do note that the installer applications require an internet connection and will download the actual MinGW packages at the time of installation.<br />
<br />
==GCC 3.4.5 manual install==<br />
This is the "candidate" release of MinGW, so it is not considered "stable" officially.<br />Personally, I have not had any kind of problem with this release.<br />
<br />
To do a manual install, simply download the desired files and extract them all into the same directory. If you have WinZip, PowerArchiver, or any other similar program, this is as easy as selecting all the archives simultaneously and choosing "unpack here" from the context menu.<br />
<br />
For clarity, I recommend to put MinGW into C:\MinGW, but almost any other locations should do equally well. Avoid pathnames with spaces or exotic characters, as this may confuse some commandline tools (most notably <tt>gdb</tt>).<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download]<br />
<br />
===Optionally:===<br />
====Fortran77 compiler====<br />
*[http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz?download http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz?download]<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Other developer tools====<br />
Ports of the most often used Unix utilities. Note that some tools in UnxUtils are quite a bit outdated, so make sure you <u>do not</u> overwrite already existing MinGW files with their UnxUtils counterparts:<br />
*[http://unxutils.sourceforge.net/UnxUtils.zip UnxUtils]<br />
*[http://unxutils.sourceforge.net/UnxUpdates.zip UnxUtils-Latest-Updates]<br />
<br />
<br />
More recent versions of commonly used utilities and utilities not found in UnxUtils:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/coreutils-5.3.0-bin.zip?download coreutils-5.3.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/zip-2.3-3-bin.zip zip-2.3.3]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/tar-1.13-1-bin.zip?download tar-1.13-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gzip-1.3.5-3-bin.zip?download gzip-1.3.5]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bzip2-1.0.3-1-bin.zip?download bzip2-1.0.0-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/autoconf-2.59-bin.zip?download autoconf-2.59]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/automake-1.9.4-bin.zip?download automake-1.9.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bison-2.1-bin.zip?download bison-2.1 (includes m4)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/flex-2.5.4a-1-bin.zip?download flex-2.5.4a]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gperf-3.0.1-bin.zip?download gperf-3.0.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/diffutils-2.8.7-1-bin.zip?download diffutils-2.8.7]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/patch-2.5.9-6-bin.zip?download patch-2.5.9-6]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/grep-2.5.1a-bin.zip?download grep-2.5.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/sed-4.1.4-bin.zip?download sed-4.1.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/hextools-1.0-bin.zip?download hextools-1.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/findutils-4.2.20-2-bin.zip?download findutils-4.2.20]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/less-394-bin.zip?download less 3.94]<br />
*[http://prdownloads.sourceforge.net/mingw/wget-1.9.1-mingwPORT.tar.bz2?download wget-1.9.1]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip gettext-0.14.5]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-dev-0.14.5.zip gettext-dev-0.14.5]<br />
<br />
Dependencies:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/pcre-6.4-1-bin.zip?download pcre-6.4.1 (needed by grep and less)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libintl-0.14.4-bin.zip?download libintl-0.14.4 (needed by most tools)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libiconv-1.9.2-1-bin.zip?download libiconv-1.9.2-1 (needed by most tools)]<br />
<br />
==Resulting Folder Layout==<br />
[[Image:Lay.png]]<br />
<br />
<br />
==GCC 3.4.4 manual install==<br />
Some people have reported various problems with gcc version 3.4.4, so it may be worth a consideration to use the either the 3.4.5 or 3.4.2 releases until a build from the 4.x branch is available.<br />Personally, I have not had any kind of problem with either 3.4.4 or 3.4.5.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download]<br />
<br />
<br />
==GCC 3.4.2 manual install==<br />
Installing MinGW can be quite intimidating the first time because it is not obvious what you have to do. Luckily, it is actually pretty simple.<br /><br />
To do a manual install, simply download the required files and extract them all into the same directory. For simplicity, I recommend <tt>C:\MinGW</tt>.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download]<br />
====Fortran77 compiler====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download]<br />
<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=MinGW_installation&diff=3899
MinGW installation
2006-10-05T09:02:07Z
<p>Thomas: /* GCC 3.4.5 manual install */</p>
<hr />
<div>[[Category:User Documentation]]<br />
==Using the MinGW installer==<br />
Note: At the present time, it is still preferrable to download the packages by hand, as the installers are not production quality (unless you really feel unsure unpacking a couple of archives).<br />
<br />
Also, the installer reportedly does not work on Windows Vista, follow the [[MinGW_installation#GCC_3.4.5_manual_install | manual installation instructions]].<br /><br />
(In general, MinGW is not confirmed to work for any Windows Vista betas or RCs)<br />
<br />
MinGW Installer 5.02 allows to choose the SF mirror while 5.03 does not (automatically picks one randomly).<br />
Either installer allows to downloads/installs "previous", "current" and "candidate" mingw packages.<br />
<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.2.exe MinGW Installer 5.0.2]<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.3.exe MinGW Installer 5.0.3]<br />
<br />
'''Note that the MinGW version number is not related to the actual compiler version.'''<br />
<br />
Please do note that the installer applications require an internet connection and will download the actual MinGW packages at the time of installation.<br />
<br />
==GCC 3.4.5 manual install==<br />
This is the "candidate" release of MinGW, so it is not considered "stable" officially.<br />Personally, I have not had any kind of problem with this release.<br />
<br />
To do a manual install, simply download the desired files and extract them all into the same directory. If you have WinZip, PowerArchiver, or any other similar program, this is as easy as selecting all the archives simultaneously and choosing "unpack here" from the context menu.<br />
<br />
For clarity, I recommend to put MinGW into C:\MinGW, but almost any other locations should do equally well. Avoid pathnames with spaces or exotic characters, as this may confuse some commandline tools (most notably <tt>gdb</tt>).<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download]<br />
<br />
===Optionally:===<br />
====Fortran77 compiler====<br />
*[http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz?download http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz?download]<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Other developer tools====<br />
Ports of the most often used Unix utilities. Note that some tools in UnxUtils are quite a bit outdated, so make sure you <u>do not</u> overwrite already existing MinGW files with their UnxUtils counterparts:<br />
*[http://unxutils.sourceforge.net/UnxUtils.zip UnxUtils]<br />
*[http://unxutils.sourceforge.net/UnxUpdates.zip UnxUtils-Latest-Updates]<br />
<br />
<br />
More recent versions of commonly used utilities and utilities not found in UnxUtils:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/coreutils-5.3.0-bin.zip?download coreutils-5.3.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/zip-2.31-bin.zip?download zip-2.31]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/tar-1.13-1-bin.zip?download tar-1.13-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gzip-1.3.5-3-bin.zip?download gzip-1.3.5]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bzip2-1.0.3-1-bin.zip?download bzip2-1.0.0-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/autoconf-2.59-bin.zip?download autoconf-2.59]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/automake-1.9.4-bin.zip?download automake-1.9.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bison-2.1-bin.zip?download bison-2.1 (includes m4)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/flex-2.5.4a-1-bin.zip?download flex-2.5.4a]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gperf-3.0.1-bin.zip?download gperf-3.0.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/diffutils-2.8.7-1-bin.zip?download diffutils-2.8.7]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/patch-2.5.9-6-bin.zip?download patch-2.5.9-6]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/grep-2.5.1a-bin.zip?download grep-2.5.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/sed-4.1.4-bin.zip?download sed-4.1.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/hextools-1.0-bin.zip?download hextools-1.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/findutils-4.2.20-2-bin.zip?download findutils-4.2.20]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/less-394-bin.zip?download less 3.94]<br />
*[http://prdownloads.sourceforge.net/mingw/wget-1.9.1-mingwPORT.tar.bz2?download wget-1.9.1]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip gettext-0.14.5]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-dev-0.14.5.zip gettext-dev-0.14.5]<br />
<br />
Dependencies:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/pcre-6.4-1-bin.zip?download pcre-6.4.1 (needed by grep and less)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libintl-0.14.4-bin.zip?download libintl-0.14.4 (needed by most tools)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libiconv-1.9.2-1-bin.zip?download libiconv-1.9.2-1 (needed by most tools)]<br />
<br />
==Resulting Folder Layout==<br />
[[Image:Lay.png]]<br />
<br />
<br />
==GCC 3.4.4 manual install==<br />
Some people have reported various problems with gcc version 3.4.4, so it may be worth a consideration to use the either the 3.4.5 or 3.4.2 releases until a build from the 4.x branch is available.<br />Personally, I have not had any kind of problem with either 3.4.4 or 3.4.5.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download]<br />
<br />
<br />
==GCC 3.4.2 manual install==<br />
Installing MinGW can be quite intimidating the first time because it is not obvious what you have to do. Luckily, it is actually pretty simple.<br /><br />
To do a manual install, simply download the required files and extract them all into the same directory. For simplicity, I recommend <tt>C:\MinGW</tt>.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download]<br />
====Fortran77 compiler====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download]<br />
<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows&diff=3898
Installing Code::Blocks from source on Windows
2006-10-05T08:52:55Z
<p>Thomas: /* Compile Code::Blocks */</p>
<hr />
<div>[[Category:Installing Code::Blocks]]<br />
[[Category:Installing Code::Blocks from source]]<br />
<br />
== Prerequisites ==<br />
<br />
'''Note for RC2 users'''<br />
<br />
The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.<br />
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].<br />
<br />
=== MinGW compiler ===<br />
<br />
At the present time, Code::Blocks only compiles successfully with the MinGW compiler (or any other gcc for that matter). You will need a complete, working [[MinGW installation]].<br />
<br />
=== wxWidgets ===<br />
<br />
Code::Blocks officially supports wxWidgets 2.6.3 (although any 2.6+ version probably works).<br/><br />
Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3-1.zip].<br />
<br />
<br />
You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').<br />
<br />
=== SVN client ===<br />
<br />
In order to check out the Code::Blocks sources you will need a SVN client.<br />
For convenience, it is recommended that you install [http://tortoisesvn.tigris.org/download.html TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn commandline client] equally well.<br />
<br />
It is generally a good idea to install the commandline client (and adding it to PATH) even if you use TortoiseSVN for convenience. The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn</tt> binary if it is available. This is preferrable to the manual parsing of the entries file that is used as fallback.<br />
<br />
<br />
Please do note that working copies checked out with the 1.4 version of Subversion are no longer compatible with earlier versions (Subversion will transparently update existing repositories).<br />
<br />
The builtin fallback mechanism in <tt>autorevision</tt> has been updated to the new 1.4 format and will no longer work with the old format.<br><br />
Therefore, if you use a Subversion client from the 1.0-1.3 line, you ''must'' put the commandline tool into <tt>PATH</tt> for a successful build.<br><br />
If you use Subversion 1.4, then it is good practice nevertheless, but you can do without, too.<br />
<br />
=== Code::Blocks sources ===<br />
<br />
You will also (obviously) need the Code::Blocks sources. <br />
<br />
Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".<br />
<br />
In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.<br />
<br />
Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:<br />
<br />
mkdir codeblocks-head<br />
cd codeblocks-head<br />
svn checkout svn://svn.berlios.de/codeblocks/trunk<br />
<br />
=== zip.exe ===<br />
<br />
You'll also need a working 'zip' program.<br />
If you have the version listed on our [https://wiki.codeblocks.org/index.php?title=Mingw#Other_developer_tools tools page], you'll be fine, alternatively you can use the one found [http://www.info-zip.org/ here].<br />
<br />
The zip program coming with cygwin will ''not'' work properly. You do ''not'' need WinZip.<br />
<br />
Make sure the zip binary is in your PATH so the <tt>update.bat</tt> script will be able to find it (alternatively, you can edit the batch file, setting the ZIPCMD variable to something else).<br />
<br />
The easiest way is to put zip.exe into <tt>bin</tt> inside your MinGW installation directory (that folder is normally in the path).<br />
<br />
== Building ==<br />
<br />
=== Unicode Build ===<br />
<br />
==== Compile wxWidgets in Unicode mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy <tt>lib\gcc_dll\wxmsw26u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>src\devel</tt> directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into dll hell).<br />
<br />
Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The stripped ("production") executable is found in <tt>output</tt> together with all libraries and data files. If you want a version with debug symbols instead (caution: huge size!), use the one found in the <tt>devel</tt> folder.<br><br />
Congratulations, you own a freshly built version of Code::Blocks!<br />
<br />
For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/><br />
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>.<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/><br />
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.<br />
<br />
Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== ANSI Build ===<br />
<br />
<div style="background-color: #f7d9d9; border: 1px solid #000"><br />
<div style="margin: 5px;"><br />
<br />
==== DEPRECATION WARNING: ====<br />
As of February 2006, the official default build for Code::Blocks is '''Unicode''' (see above). Although ANSI builds are technically possible, we discourage their use unless there is a good reason.<br/><br />
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''<br />
<br />
There is hardly any good argument against using a Unicode build if your OS supports Unicode, even if you do not understand any other language than English, as a Unicode version guarantees that it will be able to work with whatever languages you may possibly encounter in the future -- at a very reasonable cost.<br />
<br />
However, if you absolutely don't care about Unicode or if you are bound to use Windows 95, then you may want to build an ANSI version nevertheless.<br />
<br />
</div><br />
</div><br />
<br />
==== Compile wxWidgets in ANSI mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx) if you have not used it before. Enter the location where you unpacked wxWidgets.<br />
<br />
'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:<br />
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.<br />
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).<br />
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.<br />
<br />
One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).<br />
<br />
Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows&diff=3897
Installing Code::Blocks from source on Windows
2006-10-05T08:41:30Z
<p>Thomas: /* SVN client */</p>
<hr />
<div>[[Category:Installing Code::Blocks]]<br />
[[Category:Installing Code::Blocks from source]]<br />
<br />
== Prerequisites ==<br />
<br />
'''Note for RC2 users'''<br />
<br />
The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.<br />
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].<br />
<br />
=== MinGW compiler ===<br />
<br />
At the present time, Code::Blocks only compiles successfully with the MinGW compiler (or any other gcc for that matter). You will need a complete, working [[MinGW installation]].<br />
<br />
=== wxWidgets ===<br />
<br />
Code::Blocks officially supports wxWidgets 2.6.3 (although any 2.6+ version probably works).<br/><br />
Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3-1.zip].<br />
<br />
<br />
You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').<br />
<br />
=== SVN client ===<br />
<br />
In order to check out the Code::Blocks sources you will need a SVN client.<br />
For convenience, it is recommended that you install [http://tortoisesvn.tigris.org/download.html TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn commandline client] equally well.<br />
<br />
It is generally a good idea to install the commandline client (and adding it to PATH) even if you use TortoiseSVN for convenience. The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn</tt> binary if it is available. This is preferrable to the manual parsing of the entries file that is used as fallback.<br />
<br />
<br />
Please do note that working copies checked out with the 1.4 version of Subversion are no longer compatible with earlier versions (Subversion will transparently update existing repositories).<br />
<br />
The builtin fallback mechanism in <tt>autorevision</tt> has been updated to the new 1.4 format and will no longer work with the old format.<br><br />
Therefore, if you use a Subversion client from the 1.0-1.3 line, you ''must'' put the commandline tool into <tt>PATH</tt> for a successful build.<br><br />
If you use Subversion 1.4, then it is good practice nevertheless, but you can do without, too.<br />
<br />
=== Code::Blocks sources ===<br />
<br />
You will also (obviously) need the Code::Blocks sources. <br />
<br />
Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".<br />
<br />
In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.<br />
<br />
Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:<br />
<br />
mkdir codeblocks-head<br />
cd codeblocks-head<br />
svn checkout svn://svn.berlios.de/codeblocks/trunk<br />
<br />
=== zip.exe ===<br />
<br />
You'll also need a working 'zip' program.<br />
If you have the version listed on our [https://wiki.codeblocks.org/index.php?title=Mingw#Other_developer_tools tools page], you'll be fine, alternatively you can use the one found [http://www.info-zip.org/ here].<br />
<br />
The zip program coming with cygwin will ''not'' work properly. You do ''not'' need WinZip.<br />
<br />
Make sure the zip binary is in your PATH so the <tt>update.bat</tt> script will be able to find it (alternatively, you can edit the batch file, setting the ZIPCMD variable to something else).<br />
<br />
The easiest way is to put zip.exe into <tt>bin</tt> inside your MinGW installation directory (that folder is normally in the path).<br />
<br />
== Building ==<br />
<br />
=== Unicode Build ===<br />
<br />
==== Compile wxWidgets in Unicode mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy <tt>lib\gcc_dll\wxmsw26u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>src\devel</tt> directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into dll hell).<br />
<br />
Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is <tt>src\output</tt> in Code::Blocks tree. From here you do not need the nighty build any more.<br />
<br />
For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/><br />
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>. You'll now have an up-to-date Code::Blocks!<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/><br />
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.<br />
<br />
Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== ANSI Build ===<br />
<br />
<div style="background-color: #f7d9d9; border: 1px solid #000"><br />
<div style="margin: 5px;"><br />
<br />
==== DEPRECATION WARNING: ====<br />
As of February 2006, the official default build for Code::Blocks is '''Unicode''' (see above). Although ANSI builds are technically possible, we discourage their use unless there is a good reason.<br/><br />
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''<br />
<br />
There is hardly any good argument against using a Unicode build if your OS supports Unicode, even if you do not understand any other language than English, as a Unicode version guarantees that it will be able to work with whatever languages you may possibly encounter in the future -- at a very reasonable cost.<br />
<br />
However, if you absolutely don't care about Unicode or if you are bound to use Windows 95, then you may want to build an ANSI version nevertheless.<br />
<br />
</div><br />
</div><br />
<br />
==== Compile wxWidgets in ANSI mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx) if you have not used it before. Enter the location where you unpacked wxWidgets.<br />
<br />
'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:<br />
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.<br />
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).<br />
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.<br />
<br />
One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).<br />
<br />
Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows&diff=3896
Installing Code::Blocks from source on Windows
2006-10-05T08:23:42Z
<p>Thomas: /* MinGW compiler */</p>
<hr />
<div>[[Category:Installing Code::Blocks]]<br />
[[Category:Installing Code::Blocks from source]]<br />
<br />
== Prerequisites ==<br />
<br />
'''Note for RC2 users'''<br />
<br />
The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.<br />
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].<br />
<br />
=== MinGW compiler ===<br />
<br />
At the present time, Code::Blocks only compiles successfully with the MinGW compiler (or any other gcc for that matter). You will need a complete, working [[MinGW installation]].<br />
<br />
=== wxWidgets ===<br />
<br />
Code::Blocks officially supports wxWidgets 2.6.3 (although any 2.6+ version probably works).<br/><br />
Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3-1.zip].<br />
<br />
<br />
You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').<br />
<br />
=== SVN client ===<br />
<br />
In order to check out the Code::Blocks sources you will need a SVN client.<br />
It is recommended that you install [http://tortoisesvn.tigris.org/download.html TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn commandline client].<br />
<br />
=== Code::Blocks sources ===<br />
<br />
You will also (obviously) need the Code::Blocks sources. <br />
<br />
Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".<br />
<br />
In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.<br />
<br />
Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:<br />
<br />
mkdir codeblocks-head<br />
cd codeblocks-head<br />
svn checkout svn://svn.berlios.de/codeblocks/trunk<br />
<br />
=== zip.exe ===<br />
<br />
You'll also need a working 'zip' program.<br />
If you have the version listed on our [https://wiki.codeblocks.org/index.php?title=Mingw#Other_developer_tools tools page], you'll be fine, alternatively you can use the one found [http://www.info-zip.org/ here].<br />
<br />
The zip program coming with cygwin will ''not'' work properly. You do ''not'' need WinZip.<br />
<br />
Make sure the zip binary is in your PATH so the <tt>update.bat</tt> script will be able to find it (alternatively, you can edit the batch file, setting the ZIPCMD variable to something else).<br />
<br />
The easiest way is to put zip.exe into <tt>bin</tt> inside your MinGW installation directory (that folder is normally in the path).<br />
<br />
== Building ==<br />
<br />
=== Unicode Build ===<br />
<br />
==== Compile wxWidgets in Unicode mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy <tt>lib\gcc_dll\wxmsw26u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>src\devel</tt> directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into dll hell).<br />
<br />
Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is <tt>src\output</tt> in Code::Blocks tree. From here you do not need the nighty build any more.<br />
<br />
For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/><br />
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>. You'll now have an up-to-date Code::Blocks!<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/><br />
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.<br />
<br />
Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== ANSI Build ===<br />
<br />
<div style="background-color: #f7d9d9; border: 1px solid #000"><br />
<div style="margin: 5px;"><br />
<br />
==== DEPRECATION WARNING: ====<br />
As of February 2006, the official default build for Code::Blocks is '''Unicode''' (see above). Although ANSI builds are technically possible, we discourage their use unless there is a good reason.<br/><br />
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''<br />
<br />
There is hardly any good argument against using a Unicode build if your OS supports Unicode, even if you do not understand any other language than English, as a Unicode version guarantees that it will be able to work with whatever languages you may possibly encounter in the future -- at a very reasonable cost.<br />
<br />
However, if you absolutely don't care about Unicode or if you are bound to use Windows 95, then you may want to build an ANSI version nevertheless.<br />
<br />
</div><br />
</div><br />
<br />
==== Compile wxWidgets in ANSI mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx) if you have not used it before. Enter the location where you unpacked wxWidgets.<br />
<br />
'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:<br />
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.<br />
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).<br />
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.<br />
<br />
One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).<br />
<br />
Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows&diff=3895
Installing Code::Blocks from source on Windows
2006-10-05T08:07:27Z
<p>Thomas: /* zip.exe */</p>
<hr />
<div>[[Category:Installing Code::Blocks]]<br />
[[Category:Installing Code::Blocks from source]]<br />
<br />
== Prerequisites ==<br />
<br />
'''Note for RC2 users'''<br />
<br />
The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.<br />
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].<br />
<br />
=== MinGW compiler ===<br />
<br />
At the present time, Code::Blocks only compiles successfully with the MinGW compiler. You will need a complete, working [[MinGW installation]].<br />
<br />
=== wxWidgets ===<br />
<br />
Code::Blocks officially supports wxWidgets 2.6.3 (although any 2.6+ version probably works).<br/><br />
Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3-1.zip].<br />
<br />
<br />
You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').<br />
<br />
=== SVN client ===<br />
<br />
In order to check out the Code::Blocks sources you will need a SVN client.<br />
It is recommended that you install [http://tortoisesvn.tigris.org/download.html TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn commandline client].<br />
<br />
=== Code::Blocks sources ===<br />
<br />
You will also (obviously) need the Code::Blocks sources. <br />
<br />
Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".<br />
<br />
In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.<br />
<br />
Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:<br />
<br />
mkdir codeblocks-head<br />
cd codeblocks-head<br />
svn checkout svn://svn.berlios.de/codeblocks/trunk<br />
<br />
=== zip.exe ===<br />
<br />
You'll also need a working 'zip' program.<br />
If you have the version listed on our [https://wiki.codeblocks.org/index.php?title=Mingw#Other_developer_tools tools page], you'll be fine, alternatively you can use the one found [http://www.info-zip.org/ here].<br />
<br />
The zip program coming with cygwin will ''not'' work properly. You do ''not'' need WinZip.<br />
<br />
Make sure the zip binary is in your PATH so the <tt>update.bat</tt> script will be able to find it (alternatively, you can edit the batch file, setting the ZIPCMD variable to something else).<br />
<br />
The easiest way is to put zip.exe into <tt>bin</tt> inside your MinGW installation directory (that folder is normally in the path).<br />
<br />
== Building ==<br />
<br />
=== Unicode Build ===<br />
<br />
==== Compile wxWidgets in Unicode mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy <tt>lib\gcc_dll\wxmsw26u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>src\devel</tt> directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into dll hell).<br />
<br />
Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is <tt>src\output</tt> in Code::Blocks tree. From here you do not need the nighty build any more.<br />
<br />
For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/><br />
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>. You'll now have an up-to-date Code::Blocks!<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/><br />
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.<br />
<br />
Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== ANSI Build ===<br />
<br />
<div style="background-color: #f7d9d9; border: 1px solid #000"><br />
<div style="margin: 5px;"><br />
<br />
==== DEPRECATION WARNING: ====<br />
As of February 2006, the official default build for Code::Blocks is '''Unicode''' (see above). Although ANSI builds are technically possible, we discourage their use unless there is a good reason.<br/><br />
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''<br />
<br />
There is hardly any good argument against using a Unicode build if your OS supports Unicode, even if you do not understand any other language than English, as a Unicode version guarantees that it will be able to work with whatever languages you may possibly encounter in the future -- at a very reasonable cost.<br />
<br />
However, if you absolutely don't care about Unicode or if you are bound to use Windows 95, then you may want to build an ANSI version nevertheless.<br />
<br />
</div><br />
</div><br />
<br />
==== Compile wxWidgets in ANSI mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx) if you have not used it before. Enter the location where you unpacked wxWidgets.<br />
<br />
'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:<br />
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.<br />
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).<br />
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.<br />
<br />
One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).<br />
<br />
Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows&diff=3894
Installing Code::Blocks from source on Windows
2006-10-05T07:55:16Z
<p>Thomas: /* wxWidgets */</p>
<hr />
<div>[[Category:Installing Code::Blocks]]<br />
[[Category:Installing Code::Blocks from source]]<br />
<br />
== Prerequisites ==<br />
<br />
'''Note for RC2 users'''<br />
<br />
The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.<br />
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].<br />
<br />
=== MinGW compiler ===<br />
<br />
At the present time, Code::Blocks only compiles successfully with the MinGW compiler. You will need a complete, working [[MinGW installation]].<br />
<br />
=== wxWidgets ===<br />
<br />
Code::Blocks officially supports wxWidgets 2.6.3 (although any 2.6+ version probably works).<br/><br />
Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3-1.zip].<br />
<br />
<br />
You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').<br />
<br />
=== SVN client ===<br />
<br />
In order to check out the Code::Blocks sources you will need a SVN client.<br />
It is recommended that you install [http://tortoisesvn.tigris.org/download.html TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn commandline client].<br />
<br />
=== Code::Blocks sources ===<br />
<br />
You will also (obviously) need the Code::Blocks sources. <br />
<br />
Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".<br />
<br />
In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.<br />
<br />
Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:<br />
<br />
mkdir codeblocks-head<br />
cd codeblocks-head<br />
svn checkout svn://svn.berlios.de/codeblocks/trunk<br />
<br />
=== zip.exe ===<br />
<br />
You'll also need the 'zip.exe' compression program, found [http://www.info-zip.org/ here].<br />
Only the command-line zip.exe is needed; you must install it somewhere in your PATH.<br />
Put zip.exe wherever you installed MinGW in the '''bin''', or the '''mingw32\bin''' folder. <br />
<br />
== Building ==<br />
<br />
=== Unicode Build ===<br />
<br />
==== Compile wxWidgets in Unicode mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy <tt>lib\gcc_dll\wxmsw26u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>src\devel</tt> directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into dll hell).<br />
<br />
Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is <tt>src\output</tt> in Code::Blocks tree. From here you do not need the nighty build any more.<br />
<br />
For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/><br />
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>. You'll now have an up-to-date Code::Blocks!<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/><br />
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.<br />
<br />
Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== ANSI Build ===<br />
<br />
<div style="background-color: #f7d9d9; border: 1px solid #000"><br />
<div style="margin: 5px;"><br />
<br />
==== DEPRECATION WARNING: ====<br />
As of February 2006, the official default build for Code::Blocks is '''Unicode''' (see above). Although ANSI builds are technically possible, we discourage their use unless there is a good reason.<br/><br />
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''<br />
<br />
There is hardly any good argument against using a Unicode build if your OS supports Unicode, even if you do not understand any other language than English, as a Unicode version guarantees that it will be able to work with whatever languages you may possibly encounter in the future -- at a very reasonable cost.<br />
<br />
However, if you absolutely don't care about Unicode or if you are bound to use Windows 95, then you may want to build an ANSI version nevertheless.<br />
<br />
</div><br />
</div><br />
<br />
==== Compile wxWidgets in ANSI mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx) if you have not used it before. Enter the location where you unpacked wxWidgets.<br />
<br />
'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:<br />
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.<br />
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).<br />
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.<br />
<br />
One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).<br />
<br />
Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows&diff=3877
Installing Code::Blocks from source on Windows
2006-10-01T17:40:33Z
<p>Thomas: /* Building */</p>
<hr />
<div>[[Category:Installing Code::Blocks]]<br />
[[Category:Installing Code::Blocks from source]]<br />
<br />
== Prerequisites ==<br />
<br />
'''Note for RC2 users'''<br />
<br />
The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.<br />
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].<br />
<br />
=== MinGW compiler ===<br />
<br />
At the present time, Code::Blocks only compiles successfully with the MinGW compiler. You will need a complete, working [[MinGW installation]].<br />
<br />
=== wxWidgets ===<br />
<br />
Code::Blocks officially supports wxWidgets 2.6.2<br />
<br />
You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').<br />
<br />
[http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.2.zip Download wxWidgets 2.6.2 from Sourceforge].<br />
<br />
You can also use the more recent '''[http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3-Setup.exe wxWidgets-2.6.3]''', but you will need to install '''[ftp://biolpc22.york.ac.uk/pub/2.6.3/wxWidgets-2.6.3-Patch-2.zip patch 2 for 2.6.3]''' over it.<br />
The patch is not a diff file, but a '''.zip''' file that must be unpacked on top of wxWidgets tree.<br />
<br />
=== SVN client ===<br />
<br />
In order to check out the Code::Blocks sources you will need a SVN client.<br />
It is recommended that you install [http://tortoisesvn.tigris.org/download.html TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn commandline client].<br />
<br />
=== Code::Blocks sources ===<br />
<br />
You will also (obviously) need the Code::Blocks sources. <br />
<br />
Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".<br />
<br />
In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.<br />
<br />
Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:<br />
<br />
mkdir codeblocks-head<br />
cd codeblocks-head<br />
svn checkout svn://svn.berlios.de/codeblocks/trunk<br />
<br />
=== zip.exe ===<br />
<br />
You'll also need the 'zip.exe' compression program, found [http://www.info-zip.org/ here].<br />
Only the command-line zip.exe is needed; you must install it somewhere in your PATH.<br />
Put zip.exe wherever you installed MinGW in the '''bin''', or the '''mingw32\bin''' folder. <br />
<br />
== Building ==<br />
<br />
=== Unicode Build ===<br />
<br />
==== Compile wxWidgets in Unicode mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy <tt>lib\gcc_dll\wxmsw26u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>src\devel</tt> directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into dll hell).<br />
<br />
Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is <tt>src\output</tt> in Code::Blocks tree. From here you do not need the nighty build any more.<br />
<br />
For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/><br />
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>. You'll now have an up-to-date Code::Blocks!<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/><br />
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.<br />
<br />
Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<div style="background: #f9f9f9; color: #666;"><br />
=== ANSI Build ===<br />
<br />
==== DEPRECATION WARNING: ====<br />
As of February 2006, the official default build for Code::Blocks is '''Unicode''' (see above). Although ANSI builds are technically possible, we discourage their use unless there is a good reason.<br/><br />
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''<br />
<br />
There is hardly any good argument against using a Unicode build if your OS supports Unicode, even if you do not understand any other language than English, as a Unicode version guarantees that it will be able to work with whatever languages you may possibly encounter in the future -- at a very reasonable cost.<br />
<br />
However, if you absolutely don't care about Unicode or if you are bound to use Windows 95, then you may want to build an ANSI version nevertheless.<br />
<br />
<br />
==== Compile wxWidgets in ANSI mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx) if you have not used it before. Enter the location where you unpacked wxWidgets.<br />
<br />
'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:<br />
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.<br />
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).<br />
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.<br />
<br />
One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).<br />
<br />
Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.<br />
</div></div>
Thomas
https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows&diff=3876
Installing Code::Blocks from source on Windows
2006-10-01T17:16:26Z
<p>Thomas: </p>
<hr />
<div>[[Category:Installing Code::Blocks]]<br />
[[Category:Installing Code::Blocks from source]]<br />
<br />
== Prerequisites ==<br />
<br />
'''Note for RC2 users'''<br />
<br />
The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.<br />
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].<br />
<br />
=== MinGW compiler ===<br />
<br />
At the present time, Code::Blocks only compiles successfully with the MinGW compiler. You will need a complete, working [[MinGW installation]].<br />
<br />
=== wxWidgets ===<br />
<br />
Code::Blocks officially supports wxWidgets 2.6.2<br />
<br />
You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').<br />
<br />
[http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.2.zip Download wxWidgets 2.6.2 from Sourceforge].<br />
<br />
You can also use the more recent '''[http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3-Setup.exe wxWidgets-2.6.3]''', but you will need to install '''[ftp://biolpc22.york.ac.uk/pub/2.6.3/wxWidgets-2.6.3-Patch-2.zip patch 2 for 2.6.3]''' over it.<br />
The patch is not a diff file, but a '''.zip''' file that must be unpacked on top of wxWidgets tree.<br />
<br />
=== SVN client ===<br />
<br />
In order to check out the Code::Blocks sources you will need a SVN client.<br />
It is recommended that you install [http://tortoisesvn.tigris.org/download.html TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn commandline client].<br />
<br />
=== Code::Blocks sources ===<br />
<br />
You will also (obviously) need the Code::Blocks sources. <br />
<br />
Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".<br />
<br />
In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.<br />
<br />
Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:<br />
<br />
mkdir codeblocks-head<br />
cd codeblocks-head<br />
svn checkout svn://svn.berlios.de/codeblocks/trunk<br />
<br />
=== zip.exe ===<br />
<br />
You'll also need the 'zip.exe' compression program, found [http://www.info-zip.org/ here].<br />
Only the command-line zip.exe is needed; you must install it somewhere in your PATH.<br />
Put zip.exe wherever you installed MinGW in the '''bin''', or the '''mingw32\bin''' folder. <br />
<br />
== Building ==<br />
<br />
=== Unicode Build ===<br />
<br />
==== Compile wxWidgets in Unicode mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy <tt>lib\gcc_dll\wxmsw26u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>src\devel</tt> directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into dll hell).<br />
<br />
Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is <tt>src\output</tt> in Code::Blocks tree. From here you do not need the nighty build any more.<br />
<br />
For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/><br />
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>. You'll now have an up-to-date Code::Blocks!<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/><br />
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.<br />
<br />
Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
=== ANSI Build ===<br />
<br />
''Note:<br />
Code::Blocks is now built in Unicode mode by default (see above).<br />
However, if you don't care about Unicode or if you use an old Windows version that does not support Unicode, then you might want to build an ANSI version nevertheless.''<br />
<br />
==== Compile wxWidgets in ANSI mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx) if you have not used it before. Enter the location where you unpacked wxWidgets.<br />
<br />
'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:<br />
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.<br />
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).<br />
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.<br />
<br />
One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).<br />
<br />
Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
Provided by Thomas Denk<br />
Small edits by Max</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows&diff=3875
Installing Code::Blocks from source on Windows
2006-10-01T17:10:57Z
<p>Thomas: Removed wrong $(#cb) variable, some minor edits</p>
<hr />
<div>[[Category:Installing Code::Blocks]]<br />
[[Category:Installing Code::Blocks from source]]<br />
<br />
== Prerequisites ==<br />
<br />
'''Note for RC2 users'''<br />
<br />
The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.<br />
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].<br />
<br />
=== MinGW compiler ===<br />
<br />
At the present time, Code::Blocks only compiles successfully with the MinGW compiler. You will need a complete, working [[MinGW installation]].<br />
<br />
=== wxWidgets ===<br />
<br />
Code::Blocks officially supports wxWidgets 2.6.2<br />
<br />
You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').<br />
<br />
[http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.2.zip Download wxWidgets 2.6.2 from Sourceforge].<br />
<br />
You can also use the more recent '''[http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3-Setup.exe wxWidgets-2.6.3]''', but you will need to install '''[ftp://biolpc22.york.ac.uk/pub/2.6.3/wxWidgets-2.6.3-Patch-2.zip patch 2 for 2.6.3]''' over it.<br />
The patch is not a diff file, but a '''.zip''' file that must be unpacked on top of wxWidgets tree.<br />
<br />
=== SVN client ===<br />
<br />
In order to check out the Code::Blocks sources you will need a SVN client.<br />
It is recommended that you install [http://tortoisesvn.tigris.org/download.html TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn commandline client].<br />
<br />
=== Code::Blocks sources ===<br />
<br />
You will also (obviously) need the Code::Blocks sources. <br />
<br />
Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".<br />
<br />
In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.<br />
<br />
Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:<br />
<br />
mkdir codeblocks-head<br />
cd codeblocks-head<br />
svn checkout svn://svn.berlios.de/codeblocks/trunk<br />
<br />
=== zip.exe ===<br />
<br />
You'll also need the 'zip.exe' compression program, found [http://www.info-zip.org/ here].<br />
Only the command-line zip.exe is needed; you must install it somewhere in your PATH.<br />
Put zip.exe wherever you installed MinGW in the '''bin''', or the '''mingw32\bin''' folder. <br />
<br />
== Building ==<br />
<br />
=== Unicode Build ===<br />
<br />
==== Compile wxWidgets in Unicode mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy <tt>lib\gcc_dll\wxmsw26u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>src\devel</tt> directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into dll hell).<br />
<br />
Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is <tt>src\output</tt> in Code::Blocks tree. From here you do not need the nighty build any more.<br />
<br />
For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/><br />
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>. You'll now have an up-to-date Code::Blocks!<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
=== ANSI Build ===<br />
<br />
''Note:<br />
Code::Blocks is now built in Unicode mode by default (see above).<br />
However, if you don't care about Unicode or if you use an old Windows version that does not support Unicode, then you might want to build an ANSI version nevertheless.''<br />
<br />
==== Compile wxWidgets in ANSI mode ====<br />
<br />
After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets<br />
<br />
set path=c:\mingw\bin;c:\mingw\mingw32\bin<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean<br />
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0<br />
<br />
This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.<br />
<br />
You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.<br />
<br />
'''Optional:'''<br />
<br />
To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.<br />
<br />
==== Compile Code::Blocks ====<br />
<br />
Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx) if you have not used it before. Enter the location where you unpacked wxWidgets.<br />
<br />
'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:<br />
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.<br />
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).<br />
<br />
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.<br />
<br />
After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).<br />
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.<br />
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.<br />
<br />
One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).<br />
<br />
Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !<br />
<br />
==== Install Code::Blocks ====<br />
<br />
Copy the folder output to where you want Code::Blocks to reside.<br />
<br />
==== Compile contributed (or your own) plugins ====<br />
<br />
The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.<br />
<br />
Provided by Thomas Denk<br />
Small edits by Max</div>
Thomas
https://wiki.codeblocks.org/index.php?title=MinGW_installation&diff=3842
MinGW installation
2006-09-21T17:23:37Z
<p>Thomas: /* Using the MinGW installer */</p>
<hr />
<div>[[Category:User Documentation]]<br />
==Using the MinGW installer==<br />
Note: At the present time, it is still preferrable to download the packages by hand, as the installers are not production quality (unless you really feel unsure unpacking a couple of archives).<br />
<br />
Also, the installer reportedly does not work on Windows Vista, follow the [[MinGW_installation#GCC_3.4.5_manual_install | manual installation instructions]].<br /><br />
(In general, MinGW is not confirmed to work for any Windows Vista betas or RCs)<br />
<br />
MinGW Installer 5.02 allows to choose the SF mirror while 5.03 does not (automatically picks one randomly).<br />
Either installer allows to downloads/installs "previous", "current" and "candidate" mingw packages.<br />
<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.2.exe MinGW Installer 5.0.2]<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.3.exe MinGW Installer 5.0.3]<br />
<br />
'''Note that the MinGW version number is not related to the actual compiler version.'''<br />
<br />
Please do note that the installer applications require an internet connection and will download the actual MinGW packages at the time of installation.<br />
<br />
==GCC 3.4.5 manual install==<br />
This is the "candidate" release of MinGW, so it is not considered "stable" officially.<br />Personally, I have not had any kind of problem with this release.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download]<br />
<br />
===Optionally:===<br />
====Fortran77 compiler====<br />
*[http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz?download http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz?download]<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Other developer tools====<br />
Ports of the most often used Unix utilities. Note that some tools in UnxUtils are quite a bit outdated, so make sure you <u>do not</u> overwrite already existing MinGW files with their UnxUtils counterparts:<br />
*[http://unxutils.sourceforge.net/UnxUtils.zip UnxUtils]<br />
*[http://unxutils.sourceforge.net/UnxUpdates.zip UnxUtils-Latest-Updates]<br />
<br />
<br />
More recent versions of commonly used utilities and utilities not found in UnxUtils:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/coreutils-5.3.0-bin.zip?download coreutils-5.3.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/zip-2.31-bin.zip?download zip-2.31]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/tar-1.13-1-bin.zip?download tar-1.13-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gzip-1.3.5-3-bin.zip?download gzip-1.3.5]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bzip2-1.0.3-1-bin.zip?download bzip2-1.0.0-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/autoconf-2.59-bin.zip?download autoconf-2.59]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/automake-1.9.4-bin.zip?download automake-1.9.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bison-2.1-bin.zip?download bison-2.1 (includes m4)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/flex-2.5.4a-1-bin.zip?download flex-2.5.4a]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gperf-3.0.1-bin.zip?download gperf-3.0.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/diffutils-2.8.7-1-bin.zip?download diffutils-2.8.7]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/patch-2.5.9-6-bin.zip?download patch-2.5.9-6]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/grep-2.5.1a-bin.zip?download grep-2.5.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/sed-4.1.4-bin.zip?download sed-4.1.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/hextools-1.0-bin.zip?download hextools-1.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/findutils-4.2.20-2-bin.zip?download findutils-4.2.20]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/less-394-bin.zip?download less 3.94]<br />
*[http://prdownloads.sourceforge.net/mingw/wget-1.9.1-mingwPORT.tar.bz2?download wget-1.9.1]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip gettext-0.14.5]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-dev-0.14.5.zip gettext-dev-0.14.5]<br />
<br />
Dependencies:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/pcre-6.4-1-bin.zip?download pcre-6.4.1 (needed by grep and less)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libintl-0.14.4-bin.zip?download libintl-0.14.4 (needed by most tools)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libiconv-1.9.2-1-bin.zip?download libiconv-1.9.2-1 (needed by most tools)]<br />
<br />
==Resulting Folder Layout==<br />
[[Image:Lay.png]]<br />
<br />
<br />
==GCC 3.4.4 manual install==<br />
Some people have reported various problems with gcc version 3.4.4, so it may be worth a consideration to use the either the 3.4.5 or 3.4.2 releases until a build from the 4.x branch is available.<br />Personally, I have not had any kind of problem with either 3.4.4 or 3.4.5.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download]<br />
<br />
<br />
==GCC 3.4.2 manual install==<br />
Installing MinGW can be quite intimidating the first time because it is not obvious what you have to do. Luckily, it is actually pretty simple.<br /><br />
To do a manual install, simply download the required files and extract them all into the same directory. For simplicity, I recommend <tt>C:\MinGW</tt>.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download]<br />
====Fortran77 compiler====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download]<br />
<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Utilities&diff=3740
Utilities
2006-08-30T18:39:19Z
<p>Thomas: </p>
<hr />
<div>#REDIRECT [[MinGW_installation]]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Binutils&diff=3739
Binutils
2006-08-30T18:32:59Z
<p>Thomas: </p>
<hr />
<div>#REDIRECT [[MinGW_installation]]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Mingw&diff=3738
Mingw
2006-08-30T18:31:21Z
<p>Thomas: </p>
<hr />
<div>#REDIRECT [[MinGW_installation]]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=MinGW_installation&diff=3733
MinGW installation
2006-08-30T13:51:28Z
<p>Thomas: /* Other developer tools */</p>
<hr />
<div>[[Category:User Documentation]]<br />
==Using the MinGW installer==<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-4.1.1.exe MinGW 4.1.1]<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.2.exe MinGW 5.0.2]<br />
<br />
'''Note that the MinGW version number is not related to the actual compiler version. Downloading MinGW 4.1 will not provide gcc 4.1!'''<br />
<br />
These are merely installer applications which will upon request download and decompress the actual packages needed. At the present time, it is still preferrable to download the packages by hand, as the installers are not production quality.<br />
'''Both MinGW-4.1.1 and MinGW-5.0.2 are to be considered "alpha".<br />
<br />
==GCC 3.4.5 manual install==<br />
This is the "candidate" release of MinGW, so it is not considered "stable" officially.<br />Personally, I have not had any kind of problem with this release.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Other developer tools====<br />
Ports of the most often used Unix utilities. Note that some tools in UnxUtils are quite a bit outdated, so make sure you <u>do not</u> overwrite already existing MinGW files with their UnxUtils counterparts:<br />
*[http://unxutils.sourceforge.net/UnxUtils.zip UnxUtils]<br />
*[http://unxutils.sourceforge.net/UnxUpdates.zip UnxUtils-Latest-Updates]<br />
<br />
<br />
More recent versions of commonly used utilities and utilities not found in UnxUtils:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/coreutils-5.3.0-bin.zip?download coreutils-5.3.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/zip-2.31-bin.zip?download zip-2.31]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/tar-1.13-1-bin.zip?download tar-1.13-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gzip-1.3.5-3-bin.zip?download gzip-1.3.5]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bzip2-1.0.3-1-bin.zip?download bzip2-1.0.0-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/autoconf-2.59-bin.zip?download autoconf-2.59]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/automake-1.9.4-bin.zip?download automake-1.9.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bison-2.1-bin.zip?download bison-2.1 (includes m4)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/flex-2.5.4a-1-bin.zip?download flex-2.5.4a]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gperf-3.0.1-bin.zip?download gperf-3.0.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/diffutils-2.8.7-1-bin.zip?download diffutils-2.8.7]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/patch-2.5.9-6-bin.zip?download patch-2.5.9-6]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/grep-2.5.1a-bin.zip?download grep-2.5.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/sed-4.1.4-bin.zip?download sed-4.1.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/hextools-1.0-bin.zip?download hextools-1.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/findutils-4.2.20-2-bin.zip?download findutils-4.2.20]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/less-394-bin.zip?download less 3.94]<br />
*[http://prdownloads.sourceforge.net/mingw/wget-1.9.1-mingwPORT.tar.bz2?download wget-1.9.1]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip gettext-0.14.5]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-dev-0.14.5.zip gettext-dev-0.14.5]<br />
<br />
Dependencies:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/pcre-6.4-1-bin.zip?download pcre-6.4.1 (needed by grep and less)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libintl-0.14.4-bin.zip?download libintl-0.14.4 (needed by most tools)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libiconv-1.9.2-1-bin.zip?download libiconv-1.9.2-1 (needed by most tools)]<br />
<br />
==Resulting Folder Layout==<br />
[[Image:Lay.png]]<br />
<br />
<br />
==GCC 3.4.4 manual install==<br />
Some people have reported various problems with gcc version 3.4.4, so it may be worth a consideration to use the either the 3.4.5 or 3.4.2 releases until a build from the 4.x branch is available.<br />Personally, I have not had any kind of problem with either 3.4.4 or 3.4.5.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download]<br />
<br />
<br />
==GCC 3.4.2 manual install==<br />
Installing MinGW can be quite intimidating the first time because it is not obvious what you have to do. Luckily, it is actually pretty simple.<br /><br />
To do a manual install, simply download the required files and extract them all into the same directory. For simplicity, I recommend <tt>C:\MinGW</tt>.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=MinGW_installation&diff=3732
MinGW installation
2006-08-30T13:19:42Z
<p>Thomas: /* other useful stuff */</p>
<hr />
<div>[[Category:User Documentation]]<br />
==Using the MinGW installer==<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-4.1.1.exe MinGW 4.1.1]<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.2.exe MinGW 5.0.2]<br />
<br />
'''Note that the MinGW version number is not related to the actual compiler version. Downloading MinGW 4.1 will not provide gcc 4.1!'''<br />
<br />
These are merely installer applications which will upon request download and decompress the actual packages needed. At the present time, it is still preferrable to download the packages by hand, as the installers are not production quality.<br />
'''Both MinGW-4.1.1 and MinGW-5.0.2 are to be considered "alpha".<br />
<br />
==GCC 3.4.5 manual install==<br />
This is the "candidate" release of MinGW, so it is not considered "stable" officially.<br />Personally, I have not had any kind of problem with this release.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Other developer tools====<br />
Ports of the most often used Unix utilities. Note that some tools in UnxUtils are quite a bit outdated, so make sure you <u>do not</u> overwrite already existing MinGW files with their UnxUtils counterparts:<br />
*[http://unxutils.sourceforge.net/UnxUtils.zip UnxUtils]<br />
*[http://unxutils.sourceforge.net/UnxUpdates.zip UnxUtils-Latest-Updates]<br />
<br />
<br />
More recent versions of commonly used utilities and utilities not found in UnxUtils:<br />
*[http://prdownloads.sourceforge.net/gnuwin32/coreutils-5.3.0-bin.zip?download coreutils-5.3.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/zip-2.31-bin.zip?download zip-2.31]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/tar-1.13-1-bin.zip?download tar-1.13-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gzip-1.3.5-3-bin.zip?download gzip-1.3.5]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bzip2-1.0.3-1-bin.zip?download bzip2-1.0.0-1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/autoconf-2.59-bin.zip?download autoconf-2.59]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/automake-1.9.4-bin.zip?download automake-1.9.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/bison-2.1-bin.zip?download bison-2.1 (includes m4)]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/flex-2.5.4a-1-bin.zip?download flex-2.5.4a]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/gperf-3.0.1-bin.zip?download gperf-3.0.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/diffutils-2.8.7-1-bin.zip?download diffutils-2.8.7]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/patch-2.5.9-6-bin.zip?download patch-2.5.9-6]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/grep-2.5.1a-bin.zip?download grep-2.5.1]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/sed-4.1.4-bin.zip?download sed-4.1.4]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/hextools-1.0-bin.zip?download hextools-1.0]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/findutils-4.2.20-2-bin.zip?download findutils-4.2.20]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/less-394-bin.zip?download less 3.94]<br />
*[http://prdownloads.sourceforge.net/mingw/wget-1.9.1-mingwPORT.tar.bz2?download wget-1.9.1]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip gettext-0.14.5]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-dev-0.14.5.zip gettext-dev-0.14.5]<br />
<br />
==Resulting Folder Layout==<br />
[[Image:Lay.png]]<br />
<br />
<br />
==GCC 3.4.4 manual install==<br />
Some people have reported various problems with gcc version 3.4.4, so it may be worth a consideration to use the either the 3.4.5 or 3.4.2 releases until a build from the 4.x branch is available.<br />Personally, I have not had any kind of problem with either 3.4.4 or 3.4.5.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download]<br />
<br />
<br />
==GCC 3.4.2 manual install==<br />
Installing MinGW can be quite intimidating the first time because it is not obvious what you have to do. Luckily, it is actually pretty simple.<br /><br />
To do a manual install, simply download the required files and extract them all into the same directory. For simplicity, I recommend <tt>C:\MinGW</tt>.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=MinGW_installation&diff=3731
MinGW installation
2006-08-30T12:06:12Z
<p>Thomas: </p>
<hr />
<div>[[Category:User Documentation]]<br />
==Using the MinGW installer==<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-4.1.1.exe MinGW 4.1.1]<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.2.exe MinGW 5.0.2]<br />
<br />
'''Note that the MinGW version number is not related to the actual compiler version. Downloading MinGW 4.1 will not provide gcc 4.1!'''<br />
<br />
These are merely installer applications which will upon request download and decompress the actual packages needed. At the present time, it is still preferrable to download the packages by hand, as the installers are not production quality.<br />
'''Both MinGW-4.1.1 and MinGW-5.0.2 are to be considered "alpha".<br />
<br />
==GCC 3.4.5 manual install==<br />
This is the "candidate" release of MinGW, so it is not considered "stable" officially.<br />Personally, I have not had any kind of problem with this release.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download http://prdownloads.sourceforge.net/mingw/w32api-3.6.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.81-1.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====other useful stuff====<br />
*[http://prdownloads.sourceforge.net/gnuwin32/zip-2.31-bin.zip?download zip-2.31]<br />
*[http://prdownloads.sourceforge.net/mingw/wget-1.9.1-mingwPORT.tar.bz2?download wget-1.9.1]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip gettext-0.14.5]<br />
*[http://www.gimp.org/~tml/gimp/win32/gettext-dev-0.14.5.zip gettext-dev-0.14.5]<br />
<br />
*[http://www.zlib.net/zlib123-dll.zip zlib-1.2.3]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libpng-1.2.8-bin.zip?download libpng-1.2.8]<br />
*[http://prdownloads.sourceforge.net/gnuwin32/libpng-1.2.8-lib.zip?download libpng-1.2.8-devel]<br />
<br />
<br />
<br />
==Resulting Folder Layout==<br />
[[Image:Lay.png]]<br />
<br />
<br />
==GCC 3.4.4 manual install==<br />
Some people have reported various problems with gcc version 3.4.4, so it may be worth a consideration to use the either the 3.4.5 or 3.4.2 releases until a build from the 4.x branch is available.<br />Personally, I have not had any kind of problem with either 3.4.4 or 3.4.5.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download]<br />
<br />
<br />
==GCC 3.4.2 manual install==<br />
Installing MinGW can be quite intimidating the first time because it is not obvious what you have to do. Luckily, it is actually pretty simple.<br /><br />
To do a manual install, simply download the required files and extract them all into the same directory. For simplicity, I recommend <tt>C:\MinGW</tt>.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=MinGW_installation&diff=3730
MinGW installation
2006-08-30T11:27:31Z
<p>Thomas: /* Base system with C++ */</p>
<hr />
<div>[[Category:User Documentation]]<br />
==Using the MinGW installer==<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-4.1.1.exe MinGW 4.1.1]<br />
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.2.exe MinGW 5.0.2]<br />
<br />
'''Note that the MinGW version number is not related to the actual compiler version. Downloading MinGW 4.1 will not provide gcc 4.1!'''<br />
<br />
These are merely installer applications which will upon request download and decompress the actual packages needed. At the present time, it is still preferrable to download the packages by hand, as the installers are not production quality.<br />
'''Both MinGW-4.1.1 and MinGW-5.0.2 are to be considered "alpha".<br />
<br />
==GCC 3.4.2 manual install==<br />
Installing MinGW can be quite intimidating the first time because it is not obvious what you have to do. Luckily, it is actually pretty simple.<br /><br />
To do a manual install, simply download the required files and extract them all into the same directory. For simplicity, I recommend <tt>C:\MinGW</tt>.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz?download]<br />
<br />
<br />
==GCC 3.4.4 manual install==<br />
Some people have reported various problems with gcc version 3.4.4, so it may be worth a consideration to use the 3.4.2 version until a build from the 4.0 branch is available.<br />Personally, I have not had any kind of problem with 3.4.4.<br />
===Base system with C++===<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw-utils-0.3.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz?download]<br />
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz?download]<br />
*[http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download http://prdownloads.sourceforge.net/mingw/mingw32-make-3.80.0-3.tar.gz?download]<br />
<br />
===Optionally:===<br />
====gdb debugger====<br />
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download]<br />
====Objective-C====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz?download]<br />
====Native Java (experimental)====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz?download]<br />
====Fortran-77====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz?download]<br />
====Ada====<br />
*[http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download http://prdownloads.sourceforge.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz?download]<br />
<br />
==Resulting Folder Layout==<br />
[[Image:Lay.png]]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Gcv&diff=3686
Gcv
2006-08-08T16:37:00Z
<p>Thomas: </p>
<hr />
<div>#REDIRECT [[Global compiler variables]]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Global_compiler_variables&diff=3064
Global compiler variables
2006-07-04T14:21:32Z
<p>Thomas: /* Constraints */</p>
<hr />
<div>[[Category:Application Development]]<br />
== Synopsis ==<br />
Working as a developer on a project which relies on 3rd party libraries involves a lot of unnecessary repetitive tasks, such as setting up build variables according to the local filesystem layout. In the case of project files, care must be taken to not accidentially commit a locally modified copy. If one does not pay attention, this can happen easily for example after changing a build flag to make a release build.<br />
<br />
The concept of global compiler variables is an unique new solution for Code::Blocks which addresses this problem.<br />
Global compiler variables allow you to set up a project once, and any number of developers using any number of different filesystem layouts will be able to compile and develop the project. No local layout information ever needs to be changed more than once.<br />
<br />
== Names and Members ==<br />
Global compiler variables in Code::Blocks are discriminated from [[per-project variables]] by a leading hash sign. Global compiler variables are structured; every variable consists of a ''name'' and an optional ''member''.<br />
Names are freely definable, while some of the members are built into the IDE. Although you can choose anything for a variable name in principle, it is advisable to pick a known identifier for common packages. This way, the amount of information that the user needs to provide is minimised. The Code::Blocks team provides a [[Recommended global variables|list of recommended variables]] for known packages.<br />
<br />
The member <tt>base</tt> resolves to the same value as the variable name uses without a member (alias).<br />
<br />
The members <tt>include</tt> and <tt>lib</tt> are by default aliases for ''base''<tt>/include</tt> and ''base''<tt>/lib</tt>, respectively. However, a user can redefine them if another setup is desired.<br />
<br />
It is generally recommended to use the syntax <tt>$(#variable.include)</tt> instead of <tt>$(#variable)/include</tt>, as it provides additional flexibility and is otherwise exactly identical in functionality (see [[Global_compiler_variables#Custom_Members_Mini-Tutorial|mini tutorial]]).<br />
<br />
The members <tt>cflags</tt> and <tt>lflags</tt> are empty by default and can be used to provide the ability to feed the same consistent set of compiler/linker flags to all builds on one machine.<br />
Beginning with revision 2664 (4 July 2006), Code::Blocks allows you to define custom variable members in addition to the builtin ones.<br />
<br />
<br />
[[Image:Gcv_ui.png]]<br />
<br />
<br />
== Constraints ==<br />
*Both set and global compiler variable <i>names</i> may not be empty, must not contain white space, must start with a letter and must consist of alphanumeric characters. Cyrillic or Chinese letters are <i>not</i> alphanumeric characters.<br />If Code::Blocks is given invalid character sequences as name, it may replace them without asking.<br />
*Every variable requires its base to be defined. Everything else is optional, but the base is absolutely mandatory. If you don't define a variable's base, it will not be saved (no matter what other fields you have defined).<br />
*You may not define a custom member that has the same name as a builtin member. Currently, the custom member will overwrite the builtin member, but in general, the behaviour for this case is undefined.<br />
*Variable and member values may contain <i>arbitrary</i> character sequences, subject to the following three constraints:<br />
**You may not define a variable by a value that references the same variable or any of its members<br />
**You may not define a member by a value that references the same member<br />
**You may not define a member or variable by a value that references the same variable or member through a cyclic dependency.<br />
Code::Blocks will detect the most obvious cases of recursive definitions (which may happen by accident), but it will not perform an excessive depth analysis of every possible abuse. If you enter crap, then crap is what you will get, you have been warned.<br />
<br />
<u>Examples:</u><br /><br />
defining <tt>wx.include</tt> as <tt>$(#wx)/include</tt> is redundant, but perfectly legal<br /><br />
defining <tt>wx.include</tt> as <tt>$(#wx.include)</tt> is illegal and will be detected by Code::Blocks<br /><br />
defining <tt>wx.include</tt> as <tt>$(#cb.lib)</tt> which again is defined as <tt>$(#wx.include)</tt> will create an infinite loop<br />
<br />
== Using Global Compiler Variables ==<br />
All you need to do to start using global compiler variables is to put them in your project! Yes, it is really that easy.<br />
<br />
When the IDE detects the presence of an unknown global variable, it will prompt you to enter its value. The value will be saved in your settings, so you never need to enter the information twice.<br />
<br />
If you need to modify or delete a variable at a later time, you can do so from the settings menu.<br />
<br />
<br />
<u>Example:</u><br />
<br />
[[Image:Globvarsdir.png]]<br />
<br />
The above image shows both per-procect and global variables. <tt>WX_CFG</tt> is defined in the project, but <tt>WX</tt> is a global user variable.<br />
<br />
== Variable Sets ==<br />
Sometimes, you want to use different versions of the same library, or you develop two branches of the same program. Although it is still possible to get around with a global compiler variable, it can become tedious. For this purpose, Code::Blocks supports variable <i>sets</i>. A variable set is an independent collection of variables identified by a name (set names have the same constraints as variable names).<br />
<br />
If you wish to switch to a different set of variables, you simply select a different set from the menu. Different sets are not required to have the same variables, and identical variables in different sets are not required to have the same values, or even the same custom members.<br />
<br />
Another positive thing about sets is that if you have a dozen variables and you want to have a new set with one of these variables pointing to a different location, you are not required to re-enter all this redundant data again. You can simply create a clone of your current set, this will duplicate all of your variables.<br />
<br />
Deleting a set also deletes all variables in that set (but not in another set). The "default" set is always present and cannot be deleted.<br />
<br />
== Custom Members Mini-Tutorial ==<br />
As stated above, writing <tt>$(#var.include)</tt> and <tt>$(#var)/include</tt> is exactly the same thing by default.<br />
So why would you want to write something as unintuitive as <tt>$(#var.include)</tt>?<br />
<br />
Let's take a standard Boost installation under Windows as an example. Generally, you would expect a fictional package <tt>ACME</tt> to have its include files under <tt>ACME/include</tt> and its libraries under <tt>ACME/lib</tt>. Optionally, it might place its headers into yet another subfolder called <tt>acme</tt>.<br />
Thus, after adding the correct paths to the compiler and linker options, you would expect to <tt>#include <acme/acme.h></tt> and link to <tt>libacme.a</tt> (or whatever it happens to be).<br />
<br />
Boost, however, installs headers into <tt>C:\Boost\include\boost-1_33_1\boost</tt> and its libraries under <tt>C:\Boost\lib</tt> by default. It seems impossible to get this under one hood without having to adjust everything on every new PC, especially if you have to work under Linux or some other OS, too.<br />
<br />
This is where the true power of global user variables is unveiled. When defining the value of the <tt>#boost</tt> variable, you go one step further than usual. You define the member <tt>include</tt> as <tt>C:\Boost\include\boost-1_33_1\boost</tt> and the member <tt>lib</tt> as <tt>C:\Boost\lib</tt>, respectively.<br />
Your projects using <tt>$(#boost.include)</tt> and <tt>$(#boost.lib)</tt> will magically work on every PC without any modifications. You don't need to know why, you don't want to know why.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Global_compiler_variables&diff=3063
Global compiler variables
2006-07-04T14:20:24Z
<p>Thomas: /* Constraints */</p>
<hr />
<div>[[Category:Application Development]]<br />
== Synopsis ==<br />
Working as a developer on a project which relies on 3rd party libraries involves a lot of unnecessary repetitive tasks, such as setting up build variables according to the local filesystem layout. In the case of project files, care must be taken to not accidentially commit a locally modified copy. If one does not pay attention, this can happen easily for example after changing a build flag to make a release build.<br />
<br />
The concept of global compiler variables is an unique new solution for Code::Blocks which addresses this problem.<br />
Global compiler variables allow you to set up a project once, and any number of developers using any number of different filesystem layouts will be able to compile and develop the project. No local layout information ever needs to be changed more than once.<br />
<br />
== Names and Members ==<br />
Global compiler variables in Code::Blocks are discriminated from [[per-project variables]] by a leading hash sign. Global compiler variables are structured; every variable consists of a ''name'' and an optional ''member''.<br />
Names are freely definable, while some of the members are built into the IDE. Although you can choose anything for a variable name in principle, it is advisable to pick a known identifier for common packages. This way, the amount of information that the user needs to provide is minimised. The Code::Blocks team provides a [[Recommended global variables|list of recommended variables]] for known packages.<br />
<br />
The member <tt>base</tt> resolves to the same value as the variable name uses without a member (alias).<br />
<br />
The members <tt>include</tt> and <tt>lib</tt> are by default aliases for ''base''<tt>/include</tt> and ''base''<tt>/lib</tt>, respectively. However, a user can redefine them if another setup is desired.<br />
<br />
It is generally recommended to use the syntax <tt>$(#variable.include)</tt> instead of <tt>$(#variable)/include</tt>, as it provides additional flexibility and is otherwise exactly identical in functionality (see [[Global_compiler_variables#Custom_Members_Mini-Tutorial|mini tutorial]]).<br />
<br />
The members <tt>cflags</tt> and <tt>lflags</tt> are empty by default and can be used to provide the ability to feed the same consistent set of compiler/linker flags to all builds on one machine.<br />
Beginning with revision 2664 (4 July 2006), Code::Blocks allows you to define custom variable members in addition to the builtin ones.<br />
<br />
<br />
[[Image:Gcv_ui.png]]<br />
<br />
<br />
== Constraints ==<br />
*Both set and global compiler variable <i>names</i> may not be empty, must not contain white space, must start with a letter and must consist of alphanumeric characters. Cyrillic or Chinese letters are <i>not</i> alphanumeric characters.<br />If Code::Blocks is given invalid character sequences as name, it may replace them without asking.<br />
*Every variable requires its base to be defined. Everything else is optional, but the base is absolutely mandatory. If you don't define a variable's base, it will not be saved (no matter what other fields you have defined).<br />
*You may not define a custom member that has the same name as a builtin member. Currently, the custom member will overwrite the builtin member, but in general, the behaviour for this case is undefined.<br />
*Variable and member values may contain <i>arbitrary</i> character sequences, subject to the following two constraints:<br />
**You may not define a variable by a value that references the same variable or any of its members<br />
**You may not define a member by a value that references the same member<br />
**You may not define a member or variable by a value that references the same variable or member through a cyclic dependency.<br />
Code::Blocks will detect the most obvious cases of recursive definitions (which may happen by accident), but it will not perform an excessive depth analysis of every possible abuse. If you enter crap, then crap is what you will get, you have been warned.<br />
<br />
<u>Examples:</u><br /><br />
defining <tt>wx.include</tt> as <tt>$(#wx)/include</tt> is redundant, but perfectly legal<br /><br />
defining <tt>wx.include</tt> as <tt>$(#wx.include)</tt> is illegal and will be detected by Code::Blocks<br /><br />
defining <tt>wx.include</tt> as <tt>$(#cb.lib)</tt> which again is defined as <tt>$(#wx.include)</tt> will create an infinite loop<br />
<br />
== Using Global Compiler Variables ==<br />
All you need to do to start using global compiler variables is to put them in your project! Yes, it is really that easy.<br />
<br />
When the IDE detects the presence of an unknown global variable, it will prompt you to enter its value. The value will be saved in your settings, so you never need to enter the information twice.<br />
<br />
If you need to modify or delete a variable at a later time, you can do so from the settings menu.<br />
<br />
<br />
<u>Example:</u><br />
<br />
[[Image:Globvarsdir.png]]<br />
<br />
The above image shows both per-procect and global variables. <tt>WX_CFG</tt> is defined in the project, but <tt>WX</tt> is a global user variable.<br />
<br />
== Variable Sets ==<br />
Sometimes, you want to use different versions of the same library, or you develop two branches of the same program. Although it is still possible to get around with a global compiler variable, it can become tedious. For this purpose, Code::Blocks supports variable <i>sets</i>. A variable set is an independent collection of variables identified by a name (set names have the same constraints as variable names).<br />
<br />
If you wish to switch to a different set of variables, you simply select a different set from the menu. Different sets are not required to have the same variables, and identical variables in different sets are not required to have the same values, or even the same custom members.<br />
<br />
Another positive thing about sets is that if you have a dozen variables and you want to have a new set with one of these variables pointing to a different location, you are not required to re-enter all this redundant data again. You can simply create a clone of your current set, this will duplicate all of your variables.<br />
<br />
Deleting a set also deletes all variables in that set (but not in another set). The "default" set is always present and cannot be deleted.<br />
<br />
== Custom Members Mini-Tutorial ==<br />
As stated above, writing <tt>$(#var.include)</tt> and <tt>$(#var)/include</tt> is exactly the same thing by default.<br />
So why would you want to write something as unintuitive as <tt>$(#var.include)</tt>?<br />
<br />
Let's take a standard Boost installation under Windows as an example. Generally, you would expect a fictional package <tt>ACME</tt> to have its include files under <tt>ACME/include</tt> and its libraries under <tt>ACME/lib</tt>. Optionally, it might place its headers into yet another subfolder called <tt>acme</tt>.<br />
Thus, after adding the correct paths to the compiler and linker options, you would expect to <tt>#include <acme/acme.h></tt> and link to <tt>libacme.a</tt> (or whatever it happens to be).<br />
<br />
Boost, however, installs headers into <tt>C:\Boost\include\boost-1_33_1\boost</tt> and its libraries under <tt>C:\Boost\lib</tt> by default. It seems impossible to get this under one hood without having to adjust everything on every new PC, especially if you have to work under Linux or some other OS, too.<br />
<br />
This is where the true power of global user variables is unveiled. When defining the value of the <tt>#boost</tt> variable, you go one step further than usual. You define the member <tt>include</tt> as <tt>C:\Boost\include\boost-1_33_1\boost</tt> and the member <tt>lib</tt> as <tt>C:\Boost\lib</tt>, respectively.<br />
Your projects using <tt>$(#boost.include)</tt> and <tt>$(#boost.lib)</tt> will magically work on every PC without any modifications. You don't need to know why, you don't want to know why.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Global_compiler_variables&diff=3061
Global compiler variables
2006-07-04T12:29:35Z
<p>Thomas: </p>
<hr />
<div>[[Category:Application Development]]<br />
== Synopsis ==<br />
Working as a developer on a project which relies on 3rd party libraries involves a lot of unnecessary repetitive tasks, such as setting up build variables according to the local filesystem layout. In the case of project files, care must be taken to not accidentially commit a locally modified copy. If one does not pay attention, this can happen easily for example after changing a build flag to make a release build.<br />
<br />
The concept of global compiler variables is an unique new solution for Code::Blocks which addresses this problem.<br />
Global compiler variables allow you to set up a project once, and any number of developers using any number of different filesystem layouts will be able to compile and develop the project. No local layout information ever needs to be changed more than once.<br />
<br />
== Names and Members ==<br />
Global compiler variables in Code::Blocks are discriminated from [[per-project variables]] by a leading hash sign. Global compiler variables are structured; every variable consists of a ''name'' and an optional ''member''.<br />
Names are freely definable, while some of the members are built into the IDE. Although you can choose anything for a variable name in principle, it is advisable to pick a known identifier for common packages. This way, the amount of information that the user needs to provide is minimised. The Code::Blocks team provides a [[Recommended global variables|list of recommended variables]] for known packages.<br />
<br />
The member <tt>base</tt> resolves to the same value as the variable name uses without a member (alias).<br />
<br />
The members <tt>include</tt> and <tt>lib</tt> are by default aliases for ''base''<tt>/include</tt> and ''base''<tt>/lib</tt>, respectively. However, a user can redefine them if another setup is desired.<br />
<br />
It is generally recommended to use the syntax <tt>$(#variable.include)</tt> instead of <tt>$(#variable)/include</tt>, as it provides additional flexibility and is otherwise exactly identical in functionality (see [[Global_compiler_variables#Custom_Members_Mini-Tutorial|mini tutorial]]).<br />
<br />
The members <tt>cflags</tt> and <tt>lflags</tt> are empty by default and can be used to provide the ability to feed the same consistent set of compiler/linker flags to all builds on one machine.<br />
Beginning with revision 2664 (4 July 2006), Code::Blocks allows you to define custom variable members in addition to the builtin ones.<br />
<br />
<br />
[[Image:Gcv_ui.png]]<br />
<br />
<br />
== Constraints ==<br />
*Both set and global compiler variable <i>names</i> may not be empty, must not contain white space, must start with a letter and must consist of alphanumeric characters. Cyrillic or Chinese letters are <i>not</i> alphanumeric characters.<br />If Code::Blocks is given invalid character sequences as name, it may replace them without asking.<br />
*Every variable requires its base to be defined. Everything else is optional, but the base is absolutely mandatory. If you don't define a variable's base, it will not be saved (no matter what other fields you have defined).<br />
*You may not define a custom member that has the same name as a builtin member. Currently, the custom member will overwrite the builtin member, but in generally, the behaviour for this case is undefined.<br />
*Variable and member values may contain <i>arbitrary</i> character sequences, subject to the following two constraints:<br />
**You may not define a variable by a value that references the same variable or any of its members<br />
**You may not define a member by a value that references the same member<br />
**You may not define a member or variable by a value that references the same variable or member through a cyclic dependency.<br />
Code::Blocks will detect the most obvious cases of recursive definitions (which may happen by accident), but it will not perform an excessive depth analysis of every possible abuse. If you enter crap, then crap is what you will get, you have been warned.<br />
<br />
<u>Examples:</u><br /><br />
defining <tt>wx.include</tt> as <tt>$(#wx)/include</tt> is redundant, but perfectly legal<br /><br />
defining <tt>wx.include</tt> as <tt>$(#wx.include)</tt> is illegal and will be detected by Code::Blocks<br /><br />
defining <tt>wx.include</tt> as <tt>$(#cb.lib)</tt> which again is defined as <tt>$(#wx.include)</tt> will create an infinite loop<br />
<br />
== Using Global Compiler Variables ==<br />
All you need to do to start using global compiler variables is to put them in your project! Yes, it is really that easy.<br />
<br />
When the IDE detects the presence of an unknown global variable, it will prompt you to enter its value. The value will be saved in your settings, so you never need to enter the information twice.<br />
<br />
If you need to modify or delete a variable at a later time, you can do so from the settings menu.<br />
<br />
<br />
<u>Example:</u><br />
<br />
[[Image:Globvarsdir.png]]<br />
<br />
The above image shows both per-procect and global variables. <tt>WX_CFG</tt> is defined in the project, but <tt>WX</tt> is a global user variable.<br />
<br />
== Variable Sets ==<br />
Sometimes, you want to use different versions of the same library, or you develop two branches of the same program. Although it is still possible to get around with a global compiler variable, it can become tedious. For this purpose, Code::Blocks supports variable <i>sets</i>. A variable set is an independent collection of variables identified by a name (set names have the same constraints as variable names).<br />
<br />
If you wish to switch to a different set of variables, you simply select a different set from the menu. Different sets are not required to have the same variables, and identical variables in different sets are not required to have the same values, or even the same custom members.<br />
<br />
Another positive thing about sets is that if you have a dozen variables and you want to have a new set with one of these variables pointing to a different location, you are not required to re-enter all this redundant data again. You can simply create a clone of your current set, this will duplicate all of your variables.<br />
<br />
Deleting a set also deletes all variables in that set (but not in another set). The "default" set is always present and cannot be deleted.<br />
<br />
== Custom Members Mini-Tutorial ==<br />
As stated above, writing <tt>$(#var.include)</tt> and <tt>$(#var)/include</tt> is exactly the same thing by default.<br />
So why would you want to write something as unintuitive as <tt>$(#var.include)</tt>?<br />
<br />
Let's take a standard Boost installation under Windows as an example. Generally, you would expect a fictional package <tt>ACME</tt> to have its include files under <tt>ACME/include</tt> and its libraries under <tt>ACME/lib</tt>. Optionally, it might place its headers into yet another subfolder called <tt>acme</tt>.<br />
Thus, after adding the correct paths to the compiler and linker options, you would expect to <tt>#include <acme/acme.h></tt> and link to <tt>libacme.a</tt> (or whatever it happens to be).<br />
<br />
Boost, however, installs headers into <tt>C:\Boost\include\boost-1_33_1\boost</tt> and its libraries under <tt>C:\Boost\lib</tt> by default. It seems impossible to get this under one hood without having to adjust everything on every new PC, especially if you have to work under Linux or some other OS, too.<br />
<br />
This is where the true power of global user variables is unveiled. When defining the value of the <tt>#boost</tt> variable, you go one step further than usual. You define the member <tt>include</tt> as <tt>C:\Boost\include\boost-1_33_1\boost</tt> and the member <tt>lib</tt> as <tt>C:\Boost\lib</tt>, respectively.<br />
Your projects using <tt>$(#boost.include)</tt> and <tt>$(#boost.lib)</tt> will magically work on every PC without any modifications. You don't need to know why, you don't want to know why.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=File:Gcv_ui.png&diff=3060
File:Gcv ui.png
2006-07-04T12:13:48Z
<p>Thomas: Global compiler variables UI</p>
<hr />
<div>Global compiler variables UI</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Comparison_of_wxSmith_features&diff=3043
Comparison of wxSmith features
2006-07-02T12:16:15Z
<p>Thomas: /* Features supported */</p>
<hr />
<div>[[Category:Code::Blocks Documentation]]<br />
Here is a list of [[wxSmith]] features when compared to other [[wikipedia:WxWidgets|wxWidgets]] [[wikipedia:Rapid application development|RAD]] solutions. <br />
Note that support for new features are added on a daily basis for some of these [[wikipedia:Rapid application development|RADs]].<br />
<br>Please update this list when something gets added.<br />
<br />
==General information==<br />
Basic general information about the [[wikipedia:Rapid application development|RADs]]: developer, license/price etc.<br />
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%;"<br />
|- style="background: #ececec; border: solid 1px gray;"<br />
! style="width:12em" | [[wikipedia:Rapid application development|RAD]]<br />
! Developer<br />
! Cost ([[wikipedia:United States dollar|USD]])<br />
! [[wikipedia:Open source|Open source]]<br />
! [[wikipedia:Software licence|Software licence]]<br />
|- style="border: solid 1px gray;"<br />
! style="text-align: left; background: #ececec;" | [[wxSmith]]<br />
| Bartlomiej Swiecki<br />
| Free<br />
| Yes<br />
| [[wikipedia:GNU General Public License|GPL]]<br />
|- style="border: solid 1px gray;"<br />
! style="text-align: left; background: #ececec;" | [[DialogBlocks]]<br />
| Julian Smart<br />
| Free (trial), $65 (normal), $30 (student)<br />
| No<br />
| [[wikipedia:Proprietary software|Proprietary]]<br />
|- style="border: solid 1px gray;"<br />
! style="text-align: left; background: #ececec;" | [[wxDesigner]]<br />
| Robert Roebling<br />
| Free (trial), $129 (normal), $29 (student)<br />
| No<br />
| [[wikipedia:Proprietary software|Proprietary]]<br />
|- style="border: solid 1px gray;"<br />
! style="text-align: left; background: #ececec;" | [[wxFormBuilder]]<br />
| José Antonio Hurtado, Juan Antonio Ortega<br />
| Free<br />
| Yes<br />
| [[wikipedia:GNU General Public License|GPL]]<br />
|- style="border: solid 1px gray;"<br />
! style="text-align: left; background: #ececec;" | [[VisualWx]]<br />
| {{dunno}}<br />
| Free<br />
| No<br />
| {{dunno}}<br />
|- style="background: #ececec; border: solid 1px gray;"<br />
! [[wikipedia:Rapid application development|RAD]]<br />
! Developer<br />
! Cost ([[wikipedia:United States dollar|USD]])<br />
! [[wikipedia:Open source|Open source]]<br />
! [[wikipedia:Software licence|Software licence]]<br />
|-<br />
|}<br />
<br />
==Widgets supported==<br />
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;"<br />
|- style="background: #ececec;"<br />
! style="width: 12em" | Widget<br />
! [[wxSmith]]<br />
! [[DialogBlocks]]<br />
! [[wxDesigner]]<br />
! [[wxFormBuilder]]<br />
! [[VisualWx]]<br />
|-<br />
! style="text-align: left; background: #ececec;" | wxBitmapButton<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxBoxSizer<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxButton<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|-<br />
! style="text-align: left; background: #ececec;" | wxCalendarCtrl<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxCheckBox<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxCheckListBox<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxChoice<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxChoicebook<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxComboBox<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxContextHelpButton<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxDatePickerCtrl<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxDynamicSashWindow<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxFlexGridSizer<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxGauge<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxGenericDirCtrl<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxGrid<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxGridBagSizer <br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxGridSizer<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxHtmlListBox<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxHtmlWindow<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxListbook<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxListBox<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxListCtrl<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxListView<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxMenu<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxNotebook<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxPanel<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxRadioBox<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxRadioButton<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxSashLayoutWindow<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxSashWindow<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxScrollBar<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxScrolledWindow<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxSlider<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxSpacer<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxSpinButton<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxSpinCtrl<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxSplitterWindow<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxStaticBitmap<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxStaticBox<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxStaticBoxSizer<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxStaticLine<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxStaticText<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxStatusBar<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxStdDialogButtonSizer<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxTextCtrl<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxToggleButton<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxToolbar<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxTreebook<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxTreeCtrl<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxVListBox<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxVScrolledWindow<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxWindow (Foreign)<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | wxWizardPage<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- style="background: #ececec;"<br />
! Widget<br />
! [[wxSmith]]<br />
! [[DialogBlocks]]<br />
! [[wxDesigner]]<br />
! [[wxFormBuilder]]<br />
! [[VisualWx]]<br />
|-<br />
|}<br />
<br />
==Contrib widgets supported==<br />
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;"<br />
|- style="background: #ececec;"<br />
! style="width: 12em" | Widget<br />
! [[wxSmith]]<br />
! [[DialogBlocks]]<br />
! [[wxDesigner]]<br />
! [[wxFormBuilder]]<br />
! [[VisualWx]]<br />
|-<br />
! style="text-align: left; background: #ececec;" | wxEditableListBox<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|-<br />
! style="text-align: left; background: #ececec;" | wxLEDNumberCtrl<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|-<br />
! style="text-align: left; background: #ececec;" | wxPlotWindow<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|-<br />
! style="text-align: left; background: #ececec;" | wxStyledTextCtrl<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- style="background: #ececec;"<br />
! Widget<br />
! [[wxSmith]]<br />
! [[DialogBlocks]]<br />
! [[wxDesigner]]<br />
! [[wxFormBuilder]]<br />
! [[VisualWx]]<br />
|-<br />
|}<br />
<br />
==Languages supported==<br />
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;"<br />
|- style="background: #ececec;"<br />
! style="width: 12em" | Feature<br />
! [[wxSmith]]<br />
! [[DialogBlocks]]<br />
! [[wxDesigner]]<br />
! [[wxFormBuilder]]<br />
! [[VisualWx]]<br />
|-<br />
! style="text-align: left; background: #ececec;" | C++ code output<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | Python code output<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | Lua code output<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | Ruby code output<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | Perl code output<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | C# code output<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | Basic code output<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
|- style="background: #ececec;"<br />
! Feature<br />
! [[wxSmith]]<br />
! [[DialogBlocks]]<br />
! [[wxDesigner]]<br />
! [[wxFormBuilder]]<br />
! [[VisualWx]]<br />
|-<br />
|}<br />
<br />
==Features supported==<br />
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;"<br />
|- style="background: #ececec;"<br />
! style="width: 12em" | Feature<br />
! [[wxSmith]]<br />
! [[DialogBlocks]]<br />
! [[wxDesigner]]<br />
! [[wxFormBuilder]]<br />
! [[VisualWx]]<br />
|- <br />
! style="text-align: left; background: #ececec;" | XRC input<br />
| {{yes}}{{refun|XRCnotworks}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | XRC output<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | XRC code loading<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{dunno}}<br />
|-<br />
! style="text-align: left; background: #ececec;" | [[Validators]]<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | [[Conditional UI]]<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | [[Event table and handler generation]]<br />
| {{partial}}<br />
| {{yes}}<br />
| {{partial}}<br />
| {{no}}<br />
| {{partial}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | [[Bitmaps support]]<br />
| {{no}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | [[English descriptions]]<br />
| {{no}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | [[Easy access to window pointers]]<br />
| {{yes}}<br />
| {{yes}}<br />
| {{no}}<br />
| {{no}}<br />
| {{dunno}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | [[Visually creating custom controls]]<br />
| {{partial}}<br />
| {{yes}}<br />
| {{partial}}<br />
| {{no}}<br />
| {{partial}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | [[Template controls]]<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | Sizer design<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
| {{yes}}<br />
|- <br />
! style="text-align: left; background: #ececec;" | Non-sizer design<br />
| {{partial}}<br />
| {{no}}<br />
| {{no}}<br />
| {{no}}<br />
| {{yes}}<br />
|- style="background: #ececec;"<br />
! Feature<br />
! [[wxSmith]]<br />
! [[DialogBlocks]]<br />
! [[wxDesigner]]<br />
! [[wxFormBuilder]]<br />
! [[VisualWx]]<br />
|-<br />
|}<br />
<br />
*{{note|XRCnotworks}} Currently, only one dialog resource per XRC file is imported.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Roadmap_for_version_1.0&diff=3022
Roadmap for version 1.0
2006-06-23T17:59:41Z
<p>Thomas: /* Version 1.0 RC 3 (Ephialtes) */</p>
<hr />
<div>[[Category:Code::Blocks Documentation]]<br />
==Version 1.0 (Pheidippides)==<br />
''August 2006''<br />
<br />
==Version 1.0 RC final (Athenades)==<br />
''Mid-July 2006''<br />
*No feature additions.<br />
*Regression and bug handling only.<br />
<br />
==Version 1.0 RC 3 (Ephialtes)==<br />
''Around end of June 2006''<br />
*[[Image:Chk.png]]Unicode support<br />
**[[Image:Chk.png]]User interface<br />
**[[Image:Chk.png]]Configuration system<br />
**[[Image:Chk.png]]Editor component<br />
**[[Image:Nop.png]]No fully automatic detection of document encoding<br />
*[[Image:Blk.png]]<s>Scripting support (Angelscript)</s> <i>abandoned due to lack of 64bit support)</i><br />
*[[Image:Blk.png]]Scripting support (Squirrel/Sq plus)<br />
**[[Image:Chk.png]]Watch scripts (see [[Debugger scripts]])<br />
**[[Image:Chk.png]]Build target scripts<br />
*[[Image:Chk.png]]Global user variables<br />
**[[Image:Chk.png]]Profile-dependent GUVs<br />
**[[Image:Chk.png]]Multiple variable sets<br />
**[[Image:Chk.png]]Custom variable definition<br />
*[[Image:Chk.png]]wxFlatNoteBook editors<br />
*[[Image:Chk.png]]wxAUI docking library<br />
*[[Image:Chk.png]]Context-sensitive layout switching<br />
*[[Image:Chk.png]]XML-based configuration system<br />
*[[Image:Blk.png]]XML-based compiler framework<br />
*[[Image:Blk.png]]Property-based build system<br />
*[[Image:Chk.png]]Improved configuration user interface<br />
*[[Image:Blk.png]]Automatic updates<br />
*[[Image:Blk.png]]Usability and stability fixes for code completion plugin <br />
*[[Image:Blk.png]]Regression and bug handling.<br />
<br />
==Version 1.0 RC 2 (Leonidas)==<br />
''25 October 2005''<br />
*Precompiled headers (PCH) support! (currently works only with GCC) <br />
*The source is now fully UNICODE-compatible! <br />
*The source is also fully 64-bit compatible! <br />
*Autoconf/automake build system is now used for non-windows platforms<br />
* New editor functionality<br />
**Find declaration<br />
**Open #include<br />
*Project wizard plugins<br />
*Support for SDCC<br />
*Better handling of modified files outside the IDE<br />
*Single file compilation<br />
*Find-in-Files for arbitrary paths/filemasks<br />
*All internal file formats are well-formed, valid XML<br />
*New plugins:<br />
**Code statistics: counts nr. of source lines, nr. of comment lines, etc. <br />
**CBProfiler: parses and displays the output of GProf, the GNU Profiler<br />
**SourceExporter: exports the active file to HTML/RTF/ODT<br />
*New lexers: <br />
**Fortran77 <br />
**NVidia CG<br />
**X-Base languages (Clipper, Foxpro) <br />
*New and improved project templates: <br />
**SDCC program <br />
**Irrlicht 3D Graphics Engine <br />
**Ogre 3D Graphics Engine <br />
**GLFW project (OpenGL FrameWork) <br />
**wxWidgets: static/dynamic unicode/ansi versions. <br />
<br />
<br />
==Version 1.0 RC 1-1 (Oedipus)==<br />
''2 August 2005''<br />
*Several critical bug fixes<br />
<br />
<br />
==Version 1.0 RC 1 (Laius)==<br />
''25 July 2005''<br />
*Compiler support for OpenWatcom <br />
*Per-target environment variables<br />
*Convenient "Start here" page<br />
*Improved gcc error parsing<br />
*Find in files functionality<br />
*Ability to add files to project recursively. <br />
*External dependency handling<br />
*Better import of foreign project files<br />
*Many GDB debugger updates<br />
*Numerous user interface improvements<br />
*New project templates<br />
**QT4. <br />
**Ogre3D. <br />
* Modular Syntax highlighting<br />
* Syntax highlighting support for:<br />
**C/C++ <br />
**Windows resources <br />
**HTML/XML/XSL<br />
**Lua scripts <br />
**GameMonkey scripts <br />
**Hitach H8 ASM</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Using_STLFilt_with_MinGW&diff=2941
Using STLFilt with MinGW
2006-05-23T07:00:00Z
<p>Thomas: /* Links */</p>
<hr />
<div>Welcome to the '''Sandbox''' where you can edit until your heart's content. Check out the 'edit' link at the top of this page to play around in here.<br />
<br />
== Italic Text ==<br />
<br />
Look at the ''italic text''.<br />
<br />
== Bold Text ==<br />
<br />
Look at the '''bold text'''.<br />
<br />
== Lists ==<br />
<br />
*Lists are easy.<br />
**Really easy.<br />
<br />
== Images ==<br />
<br />
Some images....<br />
<br />
[[Image:Chk.png]]<br />
[[Image:Nop.png]]<br />
<br />
== Links ==<br />
<br />
Links to other pages, external sites. etc<br />
<br />
Link to page in this wiki<br />
[[Sandbox]]<br />
<br />
Link with no title<br />
[http://www.google.com]<br />
<br />
Link with title<br />
[http://www.google.com The Google Search engine]<br />
<br />
Link to category<br />
[[Category:Installation/Build_Instructions]] -- this doesn't work. How do you do this properly??<br />
Like this: [[:Category:Installation/Build Instructions]]</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Variable_expansion&diff=2917
Variable expansion
2006-05-12T12:37:32Z
<p>Thomas: /* List of available builtins */</p>
<hr />
<div>[[Category:Application Development]]<br />
== Scope ==<br />
This article refers to builtin variables to be used in during the build process,<br />
using '''Code::Blocks revision 1996 and newer'''.<br/><br />
Older versions may not support all of the listed types.<br />
<br />
== Syntax ==<br />
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:<br />
<br />
<tt>$VARIABLE</tt>, <tt>$(VARIABLE)</tt>, <tt>${VARIABLE}</tt>, and <tt>%VARIABLE%</tt><br />
<br />
<br />
Variable names must consist of alphanumeric characters and are not case-sensitive. Variables starting with a single hash sign (<tt>#</tt>) are interpreted as [[global user variables]].<br />
The names listed below are interpreted as builtin types.<br />
<br />
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.<br />
Per-target definitions have precedence over per-project definitions.<br />
<br />
== List of available builtins ==<br />
<br />
<tt>$(PROJECT_FILENAME) $(PROJECT_FILE) $(PROJECTFILE)</tt><br/><br />
The filename of the currently compiling project.<br />
<br />
<tt>$(PROJECT_NAME)</tt><br/><br />
The name of the currently compiling project.<br />
<br />
<tt>$(PROJECT_DIR) $(PROJECTDIR) $(PROJECT_DIRECTORY)</tt><br/><br />
The common top-level directory of the currently compiling project.<br />
<br />
<tt>$(CODEBLOCKS) $(APP_PATH) $(APPPATH) $(APP-PATH)</tt><br/><br />
The path to the currently running instance of Code::Blocks<br />
<br />
<tt>$(DATAPATH) $(DATA_PATH) $(DATA-PATH)</tt><br/><br />
The 'shared' folder of the currently running instance of Code::Blocks<br />
<br />
<tt>$(PLUGINS)</tt><br/><br />
The plugins folder of the currently running instance of Code::Blocks<br />
<br />
<tt>$(ACTIVE_EDITOR_FILENAME)</tt><br/><br />
The filename of the file opened in the currently active editor.<br />
<br />
<tt>$(ALL_PROJECT_FILES)</tt><br/><br />
A string containing the names of all files in the current project.<br />
<br />
<tt>$(MAKEFILE)</tt><br/><br />
The filename of the makefile.<br />
<br />
<tt>$(FOOBAR_OUTPUT_FILE)</tt><br/><br />
A ''specific'' target's output file.<br />
<br />
<tt>$(FOOBAR_OUTPUT_DIR)</tt><br/><br />
A ''specific'' target's output directory.<br />
<br />
<tt>$(TARGET_OUTPUT_DIR)</tt><br/><br />
The ''current'' target's output directory.<br />
<br />
<tt>$(TARGET_NAME)</tt><br/><br />
The ''current'' target's name.<br />
<br />
<tt>$(LANGUAGE)</tt><br/><br />
The system language in human readable form.<br />
<br />
<tt>$(ENCODING)</tt><br/><br />
The character encoding in human readable form.<br />
<br />
<tt>$(ACTIVE_EDITOR_FILENAME)<br />$(ACTIVE_EDITOR_DIRNAME) $(ACTIVE_EDITOR_STEM) $(ACTIVE_EDITOR_EXT)</tt><br/><br />
The filename of the file being open in the active editor, its containing directory (relative to the common toplevel path), its base name (without extension), and its extension.<br />
<br />
<tt>$(TDAY)</tt><br/><br />
Current date in the form 20051228<br />
<br />
<tt>$(TODAY)</tt><br/><br />
Current date in the form 2005-12-28<br />
<br />
<tt>$(NOW)</tt><br/><br />
Timestamp in the form 2005-12-28-07.15<br />
<br />
<tt>$(NOW_L)</tt><br/><br />
Timestamp in the form 2005-12-28-07.15.45<br />
<br />
<tt>$(WEEKDAY)</tt><br/><br />
Human-readable day of the week ("Wednesday")<br />
<br />
<tt>$(TDAY_UTC) $(TODAY_UTC) $(NOW_UTC)</tt><br/><br />
<tt>$(NOW_L_UTC) $(WEEKDAY_UTC)</tt><br/><br />
These are identical to the preceding types, but are expressed relative to UTC.<br />
<br />
<tt>$(COIN)</tt><br/><br />
This variable tosses a virtual coin (once per invokation) and returns 0 or 1.<br />
<br />
<tt>$(RANDOM)</tt><br/><br />
A 16bit positive random number (0-65535)</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Announcement_for_plugins/patches&diff=2837
Announcement for plugins/patches
2006-04-18T09:32:07Z
<p>Thomas: /* Lexer/Templates announcements */</p>
<hr />
<div>=== HowTo announce a new plugin/patch or similar ===<br />
<br />
''Please read carefully:''<br />
<br />
This WiKi section is to announce:<br />
* a new plugin that is '''not''' within the contrib folder of the SVN repository<br />
* a patch that is '''not''' a bugfix or similar and/or will '''not''' be applied to the SVN repository (e.g. because it's very specific)<br />
* a new lexer/template that is '''not''' completed or approved and/or will '''not''' be added to the SVN<br />
<br />
If a plugin/patch/lexer/template is moved to the repository don't forget to remove it from here! This section is intended to '''collect''' the information about available plugins/patches/lexerers/templates in one place. So the announcement should be short and clear. It should (however) include at least the following content:<br />
* Name of the plugin/patch/lexer/template and purpose<BR><br />
* Version (state) and date of last update (or release in the first place)<BR><br />
* Link to a thread (to be created) in the developers (plugin) forum for discussion of features, bugs, wishlist etc.<BR><br />
* A link where the '''most up-to-date''' version can be downloaded (e.g. in the forum).<BR><br />
The best way may be to copy the section from the '''template''' plugin/patch/lexer/template and update it with your information. This will ensure consistency in the best way! Read the article [[How to add another announcement]] to read how to change the WiKi accordingly.<br />
<br />
=== Patch announcements ===<br />
<br />
So far there are no new patches.<br />
<br />
* [[Template for patch announcement]] (Read this before posting a new patch!)<br />
<br />
=== Plugin announcements ===<br />
<br />
These are the user-contributed plugins:<br />
<br />
* [[Replace in Files]] (MortenMacFly)<br />
* [[Tab versus Space]] (MortenMacFly)<br />
* [[Edit Project]] (Killerbot)<br />
* [[Matching Brace]] (Killerbot)<br />
* [[Mouse Drag Scrolling]] (Pecan)<br />
* [[Library Finder]] (byo)<br />
* [[Template for plugin announcement]] (Read this before posting a new plugin!)<br />
<br />
=== Lexer/Templates announcements ===<br />
<br />
* [[Template for lexer/template announcement]] (Read this before posting a new lexer/template!)</div>
Thomas
https://wiki.codeblocks.org/index.php?title=CodeBlocks:Article_Writing_Guidelines&diff=2702
CodeBlocks:Article Writing Guidelines
2006-04-10T17:28:39Z
<p>Thomas: </p>
<hr />
<div>;Conventions<br />
<br />
* Avoid large paragraphs. Break them up a bit.<br />
* Use a professional writing style. Don't get too silly in your writing. If you start warning your audience about anything or using a lot of cliches like 'just my $.02' you're bordering on silly.<br />
* Name sections according to content. The table of contents should show a map of where the discussion is going to go. <br />
<br />
''This is not a useful TOC:''<br />
<br />
<pre><br />
1 The Obligitory Warning<br />
2 Get your boilerplate ready<br />
3 The Meaty Part<br />
4 From Bad to Worse<br />
</pre><br />
<br />
; Accuracy<br />
<br />
* Use proper English, spelling, and grammar. Copy your text into Word to do a spelling & grammar check if need be.<br />
* Link your article with the articles or tutorials page only after it has been proof read.<br />
* Don't post code that you haven't actually compiled and run, nor code that you didn't write. Publishing someone else's original work usually constitutes infringment (unless explicitely permitted) and is actionable in most countries.<br />
* Post all code necessary. Provide both the inline code that you are commenting on, and also post the full code base for easy copying and pasting. <br />
<br />
; Guidelines<br />
<br />
* Write for multiple platforms. Code::Blocks has a wide audience. If you don't use another platform ask someone in the forums to cross check your work before posting. <br />
* Stay on topic. Pick one or a few related topics and write exclusively to that subject. If you have many ideas, make separate tutorials.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=CodeBlocks:Article_Writing_Guidelines&diff=2701
CodeBlocks:Article Writing Guidelines
2006-04-10T17:28:10Z
<p>Thomas: </p>
<hr />
<div>;Conventions<br />
<br />
* Avoid large paragraphs. Break them up a bit.<br />
* Use a professional writing style. Don't get too silly in your writing. If you start warning your audience about anything or using a lot of cliches like 'just my $.02' you're bordering on silly.<br />
* Name sections according to content. The table of contents should show a map of where the discussion is going to go. <br />
<br />
''This is not a useful TOC:''<br />
<br />
<pre><br />
1 The Obligitory Warning<br />
2 Get your boilerplate ready<br />
3 The Meaty Part<br />
4 From Bad to Worse<br />
</pre><br />
<br />
; Accuracy<br />
<br />
* Use proper English, spelling, and grammar. Copy your text into Word to do a spelling & grammar check if need be.<br />
* Link your article with the articles or tutorials page only after it has been proof read.<br />
* Don't post code that you haven't actually compiled and ran, nor code that you didn't write. Publishing someone else's original work usually constitutes infringment (unless explicitely permitted) and is actionable in most countries.<br />
* Post all code necessary. Provide both the inline code that you are commenting on, and also post the full code base for easy copying and pasting. <br />
<br />
; Guidelines<br />
<br />
* Write for multiple platforms. Code::Blocks has a wide audience. If you don't use another platform ask someone in the forums to cross check your work before posting. <br />
* Stay on topic. Pick one or a few related topics and write exclusively to that subject. If you have many ideas, make separate tutorials.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Building_From_Source&diff=2700
Building From Source
2006-04-10T17:22:54Z
<p>Thomas: </p>
<hr />
<div>'''Note:''' The official supported compiler to build Code::Blocks with is GCC (or MinGW). At the present time, GCC is also the only compiler known to successfully build Code::Blocks without modifications.<br />
<br />
''The build instructions on this page therefore relate exclusively to GCC.''<br />
<br />
For the latest stable code (all platforms), you can check out the source from BerliOS anonymous SVN.<br />
<br />
Example checkout:<br />
<br />
svn checkout svn://svn.berlios.de/codeblocks/trunk <br />
<br />
More detailed instrcutions [https://www.codeblocks.org/source_code.shtml here].<br />
<br />
== MS Windows ==<br />
<br />
=== Prerequisites ===<br />
<br />
=== Building ===<br />
<br />
== Linux ==<br />
<br />
=== Prerequisites ===<br />
<br />
=== Building ===<br />
<br />
== Mac OS X ==</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Global_compiler_variables&diff=2532
Global compiler variables
2006-03-27T19:30:23Z
<p>Thomas: /* Names and Members */</p>
<hr />
<div>[[Category:Code::Blocks features]]<br />
[[Category:Development]]<br />
== Synopsis ==<br />
Working as a developer on a project which relies on 3rd party libraries involves a lot of unnecessary repetitive tasks, such as setting up build variables according to the local filesystem layout. In the case of project files, care must be taken to not accidentially commit a locally modified copy.<br />
<br />
The concept of global compiler variables is an unique new solution for Code::Blocks which addresses this problem.<br />
Global compiler variables allow you to set up a project once, and any number of developers using any number of different filesystem layouts will be able to compile and develop the project. No local layout information needs to be changed more than once.<br />
<br />
== Names and Members ==<br />
Global compiler variables in Code::Blocks are discriminated from [[per-project variables]] by a leading hash sign. Global compiler variables are structured; every variable consists of a ''name'' and an optional ''member''.<br />
Names are freely definable, while the member structure is built into the IDE. Although you can choose anything for a variable name in principle, it is advisable to pick a known identifier for common packages. This way, the amount of information that the user needs to provide is minimised. The Code::Blocks team provides a [[Recommended global variables|list of recommended variables]] for known packages.<br />
<br />
The members <tt>dir</tt> and <tt>base</tt> resolve to the same value as the variable name uses without a member (alias).<br />
<br />
The members <tt>include</tt> and <tt>lib</tt> are by default aliases for ''base''<tt>/include</tt> and ''base''<tt>/lib</tt>, respectively. However, a user can redefine them if another setup is desired. It is recommended to ''always'' use the syntax <tt>$(#variable.include)</tt> instead of <tt>$(#variable)/include</tt>, as it provides additional flexibility and is otherwise exactly identical in functionality (see [[Global_compiler_variables#Custom_Members_Mini-Tutorial|mini tutorial]]).<br />
<br />
The members <tt>cflags</tt> and <tt>lflags</tt> are empty by default and can be used to provide the ability to feed the same consistent set of compiler/linker flags to all builds on one machine.<br />
<br />
== Using Global Compiler Variables ==<br />
All you need to do to start using global compiler variables is to put them in your project!<br />
<br />
When the IDE detects the presence of an unknown global variable, it will prompt you to enter its value. The value will be saved in your settings, so you never need to enter the information twice.<br />
<br />
If you need to modify or delete a variable at a later time, you can do so from the settings menu.<br />
<br />
<br />
<u>Example:</u><br />
<br />
[[Image:Globvarsdir.png]]<br />
<br />
The above image shows both per-procect and global variables. <tt>WX_CFG</tt> is defined in the project, but <tt>WX</tt> is a global user variable.<br />
<br />
<br />
== Custom Members Mini-Tutorial ==<br />
As stated above, writing <tt>$(#var.include)</tt> and <tt>$(#var)/include</tt> is exactly the same thing by default.<br />
So why would you want to write something as unintuitive as <tt>$(#var.include)</tt>?<br />
<br />
Let's take a standard Boost installation under Windows as an example. Generally, you would expect a fictional package <tt>ACME</tt> to have its include files under <tt>ACME/include</tt> and its libraries under <tt>ACME/lib</tt>. Optionally, it might place its headers into yet another subfolder called <tt>acme</tt>.<br />
Thus, after adding the correct paths to the compiler and linker options, you would expect to <tt>#include <acme/acme.h></tt> and link to <tt>libacme.a</tt> (or whatever it happens to be).<br />
<br />
Boost, however, installs headers into <tt>C:\Boost\include\boost-1_33_1\boost</tt> and its libraries under <tt>C:\Boost\lib</tt> by default. It seems impossible to get this under one hood without having to adjust everything on every new PC, especially if you have to work under Linux or some other OS, too.<br />
<br />
This is where the true power of global user variables is unveiled. When defining the value of the <tt>#boost</tt> variable, you go one step further than usual. You define the member <tt>include</tt> as <tt>C:\Boost\include\boost-1_33_1\boost</tt> and the member <tt>lib</tt> as <tt>C:\Boost\lib</tt>, respectively.<br />
Your projects using <tt>$(#boost.include)</tt> and <tt>$(#boost.lib)</tt> will magically work on every PC without any modifications. You don't need to know why, you don't want to know why.</div>
Thomas
https://wiki.codeblocks.org/index.php?title=Global_compiler_variables&diff=2531
Global compiler variables
2006-03-27T19:27:27Z
<p>Thomas: </p>
<hr />
<div>[[Category:Code::Blocks features]]<br />
[[Category:Development]]<br />
== Synopsis ==<br />
Working as a developer on a project which relies on 3rd party libraries involves a lot of unnecessary repetitive tasks, such as setting up build variables according to the local filesystem layout. In the case of project files, care must be taken to not accidentially commit a locally modified copy.<br />
<br />
The concept of global compiler variables is an unique new solution for Code::Blocks which addresses this problem.<br />
Global compiler variables allow you to set up a project once, and any number of developers using any number of different filesystem layouts will be able to compile and develop the project. No local layout information needs to be changed more than once.<br />
<br />
== Names and Members ==<br />
Global compiler variables in Code::Blocks are discriminated from [[per-project variables]] by a leading hash sign. Global compiler variables are structured; every variable consists of a ''name'' and an optional ''member''.<br />
Names are freely definable, while the member structure is built into the IDE. Although you can choose anything for a variable name in principle, it is advisable to pick a known identifier for common packages. This way, the amount of information that the user needs to provide is minimised. The Code::Blocks team provides a [[Recommended global variables|list of recommended variables]] for known packages.<br />
<br />
The members <tt>dir</tt> and <tt>base</tt> resolve to the same value as the variable name uses without a member (alias).<br />
<br />
The members <tt>include</tt> and <tt>lib</tt> are by default aliases for ''base''<tt>/include</tt> and ''base''<tt>/lib</tt>, respectively. However, a user can redefine them if another setup is desired. It is recommended to ''always'' use the syntax <tt>$(#variable.include)</tt> instead of <tt>$(#variable)/include</tt>, as it provides additional flexibility and is otherwise exactly identical in functionality (see mini tutorial at end of page).<br />
<br />
The members <tt>cflags</tt> and <tt>lflags</tt> are empty by default and can be used to provide the ability to feed the same consistent set of compiler/linker flags to all builds on one machine.<br />
<br />
== Using Global Compiler Variables ==<br />
All you need to do to start using global compiler variables is to put them in your project!<br />
<br />
When the IDE detects the presence of an unknown global variable, it will prompt you to enter its value. The value will be saved in your settings, so you never need to enter the information twice.<br />
<br />
If you need to modify or delete a variable at a later time, you can do so from the settings menu.<br />
<br />
<br />
<u>Example:</u><br />
<br />
[[Image:Globvarsdir.png]]<br />
<br />
The above image shows both per-procect and global variables. <tt>WX_CFG</tt> is defined in the project, but <tt>WX</tt> is a global user variable.<br />
<br />
<br />
== Custom Members Mini-Tutorial ==<br />
As stated above, writing <tt>$(#var.include)</tt> and <tt>$(#var)/include</tt> is exactly the same thing by default.<br />
So why would you want to write something as unintuitive as <tt>$(#var.include)</tt>?<br />
<br />
Let's take a standard Boost installation under Windows as an example. Generally, you would expect a fictional package <tt>ACME</tt> to have its include files under <tt>ACME/include</tt> and its libraries under <tt>ACME/lib</tt>. Optionally, it might place its headers into yet another subfolder called <tt>acme</tt>.<br />
Thus, after adding the correct paths to the compiler and linker options, you would expect to <tt>#include <acme/acme.h></tt> and link to <tt>libacme.a</tt> (or whatever it happens to be).<br />
<br />
Boost, however, installs headers into <tt>C:\Boost\include\boost-1_33_1\boost</tt> and its libraries under <tt>C:\Boost\lib</tt> by default. It seems impossible to get this under one hood without having to adjust everything on every new PC, especially if you have to work under Linux or some other OS, too.<br />
<br />
This is where the true power of global user variables is unveiled. When defining the value of the <tt>#boost</tt> variable, you go one step further than usual. You define the member <tt>include</tt> as <tt>C:\Boost\include\boost-1_33_1\boost</tt> and the member <tt>lib</tt> as <tt>C:\Boost\lib</tt>, respectively.<br />
Your projects using <tt>$(#boost.include)</tt> and <tt>$(#boost.lib)</tt> will magically work on every PC without any modifications. You don't need to know why, you don't want to know why.</div>
Thomas