Code::Blocks - User contributions [en]

Installing Code::Blocks from source on Linux

2023-07-08T05:20:53Z

MortenMacFly: Spelling

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]
These are instructions on how to build Code::Blocks under Linux. These instructions should work for all Linux distros, as we'll be installing from sources.

===Prerequisites===

In order to successfully compile Code::Blocks, the [http://en.wikipedia.org/wiki/WxWidgets wxWidgets] User Interface library must be installed. For most Linux users, this is maybe the only dependency not already installed. wxWidget can be used directly on top of the X server, in this case the variant of the wxWidget library is called wxX11. However this library [http://wiki.wxwidgets.org/WxWidgets_Compared_To_Other_Toolkits#Why_You_Shouldn.27t_Use_wxWidgets is sub-par compared to other toolkits and unstable]. Hence Code::Blocks uses wxGTK, the version of wxWidget based on GTK+. The exact requirement is libwxGTK-2.8.0 or later (2.8.3 is not recommended because of some troubles). This creates an additional dependency on GTK+, consider the following:

A possible implementation which does not exist:

''Code::Blocks -> wxWidgets (libwxX11) -> X''

Current Code::Blocks implementation:

''Code::Blocks -> '''wxWidgets (> libwxGTK2.8)''' -> '''GTK+ (> libgtk-x11-2.0)''' -> X''

This document helps you to install libwxGTK if necessary but does not cover the installation of GTK+. GTK+ is probably installed on your Linux anyway, so don't worry ;)

''Note:'' All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

=== Checking the presence of GTK+ library ===

Have a look in /usr/lib ( /usr/lib/x86_64-linux-gnu for 64 bits) for something like "libgtk-x11-2.0.so" (Note the library must be 2.0 minimum). Alternatively, do a search with your package manager or go to your Linux distribution forum for help. If you don't want to loose time, you can even forget this check since there is a good probability that everything is already installed.

===Library wxGTK installation===

==== Checking the presence of libwxGTK library ====

In your package manager, look for 'libwxgtk' keyword and verify that '''all''' libwxgtk2.8 stuffs are installed. If you find the libraries uninstalled, just '''install them and go directly to [https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux#Code::Blocks_installation Code::Blocks installation]'''.

Alternatively you can do the same in the command line (the following is an example, there may be more than two packages):

<pre>$ ls /usr/lib/libwx_gtk* //to verify the presence
$ sudo apt-get install libwxgtk2.8-dev
$ sudo apt-get install libwxgtk2.8-0</pre>

If you don't find any packages you must install the library from source as described below, and you can redo this check afterwards to verify that the installation worked correctly.

''Note for Debian and Ubuntu users:'' You can use

<pre>$ update-alternatives --config wx-config</pre>

to see which version of libwx is there or not and currently active.

And, Debian and Ubuntu user can use this to add a value to the list of choices

<pre>$ update-alternatives --install /usr/bin/wx-config wx-config /opt/wx/2.8/bin/wx-config 50</pre>

====Getting wxGTK sources====

Visit the [http://www.wxwidgets.org wxWidgets web site]. Click the "Download" button at the top of the page. Under wxWidgets 2.8.7 downloads, select wxGTK. Save the file in <tt>~/devel</tt>. After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.8.7.tar.gz</pre>

Switch to the wxGTK directory:

<pre>cd wxGTK-2.8.7</pre>

====Building wxWidgets====

Here we will create a separate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure:

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.8 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
su
make install
exit

Add /opt/wx/2.8/bin to the PATH (if your shell is bash then edit /etc/profile or ~/.bash_profile)
(On ''Suse 10.1'' edit /etc/profile.local, it will only be available after a new login). An example PATH:
export PATH=/usr/bin:/opt/wx/2.8/bin:$PATH

Add /opt/wx/2.8/lib to /etc/ld.so.conf (nano /etc/ld.so.conf), then run:
ldconfig
source /etc/profile

That's it. Now the linker will look in /opt/wx/2.8/lib for wx libraries and you will have a monolithic shared library unicode build.

To check that things are working, type:
wx-config --prefix
which should give you /opt/wx/2.8
wx-config --libs
which should have at least:
-L/opt/wx/2.8/lib -lwx_gtk2-2.8
but can contain other flags as well.
which wx-config
should return /opt/wx/2.8/bin/wx-config

===Code::Blocks installation===

====Getting Code::Blocks sources====

You can get Code::Blocks source code [https://www.codeblocks.org/downloads/25 from the website as a tarball] or from the [https://www.codeblocks.org/downloads/7 SVN repository] (this second method is described below).

=====From SVN repository=====
NOTICE: The SourceForge CVS is no longer used although it still exists.

Enter your development directory:
<pre>cd ~/devel</pre>

Then checkout the source using one of [https://www.codeblocks.org/downloads/7 these] methods. This will create the directory <tt>trunk</tt>. Change to the source code directory, by issuing the following command:

<pre>cd trunk</pre>

If you are a ''Gentoo'' user at this point, please see [[Compiling_Code::Blocks_in_Gentoo]].

Before beginning, it is often a good idea to check you have recent versions of autoconf and automake - repositories versions are not always recent enough. (if you do not have automake, then you will get "cannot find aclocal" error). If you're compiling the svn trunk versions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks. In short, these commands build Code::Blocks from sources ''and'' installs it:
<pre> ./bootstrap
./configure
make
make install
</pre>

The long story is as follows: First run:
<pre> ./bootstrap</pre>

This sets up the configure script and its dependencies. It only needs to be run once (after downloading the source from svn).

'''If you get errors like (...):'''
./bootstrap: libtoolize: not found
...then install the "libtool" package using your package manager.

./bootstrap: 64: ./bootstrap: aclocal: not found
...then the "autoconf" and "automake" package using your package manager.

bad interpreter: File not found
...then there exists a problem with DOS line-endings, for example if you cross compile to a Windows partition. Simply check-out a fresh copy of CodeBlocks from SVN.
 
Or, instead of downloading from SVN, you might consider using the little command line tool [http://dos2unix.sourceforge.net/ dos2unix], which normally comes with most distributions.
 

(".infig.status: error: cannot find input file: Makefile")
...(configure aborts with some unspecific error messagelike that), then you might consider also running dos2unix bootstrap acinclude.m4 codeblocks.pc.in configure.in Makefile.am before running bootstrap. Once you've run the bootstrap script, jump to next step.

aclocal:configure.in:61: warning: macro `AM_OPTIONS_WXCONFIG' not found in library
...then aclocal is having trouble finding the wxWidgets .m4 files. You can do one of two things:
To just get bootstrap to find the path this time do:
<pre>export ACLOCAL_FLAGS="-I `wx-config --prefix`/share/aclocal"</pre> 

To change the aclocal search path more permanently do:
echo `wx-config --prefix`/share/aclocal >> /usr/share/aclocal/dirlist
Then aclocal will also search somewhere like /opt/wx/2.8/share/aclocal

'''''Note for Ubuntu users:''''' The above is not the correct way to fix the AM_* errors. Rather, you only need to install the package named "wx-common" (Universe repository).

The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
...then this can be solved by something like:
ACLOCAL_FLAGS="-I /usr/share/aclocal" ./bootstrap
(...maybe adopting the path, so use `wx-config --prefix` is necessary.)

====Installing Code::Blocks sources====
You can read the BUILD file included in the source, but everything is very straightforward. Do:
<pre> ./configure
make
make install</pre>

You may need to run make install with super user rights, in that case use:
<pre> sudo make install</pre>
...for the last step.

If you have multiple versions of wxWidgets installed or kept them in place, you can use:
./configure --with-wx-config=/path/to/wx-config

'''Note:''' The Nassi Shneiderman plugin (part of the contrib plugins) has a dependency on [http://www.boost.org boost] which is needed to compile this plugin. Boost does not need to be compiled therefore. It is not checked for the existing of boost at the moment (except for debian build-system, there it is a build-dependency), so if you configure C::B to be build without Nassi Schneiderman, it should not lead to problems in case you don't have/want boost.

To uninstall you can later run:
make uninstall

If you want to recompile everything, first run:
<pre> make clean
make distclean
make clean-bin
make clean-zipfiles</pre>
and then follow the above sequence for installing.

By default, CodeBlocks will install to /usr/local. If you want it in its own tree (so you can have multiple versions of CodeBlocks, each in its own subdirectory of /opt) replace the above ./configure command with:
<pre> ./configure --prefix=/opt/codeblocks-svn</pre>
or similar. Then you can later install a different build like:
<pre> ./configure --prefix=/opt/codeblocks2-svn</pre>
followed by 'make && make install' as usual.

By default, CodeBlocks will not compile the contributed plugins from SVN. If you want to compile / install them too, replace the above ./configure command with:
<pre> ./configure --with-contrib-plugins=all</pre>
followed by 'make && make install' as usual.

To see a list of other options available for configuring the build of CodeBlocks do:
<pre> ./configure --help</pre>

To compile under ''Gentoo'', use:
<pre> ./configure --with-wx-config=wx-config-2.8</pre>

====Resolving runtime issues====

When running Code::Blocks after the installation it might happen, that the system complains:
codeblocks: error while loading shared libraries: libcodeblocks.so.0: cannot open shared object file: No such file or directory
In that case make sure the library path where the Code::Blocks libraries where installed into is "known" to the system. For example: On Ubuntu using a default build process on a clean system will install the Code::Blocks executables to /use/local/bin and the libraries to /usr/local/lib. The latter is usually not known to a "clean" Ubuntu system. To add it to the search path for libraries do the following (as root / using sudo respectively):
Add the following line to the file /etc/ld.so.conf:
/usr/local/lib
...and run:
ldconfig
That's it - Code::Blocks should now work just fine as all libraries are being found.

Note that for both you may need super user rights again - so use the sudo command as needed.

Creating a patch to submit (Patch Tracker)

2022-08-19T06:09:01Z

MortenMacFly: /* Patch submission */

[[Category:Developer Documentation]]
== Introduction ==
You want to contribute to Code::Blocks? - Thank you! That is really appreciated. Hence you can help us even more if you read the following paragraphs carefully.

First of all please make sure the feature you are implementing is not already implemented in the "nightly builds" of Code::Blocks ([/index.php/board,20.0.html /index.php/board,20.0.html]). Furthermore browse through the list of available patches at the Code::Blocks project page at SourceForge (see section "Patch submission" below on how to gain access). If you are unsure, don't hesitate to ask in the forum ([ ]) for advise.

You can make it easier for the developers to integrate your patches if you follow the advices of this page. Patches can be created in different formats. The format that is used by Code::Blocks is called a "unified diff". Hence 3rd party tools may still create a different patch format although it may be labelled as "unified diff". To avoid unnecessary incompatibilities the best way to provide a patch is to '''use the Subversion (SVN) diff''' (using the command line tool or a SVN GUI application).

== What is required? ==
Not too much, you might already have the required tools installed.
You'll need a subversion client software. You can download a current version for your OS at the Subversion project webpage here: [http://subversion.tigris.org http://subversion.tigris.org]. If you want to apply or test your patches you'll also need either '''svn''' version ≥ 1.7.0 or the '''patch''' program; you can download patch and find more information about it at the [http://www.gnu.org/software/patch/ GNU patch website].

It is a good idea to apply your code to the most up-to-date sources of Code::Blocks as they are available at the SVN repository. You'll find the instructions how to obtain the sources here: [https://www.codeblocks.org/downloads/7 https://www.codeblocks.org/downloads/7]. Once you've created your local sandbox you can start integrating your changes into it. Thus you may modify existing files or add new ones. When you have finished please make sure you've verified your implementation (feature(s)) work properly. Now it's time to create the patch.

== Patch creation ==
If you have added new files you first have to register them with your sandbox. Thus go into the directory you've added new files and type at the command line:
: <tt>svn add filename(s)</tt>
...whereas "filename(s)" needs to be replaced with the files you've added. Of course if you are not using the command line version of SVN you can easily use the "Add" feature of your prefered SVN GUI. If you've completed adding all your new files to your sandbox you are ready to create the patch.

First of all go to the top-level directory of your sandbox (the first directory that has a hidden ".svn" folder with content). This is done because the patch file generated by the following command is relative to the directory where it's performed. This is the command to create the patch file:
: <tt>svn diff > my.patch</tt>

You can change the name of the patch (''my.patch'' in the example) with a more descriptive name but make sure you leave the file extension ".patch" as this avoids conflicts while submitting the patch. The creation of the ''difference file'' (the patch file) may take some time, please be patient.

Once the patch file is created please make sure it contains content! Otherwise make sure you followed the steps above or ask in the forum ([https://forums.codeblocks.org/index.php/board,7.0.html<nowiki>]) for support.</nowiki>

''Note: if the created patch is much larger than expected (it should be similar in size to the amount of code you changed/added) it is likely that extraneous white space changes are being picked up. In this case, please use the following command to create the patch file:''
: <tt>svn diff -x -w > my.patch</tt>

If you are using git or git-svn and sending to someone with an svn setup, the output can be more easily handled with either [https://forums.codeblocks.org/index.php/topic,19391.msg132530.html#msg132530<nowiki>] or one of</nowiki>
: <tt>git diff --no-prefix > my.patch</tt>
: <tt>svn patch my.patch --strip 1</tt>

=== Patch application and testing ===
Most Subversion front-end UI tools (like TortoiseSVN or SmartSVN) have an option to apply this patch files directly.

If you are using svn version ≥ 1.7.0, the command:
:<tt>svn patch my.patch</tt>

...will perform some checks and then will patch your files using the difference information saved in the patch file (''my.patch'' in the example).

If you only need the command line without SVN tooling (why would you do so?), then in order to apply a patch you need the patch program ([http://gnuwin32.sourceforge.net/packages/patch.htm Windows] [http://savannah.gnu.org/projects/patch/ Linux]). Make sure you are in the same directory the patch was created and then type the following command:
: <tt>patch --unified --strip=0 --forward --input=my.patch</tt>

'''Important note:''' If you are working under Windows you may have to convert the patch file to DOS line-ending format. You can do that using "unix2dos my.patch".

== Patch submission ==
By now you are ready to submit your work to the Patch Tracker at [https://sourceforge.net/p/codeblocks/tickets/?source=navbar Tickets] - the developer platform for Code::Blocks. If you haven't done so already, you need to register with Sourceforge to gain the right to submit patches to projects. The membership is free and appreciated. Select the "Tickets" section ([https://sourceforge.net/p/codeblocks/tickets/?source=navbar Tickets]) of the Code::Blocks project page. Click on "Submit A Patch" and fill out the form that appears. For now you only need to select a category for your patch, a '''descriptive''' summary and the patch itself. Make sure you enable the checkbox "Upload Patch" and provide the patch file you've just created. Then you are ready for submission - click on the "Submit patch" button on the bottom of the page.

You should now see the current list of patches with your patch at the top. Please note you can add additional comments or updates to your patch by simply clicking on the patch in the list and fill out the form that appears.

'''Thank you very much for your submission!'''

Creating a patch to submit (Patch Tracker)

2022-08-19T06:07:39Z

MortenMacFly: /* Patch creation */

[[Category:Developer Documentation]]
== Introduction ==
You want to contribute to Code::Blocks? - Thank you! That is really appreciated. Hence you can help us even more if you read the following paragraphs carefully.

First of all please make sure the feature you are implementing is not already implemented in the "nightly builds" of Code::Blocks ([/index.php/board,20.0.html /index.php/board,20.0.html]). Furthermore browse through the list of available patches at the Code::Blocks project page at SourceForge (see section "Patch submission" below on how to gain access). If you are unsure, don't hesitate to ask in the forum ([ ]) for advise.

You can make it easier for the developers to integrate your patches if you follow the advices of this page. Patches can be created in different formats. The format that is used by Code::Blocks is called a "unified diff". Hence 3rd party tools may still create a different patch format although it may be labelled as "unified diff". To avoid unnecessary incompatibilities the best way to provide a patch is to '''use the Subversion (SVN) diff''' (using the command line tool or a SVN GUI application).

== What is required? ==
Not too much, you might already have the required tools installed.
You'll need a subversion client software. You can download a current version for your OS at the Subversion project webpage here: [http://subversion.tigris.org http://subversion.tigris.org]. If you want to apply or test your patches you'll also need either '''svn''' version ≥ 1.7.0 or the '''patch''' program; you can download patch and find more information about it at the [http://www.gnu.org/software/patch/ GNU patch website].

It is a good idea to apply your code to the most up-to-date sources of Code::Blocks as they are available at the SVN repository. You'll find the instructions how to obtain the sources here: [https://www.codeblocks.org/downloads/7 https://www.codeblocks.org/downloads/7]. Once you've created your local sandbox you can start integrating your changes into it. Thus you may modify existing files or add new ones. When you have finished please make sure you've verified your implementation (feature(s)) work properly. Now it's time to create the patch.

== Patch creation ==
If you have added new files you first have to register them with your sandbox. Thus go into the directory you've added new files and type at the command line:
: <tt>svn add filename(s)</tt>
...whereas "filename(s)" needs to be replaced with the files you've added. Of course if you are not using the command line version of SVN you can easily use the "Add" feature of your prefered SVN GUI. If you've completed adding all your new files to your sandbox you are ready to create the patch.

First of all go to the top-level directory of your sandbox (the first directory that has a hidden ".svn" folder with content). This is done because the patch file generated by the following command is relative to the directory where it's performed. This is the command to create the patch file:
: <tt>svn diff > my.patch</tt>

You can change the name of the patch (''my.patch'' in the example) with a more descriptive name but make sure you leave the file extension ".patch" as this avoids conflicts while submitting the patch. The creation of the ''difference file'' (the patch file) may take some time, please be patient.

Once the patch file is created please make sure it contains content! Otherwise make sure you followed the steps above or ask in the forum ([https://forums.codeblocks.org/index.php/board,7.0.html<nowiki>]) for support.</nowiki>

''Note: if the created patch is much larger than expected (it should be similar in size to the amount of code you changed/added) it is likely that extraneous white space changes are being picked up. In this case, please use the following command to create the patch file:''
: <tt>svn diff -x -w > my.patch</tt>

If you are using git or git-svn and sending to someone with an svn setup, the output can be more easily handled with either [https://forums.codeblocks.org/index.php/topic,19391.msg132530.html#msg132530<nowiki>] or one of</nowiki>
: <tt>git diff --no-prefix > my.patch</tt>
: <tt>svn patch my.patch --strip 1</tt>

=== Patch application and testing ===
Most Subversion front-end UI tools (like TortoiseSVN or SmartSVN) have an option to apply this patch files directly.

If you are using svn version ≥ 1.7.0, the command:
:<tt>svn patch my.patch</tt>

...will perform some checks and then will patch your files using the difference information saved in the patch file (''my.patch'' in the example).

If you only need the command line without SVN tooling (why would you do so?), then in order to apply a patch you need the patch program ([http://gnuwin32.sourceforge.net/packages/patch.htm Windows] [http://savannah.gnu.org/projects/patch/ Linux]). Make sure you are in the same directory the patch was created and then type the following command:
: <tt>patch --unified --strip=0 --forward --input=my.patch</tt>

'''Important note:''' If you are working under Windows you may have to convert the patch file to DOS line-ending format. You can do that using "unix2dos my.patch".

== Patch submission ==
By now you are ready to submit your work to the Patch Tracker at [https://sourceforge.net/p/codeblocks/tickets/?source=navbar Tickets] - the developer platform for Code::Blocks. If you haven't done so already, you need to register with Sourceforge to gain the right to submit patches to projects. The membership is free and appreciated. Select the "Tickests" section ([https://sourceforge.net/p/codeblocks/tickets/?source=navbar Tickets]) of the Code::Blocks project page. Click on "Submit A Patch" and fill out the form that appears. For now you only need to select a category for your patch, a '''descriptive''' summary and the patch itself. Make sure you enable the checkbox "Upload Patch" and provide the patch file you've just created. Then you are ready for submission - click on the "Submit patch" button on the bottom of the page.

You should now see the current list of patches with your patch at the top. Please note you can add additional comments or updates to your patch by simply clicking on the patch in the list and fill out the form that appears.

'''Thank you very much for your submission!'''

Creating a patch to submit (Patch Tracker)

2022-08-19T06:05:30Z

MortenMacFly: Updated Instrcutions

[[Category:Developer Documentation]]
== Introduction ==
You want to contribute to Code::Blocks? - Thank you! That is really appreciated. Hence you can help us even more if you read the following paragraphs carefully.

First of all please make sure the feature you are implementing is not already implemented in the "nightly builds" of Code::Blocks ([/index.php/board,20.0.html /index.php/board,20.0.html]). Furthermore browse through the list of available patches at the Code::Blocks project page at SourceForge (see section "Patch submission" below on how to gain access). If you are unsure, don't hesitate to ask in the forum ([ ]) for advise.

You can make it easier for the developers to integrate your patches if you follow the advices of this page. Patches can be created in different formats. The format that is used by Code::Blocks is called a "unified diff". Hence 3rd party tools may still create a different patch format although it may be labelled as "unified diff". To avoid unnecessary incompatibilities the best way to provide a patch is to '''use the Subversion (SVN) diff''' (using the command line tool or a SVN GUI application).

== What is required? ==
Not too much, you might already have the required tools installed.
You'll need a subversion client software. You can download a current version for your OS at the Subversion project webpage here: [http://subversion.tigris.org http://subversion.tigris.org]. If you want to apply or test your patches you'll also need either '''svn''' version ≥ 1.7.0 or the '''patch''' program; you can download patch and find more information about it at the [http://www.gnu.org/software/patch/ GNU patch website].

It is a good idea to apply your code to the most up-to-date sources of Code::Blocks as they are available at the SVN repository. You'll find the instructions how to obtain the sources here: [https://www.codeblocks.org/downloads/7 https://www.codeblocks.org/downloads/7]. Once you've created your local sandbox you can start integrating your changes into it. Thus you may modify existing files or add new ones. When you have finished please make sure you've verified your implementation (feature(s)) work properly. Now it's time to create the patch.

== Patch creation ==
If you have added new files you first have to register them with your sandbox. Thus go into the directory you've added new files and type at the command line:
: <tt>svn add filename(s)</tt>
...whereas "filename(s)" needs to be replaced with the files you've added. Of course if you are not using the command line version of SVN you can easily use the "Add" feature of your prefered SVN GUI. If you've completed adding all your new files to your sandbox you are ready to create the patch.

First of all go to the top-level directory of your sandbox (the first directory that has a hidden ".svn" folder with content). This is done because the patch file generated by the following command is relative to the directory where it's performed. This is the command to create the patch file:
: <tt>svn diff > my.patch</tt>

You can change the name of the patch (''my.patch'' in the example) with a more descriptive name but make sure you leave the file extension ".patch" as this avoids conflicts while submitting the patch. The creation of the ''difference file'' (the patch file) may take some time, please be patient.

Once the patch file is created please make sure it contains content! Otherwise make sure you followed the steps above or ask in the forum ([ ]) for support.

''Note: if the created patch is much larger than expected (it should be similar in size to the amount of code you changed/added) it is likely that extraneous white space changes are being picked up. In this case, please use the following command to create the patch file:''
: <tt>svn diff -x -w > my.patch</tt>

If you are using git or git-svn and sending to someone with an svn setup, the output can be more easily handled with either [/index.php/topic,19391.msg132530.html#msg132530 this script] or one of
: <tt>git diff --no-prefix > my.patch</tt>
: <tt>svn patch my.patch --strip 1</tt>

=== Patch application and testing ===
Most Subversion front-end UI tools (like TortoiseSVN or SmartSVN) have an option to apply this patch files directly.

If you are using svn version ≥ 1.7.0, the command:
:<tt>svn patch my.patch</tt>

...will perform some checks and then will patch your files using the difference information saved in the patch file (''my.patch'' in the example).

If you only need the command line without SVN tooling (why would you do so?), then in order to apply a patch you need the patch program ([http://gnuwin32.sourceforge.net/packages/patch.htm Windows] [http://savannah.gnu.org/projects/patch/ Linux]). Make sure you are in the same directory the patch was created and then type the following command:
: <tt>patch --unified --strip=0 --forward --input=my.patch</tt>

'''Important note:''' If you are working under Windows you may have to convert the patch file to DOS line-ending format. You can do that using "unix2dos my.patch".

== Patch submission ==
By now you are ready to submit your work to the Patch Tracker at [https://sourceforge.net/p/codeblocks/tickets/?source=navbar Tickets] - the developer platform for Code::Blocks. If you haven't done so already, you need to register with Sourceforge to gain the right to submit patches to projects. The membership is free and appreciated. Select the "Tickests" section ([https://sourceforge.net/p/codeblocks/tickets/?source=navbar Tickets]) of the Code::Blocks project page. Click on "Submit A Patch" and fill out the form that appears. For now you only need to select a category for your patch, a '''descriptive''' summary and the patch itself. Make sure you enable the checkbox "Upload Patch" and provide the patch file you've just created. Then you are ready for submission - click on the "Submit patch" button on the bottom of the page.

You should now see the current list of patches with your patch at the top. Please note you can add additional comments or updates to your patch by simply clicking on the patch in the list and fill out the form that appears.

'''Thank you very much for your submission!'''

Main Page

2019-04-13T04:36:23Z

MortenMacFly: Reverted edits by MortenMacFly (talk) to last revision by Alpha

__NOEDITSECTION__ __NOTOC__
{{Layout_box1|1=
[[Image:cb_splash.png|left]]
'''Welcome to the official Wiki for Code::Blocks''' 
[https://www.codeblocks.org Code::Blocks] is a free, open-source, cross-platform [[wikipedia:Integrated Development Environment|IDE]]. Using a plugin architecture, its capabilities and features are defined by the provided plugins. 
Currently, [https://www.codeblocks.org Code::Blocks] is oriented towards C/C++/Fortran.
The Code::Blocks team does not take responsibility for the content nor accuracy of these pages.

Wiki Editors: In order to login to edit pages, you must create an account on the [/ forums]. Use the same username and password for the wiki. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

{|width="100%" background-color="transparent"
|width="60%" valign="top"|


<div style="background-color: #dfeefb; border: 1px dotted #010101; margin: 5px; padding: 5px;">
{|align="center" style="background:transparent" cellspacing="5"

|valign="top" align="center" colspan="2"|
=== How do I... ===

|-

|align="center"|
'''[[Installing_Code::Blocks|...install Code::Blocks?]]''' 

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] ·
[[Installing_Code::Blocks#Ubuntu|Ubuntu]] ·
[[Installing_Code::Blocks#Mac_OS_X|Mac OS X]] ·
[[Installing_Code::Blocks#Fedora|Fedora]] ·
[[Installing_Code::Blocks|more...]]


|align="center"|
'''[[Installing_a_supported_compiler|...set up a compiler in Code::Blocks?]]''' 

[[Installing_a_supported_compiler#MinGW.2FGCC|MinGW]] ·
[[Installing_a_supported_compiler#Microsoft_Visual_C.2B.2B|MS Visual C++]] ·
[[Installing_a_supported_compiler|more...]]


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

|align="center"|
'''[[User_documentation#Third-party_libraries|...use a 3rd-party library?]]''' 

[[Using_wxWidgets|wxWidgets]] ·
[[Using_Boost|Boost]] ·
[[Using_SDL_with_Code::Blocks|SDL]] ·
[[User_documentation#Third-party_libraries|more...]]


|}
</div>

{{Layout_box3|1=
== Table of Contents ==
''Main article: [[Code::Blocks Documentation]]''

=== [[User documentation]] ===
:Articles for Code::Blocks users

=== [[FAQ]] ===
:Frequently Asked Questions

=== [[Feature List]] ===
:An index of Code::Blocks' useful features

=== [[Code::Blocks Plugins]] ===
:Plugins extend Code::Blocks' functionality

=== [[Off-site documentation]] ===
:Links to external documentation

=== [[Developer documentation]] ===
:Articles for developers of Code::Blocks itself
}}

|width="40%" valign="top"|

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/26 16.01]
* [/index.php?board=20.0 Nightly builds] (updated each night)
* [[Compiled_packages_of_Code::Blocks|Official and third-party binaries]] (for various distributions)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3ABug_Report+or+_type%3AUndefined bugs] or browse [http://alpha0010.github.io/cb-history/bugs.html old bugs]
* '''Features''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3AFeature_Request+or+_type%3AUndefined features] or browse [http://alpha0010.github.io/cb-history/features.html old features]
* '''Patches''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3APatch+or+_type%3AUndefined patches] or browse [http://alpha0010.github.io/cb-history/patches.html old patches]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [http://www.mingw.org MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore and PowerPC GCC] (Win32, Linux)
* [http://developer.apple.com/tools/ Apple GCC (Xcode)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [http://msdn.microsoft.com/vstudio/express/visualc/download/ Microsoft Visual C++ 2005] (Win32)
* [http://edn.embarcadero.com/article/20633 Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [http://openwatcom.org/index.php/Main_Page OpenWatcom] (Win32)
* [https://software.intel.com/en-us/c-compilers Intel C++ compiler] (Win32)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://dlang.org/ Digital Mars D]
* [http://dgcc.sourceforge.net/ GDC D Compiler]
* [https://github.com/ldc-developers/ldc/ LLVM D Compiler]
}}
|}

<center>[https://www.codeblocks.org/about.shtml The Code::Blocks team]</center>

<center>[[Special:Allpages|Index]]</center>

Main Page

2017-12-30T18:53:11Z

MortenMacFly:

__NOEDITSECTION__ __NOTOC__
{{Layout_box1|1=
[[Image:cb_splash.png|left]]
'''Welcome to the official Wiki for Code::Blocks''' 
[https://www.codeblocks.org Code::Blocks] is a free, open-source, cross-platform [[wikipedia:Integrated Development Environment|IDE]]. Using a plugin architecture, its capabilities and features are defined by the provided plugins. 
Currently, [https://www.codeblocks.org Code::Blocks] is oriented towards C/C++/Fortran.
The Code::Blocks team does not take responsibility for the content nor accuracy of these pages.

Wiki Editors: In order to login to edit pages, you must create an account on the [/ forums]. Use the same username and password for the wiki. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

{|width="100%" background-color="transparent"
|width="60%" valign="top"|


<div style="background-color: #dfeefb; border: 1px dotted #010101; margin: 5px; padding: 5px;">
{|align="center" style="background:transparent" cellspacing="5"

|valign="top" align="center" colspan="2"|
=== How do I... ===

|-

|align="center"|
'''[[Installing_Code::Blocks|...install Code::Blocks?]]''' 

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] ·
[[Installing_Code::Blocks#Ubuntu|Ubuntu]] ·
[[Installing_Code::Blocks#Mac_OS_X|Mac OS X]] ·
[[Installing_Code::Blocks#Fedora|Fedora]] ·
[[Installing_Code::Blocks|more...]]


|align="center"|
'''[[Installing_a_supported_compiler|...set up a compiler in Code::Blocks?]]''' 

[[Installing_a_supported_compiler#MinGW.2FGCC|MinGW]] ·
[[Installing_a_supported_compiler#Microsoft_Visual_C.2B.2B|MS Visual C++]] ·
[[Installing_a_supported_compiler|more...]]


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

|align="center"|
'''[[User_documentation#Third-party_libraries|...use a 3rd-party library?]]''' 

[[Using_wxWidgets|wxWidgets]] ·
[[Using_Boost|Boost]] ·
[[Using_SDL_with_Code::Blocks|SDL]] ·
[[User_documentation#Third-party_libraries|more...]]


|}
</div>

{{Layout_box3|1=
== Table of Contents ==
''Main article: [[Code::Blocks Documentation]]''

=== [[User documentation]] ===
:Articles for Code::Blocks users

=== [[FAQ]] ===
:Frequently Asked Questions

=== [[Feature List]] ===
:An index of Code::Blocks' useful features

=== [[Code::Blocks Plugins]] ===
:Plugins extend Code::Blocks' functionality

=== [[Off-site documentation]] ===
:Links to external documentation

=== [[Developer documentation]] ===
:Articles for developers of Code::Blocks itself
}}

|width="40%" valign="top"|

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/26 17.12]
* [/index.php?board=20.0 Nightly builds] (updated each night)
* [[Compiled_packages_of_Code::Blocks|Official and third-party binaries]] (for various distributions)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3ABug_Report+or+_type%3AUndefined bugs] or browse [http://alpha0010.github.io/cb-history/bugs.html old bugs]
* '''Features''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3AFeature_Request+or+_type%3AUndefined features] or browse [http://alpha0010.github.io/cb-history/features.html old features]
* '''Patches''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3APatch+or+_type%3AUndefined patches] or browse [http://alpha0010.github.io/cb-history/patches.html old patches]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [http://www.mingw.org MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore and PowerPC GCC] (Win32, Linux)
* [http://developer.apple.com/tools/ Apple GCC (Xcode)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [http://msdn.microsoft.com/vstudio/express/visualc/download/ Microsoft Visual C++ 2005] (Win32)
* [http://edn.embarcadero.com/article/20633 Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [http://openwatcom.org/index.php/Main_Page OpenWatcom] (Win32)
* [https://software.intel.com/en-us/c-compilers Intel C++ compiler] (Win32)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://dlang.org/ Digital Mars D]
* [http://dgcc.sourceforge.net/ GDC D Compiler]
* [https://github.com/ldc-developers/ldc/ LLVM D Compiler]
}}
|}

<center>[https://www.codeblocks.org/about.shtml The Code::Blocks team]</center>

<center>[[Special:Allpages|Index]]</center>

Creating a custom lexer for Code::Blocks editor

2017-02-19T19:02:50Z

MortenMacFly: /* Tips */

[[Category:Developer Documentation]]
Code::Blocks can provide syntax highlighting for any of the languages supported by Scintilla http://www.scintilla.org (the Rich Editing API used by C::B to provide syntax highlighting, code folding etc). Each language that C::B provides highlighting for has a C::B specific xml file found under <tt>sdk/resources/lexers</tt> that specifies styles and keywords of the language (they're simple XML files with names of the form <tt>lexer_*.xml</tt>). Adding a new language that is supported by Scintilla is as simple as adding an xml file for that language. At a minimum, the xml file must list the available set of styles for the lexical elements of a language and provide for keywords (the file will also specify a file containing sample code for editing and previewing lexer styles in Code::Blocks). Actual styles and keywords for each language can be edited by users within Code::Blocks under Settings->Editors->Syntax Highlighting allowing them view the results in a preview window (for the preview to display you will need to provide this sample code in a separate file also located in <tt>sdk/resources/lexers</tt>). User customized styles and keywords are kept in the users <tt>default.conf</tt> file (i.e. the xml file is never changed within codeblocks) allowing users to easily revert to the xml file.

To illustrate how you might construct a new lexer xml file let's look at the pre-installed CPP lexer, whose styles and keywords are stored in <tt>lexer_cpp.xml</tt>.

==XML==

<?xml version="1.0"?>

Basically this says "I am an XML file". '''Very Important'''

==DOCTYPE==

<!DOCTYPE CodeBlocks_lexer_properties>

This needs to be in every lexer file. Code::Blocks '''will not''' load the lexer if this is not present.

==Lexers==

<Lexer name="C/C++"
index="3"
filemasks="*.c,*.cpp,*.cc,*.cxx,*.h,*.hpp,*.hh,*.hxx,*.inl">

Pretty much self explanatory, except for the "magic" ''index'' number (we'll come to it in a sec).

* '''name''' is the lexer's configuration name. This will appear in the editor's configuration dialog, in the languages drop down box (in colors editing page).

* '''filemasks''' is a comma separated list of the extensions that this lexer should be used for. This is case-insensitive.

* '''index''' corresponds with the <tt>wxSCI_LEX_*</tt> constants, found in [http://svn.berlios.de/wsvn/codeblocks/trunk/src/sdk/wxscintilla/include/wx/wxscintilla.h <tt>sdk/wxscintilla/include/wx/wxscintilla.h</tt>]. In this example, if you look in <tt>sdk/wxscintilla/include/wx/wxscintilla.h</tt>, you'll see that ''index 3'' matches <tt>wxSCI_LEX_CPP</tt>. That is the ''lexer id'' for C/C++ syntax highlighting.

If we were building a lexer configuration for let's say, XML (random choice) we would look up the constant <tt>wxSCI_LEX_XML</tt> which is defined to be number ''5''. So ''index=5''. Simple.

==Styles==

Next follows many <tt><Style></tt> tags defining the different styles:

<Style name="Default"
index="0"
fg="0,0,0"
bg="255,255,255"
bold="0"
italics="0"
underlined="0" />

* '''name''' is the style's name. It appears in the editor's configuration dialog, in the colors editing page.

* '''fg''' is the foreground color. Comma separated list of three numbers from 0 to 255. In order: red, green and blue (RGB).

* '''bg''' is the background color.

* '''bold''' is <tt>"0"</tt> for disabled, <tt>"1"</tt> for enabled.

* '''italics''' is <tt>"0"</tt> for disabled, <tt>"1"</tt> for enabled.

* '''underlined''' is <tt>"0"</tt> for disabled, <tt>"1"</tt> for enabled.

You don't have to define all of these attributes. It's good to define them all for the <tt>"default"</tt> style (all lexers have a default style), but only the attributes needed should be defined for the rest of the styles.

* The '''index''' number in the <tt><Style></tt> tags, comes from a different set of constants defined in <tt>sdk/wxscintilla/include/wx/wxscintilla.h</tt>.

For each language supported by scintilla, there is a set of styles ''(lexical states)'' defined (these are what we're trying to configure with these files).

For example, for C/C++ files (<tt>wxSCI_LEX_CPP</tt>, remember?) the styles are defined as <tt>wxSCI_C_*</tt>.

For the <tt>"default"</tt> style shown above, this would be <tt>wxSCI_C_DEFAULT</tt> which is defined to be ''0''. Hence ''index=0'' for <tt>"default"</tt>.

<Style name="Comment (normal)"
index="1,2"
fg="160,160,160" />

This is the style definition for normal comments. As you can see you can define a single style for more than one style index, in this case two: ''1'' and ''2'' (always comma separated).

''1'' is for <tt>wxSCI_C_COMMENT</tt> (the C comment <tt>/* */</tt>) and ''2'' is for <tt>wxSCI_C_COMMENTLINE</tt> (the C++ comment to end of line <tt>// </tt>).

There are some special styles defined by Code::Blocks and are available to all lexers:

* '''index -99''' is the selected text style.
* '''index -98''' is the active line style (the line the caret is on).
* '''index -2''' is the breakpoint line style.
* '''index -3''' is the debugger active line style (while stepping the debugger).
* '''index -4''' is the compiler warning/error line style. ('''Note: this index was removed completely?''')

==Keywords==

Now on to the keywords.

<Keywords>
<Set index="0"
value="if int long try while and-so-on" />
<Set index="1" />
<Set index="2"
value="param remarks return $ @ \ & < > # { } and-so-on" />
</Keywords>

If you are defining a lexer configuration for a language that has keywords they should be added in the <tt><Keywords></tt> tag.
In the scintilla version used by Code::Blocks, you can setup up to 9 keyword sets (the "index" attribute). What each set does and which sets are used by a lexer, is defined by the lexer itself.

If you open LexCPP.cxx (from the scintilla sources), you will find the following:

static const char * const cppWordLists[] = {
"Primary keywords and identifiers",
"Secondary keywords and identifiers",
"Documentation comment keywords",
"Unused",
"Global classes and typedefs",
0,
};

This tells us which indices are valid and what each one represents:

Index 0, "Primary keywords and identifiers"

Index 1, "Secondary keywords and identifiers"

Index 2, "Documentation comment keywords"

(notice that index "3" is not used)

Index 4, "Global classes and typedefs"

==Sample Code==

The tag left is <tt>SampleCode</tt>. This is much pretty self explanatory:

<SampleCode value="lexer_cpp.sample"
breakpoint_line="20"
debug_line="22"
error_line="23"/>

* '''value''' is the filename of the code that will be shown in the Preview window.
When creating a <tt>lexer_*.sample</tt> try to do it with simple and concise sample code (like the ones found in a typical "Hello world!"), yet include all the styles of the lexer.

There are other optional options ('''Note: this index was removed completely?''')
* '''breakpoint_line''' is the number of the line in which a breakpoint line will be previewed.
* '''debug_line''' is the number of the line in which a debug line will be previewed.
* '''error_line''' is the number of the line in which an error line will be previewed.

==Tips==
When writing a lexer, this can be useful:
* .properties files of SciTE (the official Scintilla-based text editor) [http://scintilla.sourceforge.net/SciTE.html]
* .lang files of GtkSourceView (used Gedit) [http://git.gnome.org/browse/gtksourceview/tree/data/language-specs]

==Adding support for code-folding==

'''Note: support for code-folding can't be done from the lexer files. It must be done right in the Scintilla code'''.

See here: http://sphere.sourceforge.net/flik/docs/scintilla-folding.html

==Adding support for a lexer not supported in Scintilla==

'''Note: support for a lexer not supported in Scintilla is out of scope of Code::Blocks. It must be done right in the Scintilla code.'''

Here are some instructions: http://scintilla.sourceforge.net/Lexer.txt. To be able to use your newly created lexer in C::B, adjust the validity check of "lexer" in EditorColourSet::AddHighlightLanguage().

* After you've written the Scintilla lexer, submit the files to the [http://sourceforge.net/tracker/?group_id=2439 Scintilla tracker], following their own [http://scintilla.sourceforge.net/SciCoding.html coding style].

* After that, make any necesary change to wxScintilla and sumbit the files to the [http://sourceforge.net/tracker/?group_id=51305&atid=462818 wxScintilla tracker] or send a mail to the autor wyo@users.sourceforge.net (Otto Wyss).

* And finishing, be sure to send all to the [http://developer.berlios.de/patch/?func=addpatch&group_id=5358 Code::Blocks tracker] (Category: Lexer), and announce it at the [/index.php?board=7.0 Forum] and the [[Announcement for plugins/patches|Wiki announcement for plugins/patches]].

==See also==
* [[Languages supported by Code::Blocks lexers]]

Symbol Table plugin

2016-02-26T19:05:12Z

MortenMacFly:

[[Category:Code::Blocks Contrib Plugins]]
{{Infobox_Plugin|
name = SymTab |
logo = [[File:Generic-plugin.png]] |
developer = MortenMacFly |
maintainer = |
version = 1.0
}}

This plugin makes it possible to search for symbols in objects and libraries. The options and the path for the command line program <tt>nm</tt> are defined in the Options tab.

Clicking the ''Search'' starts the search, the results of the <tt>nm</tt> program are displayed in a separate window called ''SymTabs Result''. The name of the objects or libraries containing the symbol are listed under the title ''NM's Output''.

Main Page

2015-08-25T05:23:24Z

MortenMacFly:

__NOEDITSECTION__ __NOTOC__
{{Layout_box1|1=
[[Image:cb_splash.png|left]]
'''Welcome to the official Wiki for Code::Blocks''' 
[https://www.codeblocks.org Code::Blocks] is a free, open-source, cross-platform [[wikipedia:Integrated Development Environment|IDE]]. Using a plugin architecture, its capabilities and features are defined by the provided plugins. 
Currently, [https://www.codeblocks.org Code::Blocks] is oriented towards C/C++/Fortran.
The Code::Blocks team does not take responsibility for the content nor accuracy of these pages.

Wiki Editors: In order to login to edit pages, you must create an account on the [/ forums]. Use the same username and password for the wiki. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

{|width="100%" background-color="transparent"
|width="60%" valign="top"|


<div style="background-color: #dfeefb; border: 1px dotted #010101; margin: 5px; padding: 5px;">
{|align="center" style="background:transparent" cellspacing="5"

|valign="top" align="center" colspan="2"|
=== How do I... ===

|-

|align="center"|
'''[[Installing_Code::Blocks|...install Code::Blocks?]]''' 

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] ·
[[Installing_Code::Blocks#Ubuntu|Ubuntu]] ·
[[Installing_Code::Blocks#Mac_OS_X|Mac OS X]] ·
[[Installing_Code::Blocks#Fedora|Fedora]] ·
[[Installing_Code::Blocks|more...]]


|align="center"|
'''[[Installing_a_supported_compiler|...set up a compiler in Code::Blocks?]]''' 

[[Installing_a_supported_compiler#MinGW.2FGCC|MinGW]] ·
[[Installing_a_supported_compiler#Microsoft_Visual_C.2B.2B|MS Visual C++]] ·
[[Installing_a_supported_compiler|more...]]


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

|align="center"|
'''[[User_documentation#Third-party_libraries|...use a 3rd-party library?]]''' 

[[Using_wxWidgets|wxWidgets]] ·
[[Using_Boost|Boost]] ·
[[Using_SDL_with_Code::Blocks|SDL]] ·
[[User_documentation#Third-party_libraries|more...]]


|}
</div>

{{Layout_box3|1=
== Table of Contents ==
''Main article: [[Code::Blocks Documentation]]''

=== [[User documentation]] ===
:Articles for Code::Blocks users

=== [[FAQ]] ===
:Frequently Asked Questions

=== [[Feature List]] ===
:An index of Code::Blocks' useful features

=== [[Code::Blocks Plugins]] ===
:Plugins extend Code::Blocks' functionality

=== [[Off-site documentation]] ===
:Links to external documentation

=== [[Developer documentation]] ===
:Articles for developers of Code::Blocks itself
}}

|width="40%" valign="top"|

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/26 13.12]
* [/index.php?board=20.0 Nightly builds] (updated each night)
* [[Compiled_packages_of_Code::Blocks|Official and third-party binaries]] (for various distributions)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3ABug_Report+or+_type%3AUndefined bugs] or browse [http://alpha0010.github.io/cb-history/bugs.html old bugs]
* '''Features''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3AFeature_Request+or+_type%3AUndefined features] or browse [http://alpha0010.github.io/cb-history/features.html old features]
* '''Patches''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3APatch+or+_type%3AUndefined patches] or browse [http://alpha0010.github.io/cb-history/patches.html old patches]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [http://www.mingw.org MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore and PowerPC GCC] (Win32, Linux)
* [http://developer.apple.com/tools/ Apple GCC (Xcode)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [http://msdn.microsoft.com/vstudio/express/visualc/download/ Microsoft Visual C++ 2005] (Win32)
* [http://edn.embarcadero.com/article/20633 Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [http://openwatcom.org/index.php/Main_Page OpenWatcom] (Win32)
* [https://software.intel.com/en-us/c-compilers Intel C++ compiler] (Win32)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://dlang.org/ Digital Mars D]
* [http://dgcc.sourceforge.net/ GDC D Compiler]
* [https://github.com/ldc-developers/ldc/ LLVM D Compiler]
}}
|}

<center>[https://www.codeblocks.org/about.shtml The Code::Blocks team]</center>

<center>[[Special:Allpages|Index]]</center>

Main Page

2015-08-25T05:22:06Z

MortenMacFly:

__NOEDITSECTION__ __NOTOC__
{{Layout_box1|1=
[[Image:cb_splash.png|left]]
'''Welcome to the official Wiki for Code::Blocks''' 
[https://www.codeblocks.org Code::Blocks] is a free, open-source, cross-platform [[wikipedia:Integrated Development Environment|IDE]]. Using a plugin architecture, its capabilities and features are defined by the provided plugins. 
Currently, [https://www.codeblocks.org Code::Blocks] is oriented towards C/C++/Fortran.
The Code::Blocks team does not take responsibility for the content nor accuracy of these pages.

Wiki Editors: In order to login to edit pages, you must create an account on the [/ forums]. Use the same username and password for the wiki. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

{|width="100%" background-color="transparent"
|width="60%" valign="top"|


<div style="background-color: #dfeefb; border: 1px dotted #010101; margin: 5px; padding: 5px;">
{|align="center" style="background:transparent" cellspacing="5"

|valign="top" align="center" colspan="2"|
=== How do I... ===

|-

|align="center"|
'''[[Installing_Code::Blocks|...install Code::Blocks?]]''' 

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] ·
[[Installing_Code::Blocks#Ubuntu|Ubuntu]] ·
[[Installing_Code::Blocks#Mac_OS_X|Mac OS X]] ·
[[Installing_Code::Blocks#Fedora|Fedora]] ·
[[Installing_Code::Blocks|more...]]


|align="center"|
'''[[Installing_a_supported_compiler|...set up a compiler in Code::Blocks?]]''' 

[[Installing_a_supported_compiler#MinGW.2FGCC|MinGW]] ·
[[Installing_a_supported_compiler#Microsoft_Visual_C.2B.2B|MS Visual C++]] ·
[[Installing_a_supported_compiler|more...]]


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

|align="center"|
'''[[User_documentation#Third-party_libraries|...use a 3rd-party library?]]''' 

[[Using_wxWidgets|wxWidgets]] ·
[[Using_Boost|Boost]] ·
[[Using_SDL_with_Code::Blocks|SDL]] ·
[[User_documentation#Third-party_libraries|more...]]


|}
</div>

{{Layout_box3|1=
== Table of Contents ==
''Main article: [[Code::Blocks Documentation]]''

=== [[User documentation]] ===
:Articles for Code::Blocks users

=== [[FAQ]] ===
:Frequently Asked Questions

=== [[Feature List]] ===
:An index of Code::Blocks' useful features

=== [[Code::Blocks Plugins]] ===
:Plugins extend Code::Blocks' functionality

=== [[Off-site documentation]] ===
:Links to external documentation

=== [[Developer documentation]] ===
:Articles for developers of Code::Blocks itself
}}

|width="40%" valign="top"|

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/26 13.12]
* [/index.php?board=20.0 Nightly builds] (updated each night)
* [[Compiled_packages_of_Code::Blocks|Official and third-party binaries]] (for various distributions)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3ABug_Report+or+_type%3AUndefined bugs] or browse [http://alpha0010.github.io/cb-history/bugs.html old bugs]
* '''Features''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3AFeature_Request+or+_type%3AUndefined features] or browse [http://alpha0010.github.io/cb-history/features.html old features]
* '''Patches''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3APatch+or+_type%3AUndefined patches] or browse [http://alpha0010.github.io/cb-history/patches.html old patches]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [http://www.mingw.org MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore GCC] (Win32, Linux)
* [http://www.hightec-rt.com PowerPC GCC] (Win32, Linux)
* [http://developer.apple.com/tools/ Apple GCC (Xcode)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [http://msdn.microsoft.com/vstudio/express/visualc/download/ Microsoft Visual C++ 2005] (Win32)
* [http://edn.embarcadero.com/article/20633 Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [http://openwatcom.org/index.php/Main_Page OpenWatcom] (Win32)
* [https://software.intel.com/en-us/c-compilers Intel C++ compiler] (Win32)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://dlang.org/ Digital Mars D]
* [http://dgcc.sourceforge.net/ GDC D Compiler]
* [https://github.com/ldc-developers/ldc/ LLVM D Compiler]
}}
|}

<center>[https://www.codeblocks.org/about.shtml The Code::Blocks team]</center>

<center>[[Special:Allpages|Index]]</center>

Main Page

2015-08-25T05:21:04Z

MortenMacFly:

__NOEDITSECTION__ __NOTOC__
{{Layout_box1|1=
[[Image:cb_splash.png|left]]
'''Welcome to the official Wiki for Code::Blocks''' 
[https://www.codeblocks.org Code::Blocks] is a free, open-source, cross-platform [[wikipedia:Integrated Development Environment|IDE]]. Using a plugin architecture, its capabilities and features are defined by the provided plugins. 
Currently, [https://www.codeblocks.org Code::Blocks] is oriented towards C/C++/Fortran.
The Code::Blocks team does not take responsibility for the content nor accuracy of these pages.

Wiki Editors: In order to login to edit pages, you must create an account on the [/ forums]. Use the same username and password for the wiki. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

{|width="100%" background-color="transparent"
|width="60%" valign="top"|


<div style="background-color: #dfeefb; border: 1px dotted #010101; margin: 5px; padding: 5px;">
{|align="center" style="background:transparent" cellspacing="5"

|valign="top" align="center" colspan="2"|
=== How do I... ===

|-

|align="center"|
'''[[Installing_Code::Blocks|...install Code::Blocks?]]''' 

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] ·
[[Installing_Code::Blocks#Ubuntu|Ubuntu]] ·
[[Installing_Code::Blocks#Mac_OS_X|Mac OS X]] ·
[[Installing_Code::Blocks#Fedora|Fedora]] ·
[[Installing_Code::Blocks|more...]]


|align="center"|
'''[[Installing_a_supported_compiler|...set up a compiler in Code::Blocks?]]''' 

[[Installing_a_supported_compiler#MinGW.2FGCC|MinGW]] ·
[[Installing_a_supported_compiler#Microsoft_Visual_C.2B.2B|MS Visual C++]] ·
[[Installing_a_supported_compiler|more...]]


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

|align="center"|
'''[[User_documentation#Third-party_libraries|...use a 3rd-party library?]]''' 

[[Using_wxWidgets|wxWidgets]] ·
[[Using_Boost|Boost]] ·
[[Using_SDL_with_Code::Blocks|SDL]] ·
[[User_documentation#Third-party_libraries|more...]]


|}
</div>

{{Layout_box3|1=
== Table of Contents ==
''Main article: [[Code::Blocks Documentation]]''

=== [[User documentation]] ===
:Articles for Code::Blocks users

=== [[FAQ]] ===
:Frequently Asked Questions

=== [[Feature List]] ===
:An index of Code::Blocks' useful features

=== [[Code::Blocks Plugins]] ===
:Plugins extend Code::Blocks' functionality

=== [[Off-site documentation]] ===
:Links to external documentation

=== [[Developer documentation]] ===
:Articles for developers of Code::Blocks itself
}}

|width="40%" valign="top"|

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/26 13.12]
* [/index.php?board=20.0 Nightly builds] (updated each night)
* [[Compiled_packages_of_Code::Blocks|Official and third-party binaries]] (for various distributions)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3ABug_Report+or+_type%3AUndefined bugs] or browse [http://alpha0010.github.io/cb-history/bugs.html old bugs]
* '''Features''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3AFeature_Request+or+_type%3AUndefined features] or browse [http://alpha0010.github.io/cb-history/features.html old features]
* '''Patches''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3APatch+or+_type%3AUndefined patches] or browse [http://alpha0010.github.io/cb-history/patches.html old patches]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [http://www.mingw.org MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore GCC] (Win32, Linux)
* [http://www.hightec-rt.com PowerPC GCC] (Win32, Linux)
* [http://developer.apple.com/tools/ Apple GCC (Xcode)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [http://msdn.microsoft.com/vstudio/express/visualc/download/ Microsoft Visual C++ 2005] (Win32)
* [http://edn.embarcadero.com/article/20633 Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [http://openwatcom.org/index.php/Main_Page OpenWatcom] (Win32)
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/219754.htm Intel C++ compiler] (Win32)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://dlang.org/ Digital Mars D]
* [http://dgcc.sourceforge.net/ GDC D Compiler]
* [https://github.com/ldc-developers/ldc/ LLVM D Compiler]
}}
|}

<center>[https://www.codeblocks.org/about.shtml The Code::Blocks team]</center>

<center>[[Special:Allpages|Index]]</center>

Main Page

2015-08-25T05:16:45Z

MortenMacFly:

__NOEDITSECTION__ __NOTOC__
{{Layout_box1|1=
[[Image:cb_splash.png|left]]
'''Welcome to the official Wiki for Code::Blocks''' 
[https://www.codeblocks.org Code::Blocks] is a free, open-source, cross-platform [[wikipedia:Integrated Development Environment|IDE]]. Using a plugin architecture, its capabilities and features are defined by the provided plugins. 
Currently, [https://www.codeblocks.org Code::Blocks] is oriented towards C/C++/Fortran.
The Code::Blocks team does not take responsibility for the content nor accuracy of these pages.

Wiki Editors: In order to login to edit pages, you must create an account on the [/ forums]. Use the same username and password for the wiki. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

{|width="100%" background-color="transparent"
|width="60%" valign="top"|


<div style="background-color: #dfeefb; border: 1px dotted #010101; margin: 5px; padding: 5px;">
{|align="center" style="background:transparent" cellspacing="5"

|valign="top" align="center" colspan="2"|
=== How do I... ===

|-

|align="center"|
'''[[Installing_Code::Blocks|...install Code::Blocks?]]''' 

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] ·
[[Installing_Code::Blocks#Ubuntu|Ubuntu]] ·
[[Installing_Code::Blocks#Mac_OS_X|Mac OS X]] ·
[[Installing_Code::Blocks#Fedora|Fedora]] ·
[[Installing_Code::Blocks|more...]]


|align="center"|
'''[[Installing_a_supported_compiler|...set up a compiler in Code::Blocks?]]''' 

[[Installing_a_supported_compiler#MinGW.2FGCC|MinGW]] ·
[[Installing_a_supported_compiler#Microsoft_Visual_C.2B.2B|MS Visual C++]] ·
[[Installing_a_supported_compiler|more...]]


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

|align="center"|
'''[[User_documentation#Third-party_libraries|...use a 3rd-party library?]]''' 

[[Using_wxWidgets|wxWidgets]] ·
[[Using_Boost|Boost]] ·
[[Using_SDL_with_Code::Blocks|SDL]] ·
[[User_documentation#Third-party_libraries|more...]]


|}
</div>

{{Layout_box3|1=
== Table of Contents ==
''Main article: [[Code::Blocks Documentation]]''

=== [[User documentation]] ===
:Articles for Code::Blocks users

=== [[FAQ]] ===
:Frequently Asked Questions

=== [[Feature List]] ===
:An index of Code::Blocks' useful features

=== [[Code::Blocks Plugins]] ===
:Plugins extend Code::Blocks' functionality

=== [[Off-site documentation]] ===
:Links to external documentation

=== [[Developer documentation]] ===
:Articles for developers of Code::Blocks itself
}}

|width="40%" valign="top"|

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/26 13.12]
* [/index.php?board=20.0 Nightly builds] (updated each night)
* [[Compiled_packages_of_Code::Blocks|Official and third-party binaries]] (for various distributions)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3ABug_Report+or+_type%3AUndefined bugs] or browse [http://alpha0010.github.io/cb-history/bugs.html old bugs]
* '''Features''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3AFeature_Request+or+_type%3AUndefined features] or browse [http://alpha0010.github.io/cb-history/features.html old features]
* '''Patches''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3APatch+or+_type%3AUndefined patches] or browse [http://alpha0010.github.io/cb-history/patches.html old patches]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [http://www.mingw.org MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore GCC] (Win32, Linux)
* [http://www.hightec-rt.com PowerPC GCC] (Win32, Linux)
* [http://developer.apple.com/tools/ Apple GCC (Xcode)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [http://msdn.microsoft.com/vstudio/express/visualc/download/ Microsoft Visual C++ 2005] (Win32)
* [http://edn.embarcadero.com/article/20633 Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [http://openwatcom.org/index.php/Main_Page OpenWatcom] (Win32)
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/219754.htm Intel C++ compiler] (Win32)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://www.digitalmars.com/d/dcompiler.html Digital Mars D]
* [http://dgcc.sourceforge.net/ GDC D Compiler]
* [https://github.com/ldc-developers/ldc/ LLVM D Compiler]
}}
|}

<center>[https://www.codeblocks.org/about.shtml The Code::Blocks team]</center>

<center>[[Special:Allpages|Index]]</center>

Roadmap for version 1.0

2015-01-23T19:27:28Z

MortenMacFly: /* Version 1.0 RC 3 (Ephialtes) */

[[Category:Roadmaps]]

'''Warning : This page is very likely outdated and irrelevant of what is actually going on'''

==Version 1.0 (Pheidippides)==
''To Be Announced''

==Version 1.0 RC final (Athenades)==
''TBA''
*No feature additions.
*Regression and bug handling only.

==Version 1.0 RC 3 (Ephialtes)==
''TBA''

*[[Image:Chk.png]]Unicode support
**[[Image:Chk.png]]User interface
**[[Image:Chk.png]]Configuration system
**[[Image:Chk.png]]Editor component
**[[Image:Nop.png]]Fully automatic detection of document encoding
*[[Image:Blk.png]]<s>Scripting support (Angelscript)</s> (abandoned due to lack of 64bit support)
*[[Image:Chk.png]]Scripting support (Squirrel/Sq plus)
**[[Image:Chk.png]]Watch scripts (see [[Debugger scripts]])
**[[Image:Chk.png]]Build target scripts
*[[Image:Chk.png]]Virtual folder support
*[[Image:Chk.png]]Global user variables
**[[Image:Chk.png]]Profile-dependent GUVs
**[[Image:Chk.png]]Multiple variable sets
**[[Image:Chk.png]]Custom variable definition
*[[Image:Chk.png]]wxFlatNoteBook editors
*[[Image:Chk.png]]wxAUI docking library
*[[Image:Chk.png]]Context-sensitive layout switching
*[[Image:Chk.png]]XML-based configuration system
*[[Image:Chk.png]]XML-based compiler framework
*[[Image:Blk.png]]Property-based build system
*[[Image:Chk.png]]Improved configuration user interface
*[[Image:Blk.png]]Automatic updates
*[[Image:Blk.png]]Usability and stability fixes for code completion plugin
*[[Image:Blk.png]]Regression and bug handling.

==Version 1.0 RC 2 (Leonidas)==
''25 October 2005''
*Precompiled headers (PCH) support! (currently works only with GCC)
*The source is now fully UNICODE-compatible!
*The source is also fully 64-bit compatible!
*Autoconf/automake build system is now used for non-windows platforms
* New editor functionality
**Find declaration
**Open #include
*Project wizard plugins
*Support for SDCC
*Better handling of modified files outside the IDE
*Single file compilation
*Find-in-Files for arbitrary paths/filemasks
*All internal file formats are well-formed, valid XML
*New plugins:
**Code statistics: counts nr. of source lines, nr. of comment lines, etc.
**CBProfiler: parses and displays the output of GProf, the GNU Profiler
**SourceExporter: exports the active file to HTML/RTF/ODT
*New lexers:
**Fortran77
**NVidia CG
**X-Base languages (Clipper, Foxpro)
*New and improved project templates:
**SDCC program
**Irrlicht 3D Graphics Engine
**Ogre 3D Graphics Engine
**GLFW project (OpenGL FrameWork)
**wxWidgets: static/dynamic unicode/ansi versions.

==Version 1.0 RC 1-1 (Oedipus)==
''2 August 2005''
*Several critical bug fixes

==Version 1.0 RC 1 (Laius)==
''25 July 2005''
*Compiler support for OpenWatcom
*Per-target environment variables
*Convenient "Start here" page
*Improved gcc error parsing
*Find in files functionality
*Ability to add files to project recursively.
*External dependency handling
*Better import of foreign project files
*Many GDB debugger updates
*Numerous user interface improvements
*New project templates
**QT4.
**Ogre3D.
* Modular Syntax highlighting
* Syntax highlighting support for:
**C/C++
**Windows resources
**HTML/XML/XSL
**Lua scripts
**GameMonkey scripts
**Hitach H8 ASM

Main Page

2013-12-27T20:44:27Z

MortenMacFly:

__NOEDITSECTION__ __NOTOC__
{{Layout_box1|1=
[[Image:cb_splash.png|left]]
'''Welcome to the official Wiki for Code::Blocks''' 
[https://www.codeblocks.org Code::Blocks] is an open-source, cross-platform [[wikipedia:Integrated Development Environment|IDE]]. Using a plugin architecture, its capabilities and features are defined by the provided plugins. 
Currently, [https://www.codeblocks.org Code::Blocks] is oriented towards C/C++.
The Code::Blocks team does not take responsibility for the content nor accuracy of these pages.

Wiki Editors: In order to login to edit pages, you must create an account on the [/ forums]. Use the same username and password for the wiki. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

{|width="100%" background-color="transparent"
|width="60%" valign="top"|


<div style="background-color: #dfeefb; border: 1px dotted #010101; margin: 5px; padding: 5px;">
{|align="center" style="background:transparent" cellspacing="5"

|valign="top" align="center" colspan="2"|
=== How do I... ===

|-

|align="center"|
'''[[Installing_Code::Blocks|...install Code::Blocks?]]''' 

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] ·
[[Installing_Code::Blocks#Ubuntu|Ubuntu]] ·
[[Installing_Code::Blocks#Mac_OS_X|Mac OS X]] ·
[[Installing_Code::Blocks#Fedora|Fedora]] ·
[[Installing_Code::Blocks|more...]]


|align="center"|
'''[[Installing_a_supported_compiler|...set up a compiler in Code::Blocks?]]''' 

[[Installing_a_supported_compiler#MinGW.2FGCC|MinGW]] ·
[[Installing_a_supported_compiler#Microsoft_Visual_C.2B.2B|MS Visual C++]] ·
[[Installing_a_supported_compiler|more...]]


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

|align="center"|
'''[[User_documentation#Third-party_libraries|...use a 3rd-party library?]]''' 

[[Using_wxWidgets|wxWidgets]] ·
[[Using_Boost|Boost]] ·
[[Using_SDL_with_Code::Blocks|SDL]] ·
[[User_documentation#Third-party_libraries|more...]]


|}
</div>

{{Layout_box3|1=
== Table of Contents ==
''Main article: [[Code::Blocks Documentation]]''

=== [[User documentation]] ===
:Articles for Code::Blocks users

=== [[FAQ]] ===
:Frequently Asked Questions

=== [[Feature List]] ===
:An index of Code::Blocks' useful features

=== [[Code::Blocks Plugins]] ===
:Plugins extend Code::Blocks' functionality

=== [[Off-site documentation]] ===
:Links to external documentation

=== [[Developer documentation]] ===
:Articles for developers of Code::Blocks itself
}}

|width="40%" valign="top"|

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/26 13.12]
* [/index.php?board=20.0 Nightly builds] (updated each night)
* [[Compiled_packages_of_Code::Blocks|Official and third-party binaries]] (for various distributions)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://developer.berlios.de/projects/codeblocks/ Project page at BerliOS]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': [http://developer.berlios.de/bugs/?group_id=5358 Browse] or [http://developer.berlios.de/bugs/?func=addbug&group_id=5358 submit new]
* '''Features''': [http://developer.berlios.de/feature/?group_id=5358 Browse] or [http://developer.berlios.de/feature/?func=addfeature&group_id=5358 submit new]
* '''Patches''': [http://developer.berlios.de/patch/?group_id=5358 Browse] or [http://developer.berlios.de/patch/?func=addpatch&group_id=5358 submit new]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [http://www.mingw.org MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore GCC] (Win32, Linux)
* [http://www.hightec-rt.com PowerPC GCC] (Win32, Linux)
* [http://developer.apple.com/tools/ Apple GCC (Xcode)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [http://msdn.microsoft.com/vstudio/express/visualc/download/ Microsoft Visual C++ 2005] (Win32)
* [http://edn.embarcadero.com/article/20633 Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [http://openwatcom.org/index.php/Main_Page OpenWatcom] (Win32)
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/219754.htm Intel C++ compiler] (Win32)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://www.digitalmars.com/d/dcompiler.html Digital Mars D]
* [http://dgcc.sourceforge.net/ GDC D Compiler]
* [http://dsource.org/projects/ldc/ LLVM D Compiler]
}}
|}

<center>[https://www.codeblocks.org/about.shtml The Code::Blocks team]</center>

<center>[[Special:Allpages|Index]]</center>

File:Cb splash.png

2013-12-27T20:43:48Z

MortenMacFly: uploaded a new version of "File:Cb splash.png"

The splash screen used in Code::Blocks, resized to 320x113

File:Cb splash.png

2013-12-27T20:43:19Z

MortenMacFly: uploaded a new version of "File:Cb splash.png"

The splash screen used in Code::Blocks, resized to 320x113

Debugger scripts

2013-01-12T12:59:45Z

MortenMacFly: /* Basic principle of the debugger script */

[[Category:Scripting Code::Blocks]]

==Basic principle of the debugger script==

[[image:Debuggercommand.png]]

Look at the image above, this will give a brief introduction of how the debugger script works. For example, you want to view the variable "msg". There are two handshake between the debugger plugin and gdb.

First, the debugger plugin sends a command to gdb to query the type of msg
<pre>
whatis msg
</pre>
then, the gdb will return the type
<pre>
type = wxString
</pre>
Secondly, the debugger checks that wxString is already registered, and sends the command
<pre>
output /c msg.m_pchData[0]@((wxStringData*)msg.m_pchData-1)->nDataLength
</pre>
Then, gdb replies with the string below:
<pre>
{119 'w', 120 'x', 87 'W', 105 'i', 100 'd', 103 'g', 101 'e', 116 't',
115 's', 32 ' ', 50 '2', 46 '.', 56 '8', 46 '.', 49 '1', 48 '0', 45 '-',
87 'W', 105 'i', 110 'n', 100 'd', 111 'o', 119 'w', 115 's', 45 '-',
85 'U', 110 'n', 105 'i', 99 'c', 111 'o', 100 'd', 101 'e', 32 ' ',
98 'b', 117 'u', 105 'i', 108 'l', 100 'd'}
</pre>

Finally, the value is shown in the watch window

==Script functions==
Debugger scripts are similar to [http://www.codeproject.com/csharp/ImageVisualizer.asp Visual Studio Debugger Visualizer]. It allows you to write a small piece of code that gets executed by the debugger whenever you try to view a specific type of variables and can be used to show custom text with the important information you need in it.

Quote from Game_Ender - March 23, 2006

''I don't think its possible to open up another window to visualize something.''

Let's see how this works. Everything is inside a single file in the scripts/ folder, named gdb_types.script :). Support for more (user-defined) scripts is planned for the future.

This script is called by Code::Blocks at two places:

# when GDB is launched. It calls the script function RegisterTypes() to register all user-defined types known by the Code::Blocks' debugger.
# whenever GDB encounters your variable type, it calls the script functions specific to this datatype (registered in RegisterTypes() - more on that below).

That's the overview. Let's dissect the shipped gdb_types.script and see how it adds std::string support to GDB.

// Registers new types with driver
function RegisterTypes(driver)
{
// signature:
// driver.RegisterType(type_name, regex, eval_func, parse_func);

// STL String
driver.RegisterType(
_T("STL String"),
_T("[^[:alnum:]_]+string[^[:alnum:]_]*"),
_T("Evaluate_StlString"),
_T("Parse_StlString")
);
}

The "driver" parameter is the debugger driver but you don't need to care about it :) (currently this only works with GDB). This class contains a single method: RegisterType. Here's its C++ declaration:

void GDB_driver::RegisterType(const wxString& name, const wxString& regex, const wxString& eval_func, const wxString& parse_func)

So, in the above script code, the "STL String" (just a name - doesn't matter what) type is registered, providing a regular expression string for the debugger plugin to match against and, finally, it provides the names of the two mandatory functions needed for each registered type:

# evaluation function: this must return a command understood by the actual debugger (GDB in this case). For the "STL string", the evaluate function returns an GDB "output" command which will be executed by the GDB debugger.
# parser function: once the debugger runs the command returned by the evaluation function, it passes its result to this function for further processing. What this function returns, is what is actually diplayed by CodeBlocks (usually in the watches window or in a tooltip).

Let's see the evaluation function for std::string:

function Evaluate_StlString(type, a_str, start, count)
{
local oper = _T(".");

if (type.Find(_T("*")) > 0)
oper = _T("->");

local result = _T("output ") + a_str + oper + _T("c_str()[") + start + _T("]@");
if (count != 0)
result = result + count;
else
result = result + a_str + oper + _T("size()");
return result;
}

I 'm not going to explain what this function returns. I 'll just tell you that it returns a GDB command that will make GDB print the actual std::string's contents. ''Yes, you need to know your debugger and its commands before you try to extend it.''

What I will tell you though, is what those function arguments are.

* type: the datatype, e.g. "char*", "const string", etc.
* a_str: the name of the variable GDB is trying to evaluate.
* start: the start offset (used for arrays).
* count: the count starting from the start offset (used for arrays).

Let's see the relevant parser function now:

function Parse_StlString(a_str, start)
{
// nothing needs to be done
return a_str;
}

* a_str: the returned string when GDB ran the command returned by the evaluation function. In the case of std::string, it's the contents of the string.
* start: the start offset (used for arrays).

Well, in this example, nothing needs to be done. "a_str" already contains the std:string's contents so we just return it :)

I suggest you study how wxString is registered in that same file, as a more complex example.

== Links ==

#[/index.php/topic,11184.msg76200.html#msg76200 Debugging QString]

== See also ==
* [[Scripting commands]]

Comparison of wxSmith features

2013-01-07T07:51:42Z

MortenMacFly: /* Contrib widgets supported */

[[Category:wxSmith Documentation]]
Here is a list of [[wxSmith plugin|wxSmith]] features when compared to other [[wikipedia:WxWidgets|wxWidgets]] [[wikipedia:Rapid application development|RAD]] solutions.

Note that support for new features are added on a daily basis for some of these [[wikipedia:Rapid application development|RADs]].

Please update this list when something gets added.

==General information==
Basic general information about the [[wikipedia:Rapid application development|RADs]]: developer, license/price etc.
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec; border: solid 1px gray;"
! style="width:12em" | [[wikipedia:Rapid application development|RAD]]
! Developer
! Cost ([[wikipedia:United States dollar|USD]])
! [[wikipedia:Open source|Open source]]
! [[wikipedia:Software licence|Software licence]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[wxSmith plugin|wxSmith]]
| Bartlomiej Swiecki
| Free
| Yes
| [[wikipedia:GNU General Public License|GPL]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [http://www.anthemion.co.uk/dialogblocks/ DialogBlocks]
| Julian Smart
| Free (trial), €66 (normal), €35 (student)
| No
| [[wikipedia:Proprietary software|Proprietary]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [http://www.roebling.de/ wxDesigner]
| Robert Roebling
| Free (trial), €129 (normal), €29 (student)
| No
| [[wikipedia:Proprietary software|Proprietary]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [http://wxformbuilder.org/ wxFormBuilder]
| José Antonio Hurtado, Juan Antonio Ortega, Ryan Mulder, Ryan Pusztai, Michal Bliznak
| Free
| Yes
| [[wikipedia:GNU General Public License|GPL]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [http://visualwx.altervista.org/ VisualWx]
| {{dunno}}
| Free
| No
| {{dunno}}
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [http://wxdsgn.sf.net/ wxDevC++]
| Guru Kathiresan , Tony Reina, Malcolm Nealon, Joel Low
| Free
| Yes
| [[wikipedia:GNU General Public License|GPL]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [http://twinforms.com/ wxForms for Delphi / C++ Builder]
| Guru Kathiresan
| Free (trial), $29.99
| No
| [[wikipedia:Proprietary software|Proprietary]]
|- style="background: #ececec; border: solid 1px gray;"
! [[wikipedia:Rapid application development|RAD]]
! Developer
! Cost ([[wikipedia:United States dollar|USD]])
! [[wikipedia:Open source|Open source]]
! [[wikipedia:Software licence|Software licence]]
|-
|}

==Widgets supported==
{| 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;"
|- style="background: #ececec;"
! style="width: 17em" | Widget
! wxSmith
! DialogBlocks
! wxDesigner
! wxFormBuilder
! VisualWx
! wxDevC++
! wxForms
|-
! style="text-align: left; background: #ececec;" | wxAnimationCtrl
| {{yes}}{{refun|svn}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxAuiManager
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxAuiNotebook
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxAuiToolBar
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxAuiToolBarItem
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxAuiToolBarLabel
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxAuiToolBarSeparator
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxAuiToolBarSpacer
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxBitmapButton
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxBitmapComboBox
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxBoxSizer
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxButton
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxCalendarCtrl
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxCheckBox
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxCheckListBox
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxChoice
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxChoicebook
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxColourDialog
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxColourPickerCtrl
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxComboBox
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxContextHelpButton
| {{yes}}{{refun|svn}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxDatePickerCtrl
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxDialUpManager
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxDirDialog
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxDirPickerCtrl
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxFileDialog
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxFilePickerCtrl
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxFindReplaceDialog
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxFlexGridSizer
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxFontDialog
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxFontPickerCtrl
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxGauge
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxGenericDirCtrl
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxGLCanvas
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxGrid
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxGridBagSizer
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxGridSizer
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxHtmlEasyPrinting
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxHtmlListBox
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxHtmlWindow
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxHyperLinkCtrl
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxImage
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxImageList
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxListbook
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxListBox
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxListCtrl
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxListView
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxMediaCtrl
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxMenu
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxMenuBar
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxMessageDialog
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxMultiChoiceDialog
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxNotebook
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxOwnerDrawnComboBox
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxPageSetupDialog
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxPanel
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxPasswordEntryDialog
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxPrintDialog
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxProgressDialog
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxPropertySheetDialog
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxRadioBox
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxRadioButton
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxRichTextCtrl
| {{yes}}{{refun|svn}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxRichTextFormattingDialog
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxRichTextStyleComboCtrl
| {{yes}}{{refun|patch}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxRichTextStyleListBox
| {{yes}}{{refun|patch}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxRichTextStyleListCtrl
| {{yes}}{{refun|patch}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxRichTextStyleOrganiserDialog
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxSashLayoutWindow
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxSashWindow
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxScrollBar
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxScrolledWindow
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxSearchCtrl
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxSimpleHtmlListBox
| {{yes}}{{refun|svn}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxSingleChoiceDialog
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxSingleInstanceChecker
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxSlider
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxSpacer
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxSpinButton
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxSpinCtrl
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxSplitterWindow
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxStaticBitmap
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxStaticBox
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxStaticBoxSizer
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxStaticLine
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxStaticText
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxStatusBar
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxStopWatch
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxSymbolPickerDialog
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxStdDialogButtonSizer
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxTextCtrl
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxTextEntryDialog
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxTimer
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxToggleButton
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxToolbar
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxTreebook
| {{yes}}{{refun|svn}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxTreeCtrl
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxVListBox
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxVScrolledWindow
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxWindow (Foreign)
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | wxWizardPage
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|- style="background: #ececec;"
! Widget
! wxSmith
! DialogBlocks
! wxDesigner
! wxFormBuilder
! VisualWx
! wx-DevC++
! wxForms
|-
|}

*{{note|patch}} Currently available via patch but should be integrated into the main distribution soon.
*{{note|svn}} Currently available from the SVN repository and in nightly builds and will be part of the next release.

==Contrib widgets supported==
{| 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;"
|- style="background: #ececec;"
! style="width: 17em" | Widget
! wxSmith
! DialogBlocks
! wxDesigner
! wxFormBuilder
! VisualWx
! wxDevC++
! wxForms
|-
! style="text-align: left; background: #ececec;" | awxLed
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxChartCtrl
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxCustomButton
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxDynamicSashWindow
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxEditableListBox
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxFlatNotebook
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxImageButton
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxImagePanel
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxLEDNumberCtrl
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxMathPlot
| {{yes}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
| {{dunno}}
|-
! style="text-align: left; background: #ececec;" | wxPlotCtrl
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxPlotWindow
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxPropertyGrid
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxPropertyGridManager
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxScintilla
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxStyledTextCtrl
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | wxTreeListCtrl
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
|- style="background: #ececec;"
! Widget
! wxSmith
! DialogBlocks
! wxDesigner
! wxFormBuilder
! VisualWx
! wxDevC++
! wxForms
|-
|}

==Languages supported==
{| 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;"
|- style="background: #ececec;"
! style="width: 17em" | Feature
! wxSmith
! DialogBlocks
! wxDesigner
! wxFormBuilder
! VisualWx
! wxDevC++
! wxForms
|-
! style="text-align: left; background: #ececec;" | C++ code output
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | Delphi / Pascal code output
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | Python code output
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | Lua code output
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | Ruby code output
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | Perl code output
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | C# code output
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | Basic code output
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|- style="background: #ececec;"
! Feature
! wxSmith
! DialogBlocks
! wxDesigner
! wxFormBuilder
! VisualWx
! wxDevC++
! wxForms
|-
|}

==Features supported==
{| 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;"
|- style="background: #ececec;"
! style="width: 17em" | Feature
! wxSmith
! DialogBlocks
! wxDesigner
! wxFormBuilder
! VisualWx
! wxDevC++
! wxForms
|-
! style="text-align: left; background: #ececec;" | XRC input
| {{yes}}{{refun|XRCnotworks}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | XRC output
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | XRC code loading
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | Validators{{refun|Validators}}
| {{partial}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | Conditional UI{{refun|ConditionalUI}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | Event table and handler generation{{refun|EventTable}}
| {{yes}}
| {{yes}}
| {{partial}}
| {{yes}}
| {{partial}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | Bitmaps support{{refun|Bitmaps}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{partial}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | English descriptions{{refun|EnglishDesc}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | Easy access to window pointers{{refun|WindowPointers}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{dunno}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | Visually creating custom controls
| {{partial}}
| {{yes}}
| {{partial}}
| {{partial}}
| {{partial}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | Template controls{{refun|TemplateControls}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | Sizer design
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! style="text-align: left; background: #ececec;" | Non-sizer design
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
|- style="background: #ececec;"
! Feature
! wxSmith
! DialogBlocks
! wxDesigner
! wxFormBuilder
! VisualWx
! wxDevC++
! wxForms
|-
|}

*{{note|XRCnotworks}} Currently, only one dialog resource per XRC file is imported.

=== Features explained ===

==== {{note|Validators}}Validators ====

The aim of the validator concept is to make dialogs very much easier to write. A validator is an object that can be plugged into a control (such as a wxTextCtrl), and mediates between C++ data and the control, transferring the data in either direction and validating it. It also is able to intercept events generated by the control, providing filtering behaviour without the need to derive a new control class.

How to use validators in a RAD that supports this concept: Just add a variable, select the variable and a validator, and the data transfer between variable and control is done for you.

==== {{note|ConditionalUI}}Conditional UI ====

It's the ability to adapt the user interface to the UI guidelines of different platform.

Just mark elements as for one platform (or several), and preview the look for any given platform.

[[Image:Conditional ui.PNG|Example of how it looks on DialogBlocks]]

==== {{note|EventTable}}Event table and handler generation ====

The RAD generates the event tables and empty handlers (including UI update handlers) so you can immediately concentrate on writing code to make the dialog come to life.

It includes a choice of event types for each window, with function name editing.

'''DialogBlocks Event Handler'''

Here DialogBlocks haves the list of event handlers.

The most noticeable feature here is that if you do a double-click on a event, you're transported to the function associated in the code. It's very handy.

[[Image:Event handler dialogblocks.PNG|Event Tables in DialogBlocks]]

'''VisualWx Event Handler'''

Here VisualWx filters the events:
* Base wxWidgets Events
* Component Events
* Windows Events
* VisualWx Events
* Custom Events

[[Image:Event handler visualwx.PNG|Event Tables in VisualWx]]

==== {{note|Bitmaps}}Bitmap support ====

Bitmaps support means that you can import images into your project from a variety of formats and associate them with your static bitmap and bitmap button controls.

You can specify whether the bitmaps will converted into XPM format (the standard format for small bitmaps in wxWidgets) and whether the XPM image will be inserted as inline C++ code, or loaded from a file.

==== {{note|EnglishDesc}}English descriptions ====

English descriptions show a brief description of each element, to help you get used to sizers and also to make it easier to see at a glance the important aspects of your dialog element.

[[Image:Rad english descriptions.PNG|An example of DialogBlocks English descriptions]]

==== {{note|WindowPointers}}Easy access to window pointers ====

The ''easy access to window pointers'' concept means:

Give each window a variable name, and the RAD will add the name to the class declaration, and initialise it to the appropriate window in the implementation.

In XRC mode, the RAD can generate the code to find the window and assign it to the pointer variable.

==== {{note|TemplateControls}}Template controls ====

Template controls are sets of most common widgets together, like an Ok/Cancel pair buttons inside a sizer, being user-definable.

FAQ

2012-12-25T12:38:21Z

MortenMacFly: /* Compiling (errors) */

[[Category:Code::Blocks Documentation]]

== [[FAQ-General|General]] ==

* '''[[FAQ-General#Q: What is Code::Blocks?|What is Code::Blocks?]]'''
* '''[[FAQ-General#Q: What Code::Blocks is not?|What Code::Blocks is not?]]'''
* '''[[FAQ-General#Q: What license is Code::Blocks released under?|What license is Code::Blocks released under?]]'''
* '''[[FAQ-General#Q: When will the next stable version of Code::Blocks be released?|When will the next stable version of Code::Blocks be released?]]'''
* '''[[FAQ-General#Q: Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret?|Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret?]]'''

== [[FAQ-Compiling (general)|Compiling (general)]] ==

* '''[[FAQ-Compiling (general)#Q: What compiler can I use with Code::Blocks?|What compiler can I use with Code::Blocks?]]'''
* '''[[FAQ-Compiling (general)#Q: My project should be compiled with a custom makefile. Is it possible with Code::Blocks?|My project should be compiled with a custom makefile. Is it possible with Code::Blocks?]]'''
* '''[[FAQ-Compiling (general)#Q: I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler?|I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler?]]'''
* '''[[FAQ-Compiling (general)#Q: Microsoft calls MSVCRT.DLL a "Known DLL." How do I know if I can/should use it?|Microsoft calls MSVCRT.DLL a "Known DLL." How do I know if I can/should use it?]]'''
* '''[[FAQ-Compiling (general)#Q: How can I use a DLL without DEF or LIB files?|How can I use a DLL without DEF or LIB files?]]'''
* '''[[FAQ-Compiling (general)#Q: Where are the libraries for the OpenGL, Ogre3D, SDL, QT, wxWidgets etc. projects?|Where are the libraries for the OpenGL, Ogre3D, SDL, QT, wxWidgets etc. projects?]]'''
* '''[[FAQ-Compiling (general)#Q: Is it possible to use Visual C++ 6.0 with Code::Blocks?|Is it possible to use Visual C++ 6.0 with Code::Blocks?]]'''
* '''[[FAQ-Compiling (general)#Q: I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?|I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?]]'''
* '''[[FAQ-Compiling (general)#Q: How do I use both Debug and Release builds of wx libraries?|How do I use both Debug and Release builds of wx libraries?]]'''
* '''[[FAQ-Compiling (general)#Q: How do I add version information to windows executables and dll's?|How do I add version information to windows executables and dll's?]]'''
* '''[[FAQ-Compiling (general)#Q: Code::Blocks does not force relink if the library is changed?|Code::Blocks does not force relink if the library is changed?]]'''
* '''[[FAQ-Compiling (general)#Q: How do I report a compilation problem on the forums?|How do I report a compilation problem on the forums?]]'''
* '''[[FAQ-Compiling (general)#Q: All of the Build related options are grayed out?|All of the Build related options are grayed out?]]'''

== [[FAQ-Compiling (errors)|Compiling (errors)]] ==

* '''[[FAQ-Compiling (errors)#Q: How do I troubleshoot a compiler problem?|How do I troubleshoot a compiler problem?]]'''
* '''[[FAQ-Compiling (errors)#Q: What do I need to know when using 3rd party libs?|What do I need to know when using 3rd party libs?]]'''
* '''[[FAQ-Compiling (errors)#Q: My simple C++ program throws up lots of errors - what is going on?|My simple C++ program throws up lots of errors - what is going on?]]'''
* '''[[FAQ-Compiling (errors)#Q: I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong?|I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong?]]'''
* '''[[FAQ-Compiling (errors)#Q: When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong?|When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong?]]'''
* '''[[FAQ-Compiling (errors)#Q: I can't compile a multithreaded app with VC Toolkit! Where are the libraries?|I can't compile a multithreaded app with VC Toolkit! Where are the libraries?]]'''
* '''[[FAQ-Compiling (errors)#Q: I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll"|I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll"]]'''
* '''[[FAQ-Compiling (errors)#Q: My build fails with multiple undefined reference errors?|My build fails with multiple ''undefined reference'' errors?]]'''
* '''[[FAQ-Compiling (errors)#Q: My build fails in the compile/link/run step with a Permission denied error?|My build fails in the compile/link/run step with a ''Permission denied'' error?]]'''
* '''[[FAQ-Compiling (errors)#Q: My build fails to link due to multiple definition of xyz errors?|My build fails to link due to ''multiple definition of xyz'' errors?]]'''

== [[FAQ-Settings|Settings]] ==

* '''[[FAQ-Settings#Q: How do I get Code Completion to work?|How do I get Code Completion to work?]]'''
* '''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|How do I make Code::Blocks portable?]]'''
* '''[[FAQ-Settings#Q: Code::Blocks option xyz is missing?|Code::Blocks option ''xyz'' is missing?]]'''
* '''[[FAQ-Settings#Q: How do I change the default location of the output terminal?|How do I change the default location of the output terminal?]]'''

== [[FAQ-Issues and Workarounds|Issues and Workarounds]] ==

* '''[[FAQ-Issues and Workarounds#Q: Sometime, in the text editor, space bar triggers Code Completion, how do I fix that?|Sometime, in the text editor, space bar triggers Code Completion, how do I fix that?]]'''
* '''[[FAQ-Issues and Workarounds#Q: IDE is drawing the text from Right to Left?|IDE is drawing the text from Right to Left?]]'''
* '''[[FAQ-Issues and Workarounds#Q: All the options in the debug menu are grayed out?|All the options in the debug menu are grayed out?]]'''
* '''[[FAQ-Issues and Workarounds#Q: My project works everywhere except one computer?|My project works everywhere except one computer?]]'''
* '''[[FAQ-Issues and Workarounds#Q: Syntax highlighting is broken; how do I fix it?|Syntax highlighting is broken; how do I fix it?]]'''
* '''[[FAQ-Issues and Workarounds#Q: I posted on the forums that Code::Blocks was not working, but no one could help me?|I posted on the forums that Code::Blocks was not working, but no one could help me?]]'''
* '''[[FAQ-Issues and Workarounds#Q: I cannot find any text in my Code::Blocks logs?|I cannot find any text in my Code::Blocks logs?]]'''
* '''[[FAQ-Issues and Workarounds#Q: Scrolling causes gray areas/distortions to obscure my code in the editor?|Scrolling causes gray areas/distortions to obscure my code in the editor?]]'''
* '''[[FAQ-Issues and Workarounds#Q: I cannot type a greater-than '>' sign?|I cannot type a greater-than '>' sign?]]'''

FAQ-Compiling (errors)

2012-12-25T12:37:52Z

MortenMacFly: /* Q: What so I need to know when using 3rd party libs? */

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: How do I troubleshoot a compiler problem? ====

'''A:''' I would start by turning on full Compiler logging.

This is done by selecting the "Full command line" option Under menu "Settings" -> "Compiler and Debugger" -> Global compiler settings -> [the compiler you use] -> "Other Setting" tab, "Compiler logging".

This option will make Code::Blocks output the exact commands it uses to compile your code.

Things to remember:

* You should review all the commands and their options;
* If you have compiled your app before, do a ''re-''build (or ''clean'' before build) to see all compiling / linking steps;
* If you don't know what an option or a command does please read the documentation for the compiler/linker you're using;
* Look for missing commands;
* For every source file (<tt>.cpp</tt>; <tt>.c</tt>; <tt>.d</tt>; etc) in your project, you must have at least one command in the log. This command must produce an object file (file extension <tt>.o</tt> if using gcc/g++ and <tt>.obj</tt> if using Visual Studio);
* Every object file should be linked in the final executable, if not there are undefined symbols errors;
* Remember the file extension matters: <tt>*.c</tt> is compiled as C file, <tt>*.cpp</tt> is compiled as C++ file. [http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html Read more]

==== Q: What do I need to know when using 3rd party libs? ====
Here are some basics about typical mistakes done when working with third party libs, including wxWidgets. The following is valid for ''every'' third party SDK / toolbox / component you want to use and describes what steps your have to do:

* Download the sources of the component OR a ready-to-use development version. The difference: While the first requires you to compile the component yourself is will definitely work with your compiler. The latter must be compiled in a compatible way: So a compatible compiler, compatible OS, compatible settings. Inspect the components docs about how to get what you want.
* Place the component sources and compiled parts anywhere you want It is not required to copy such parts to any other folder you might think - in fact, this may even be dangerous in case you overwrite existing files.
* Create a project where you want to use your component.
* In the ''compiler'' settings, point to the folder, where the include files of your component are. For WX this is special, as usually you include like #include <wx/foo.h>. So do ''not'' point to [Component_Folder]\include\wx, but to [Component_Folder]\include instead.
* Note that the compiler only needs to know the interfaces / classes / structures / methods, it will not throw an error about undefined references or alike. The compiler will only complain in case it cannot find references in terms of include files. If thats the case, adjust your project's compiler settings. Keep in mind that you do need to fulfil the requirements of your component itself, too. Thus, wxChart for example will need for wxWidgets, too. So - you may need to do the same process for wxWidgets, too before you can use wxChart - unless you have done that already.
* In the ''linker'' settings, point to the folder where you have your compiled library. A library usually ends with *.a or *.lib. Note that there are generally two types of libs: Static libs (after linking you are done) and Dynamic libs (where you link against an import lib but require another dynamic lib at runtime).
* In the linker settings add the library/libraries you need to link against in the ''right order'' to the list of libs to link against. ''Order matters'' - again, dependencies must be taken into account. Inspect the developers guide of the component to know the dependencies. On Windows, this may include the MSDN, too which tells you what libraries you need to link against for certain symbols you or the library may make use of.
* The linker will never complain about includes it cannot find. Because the linker just links object files or library files together. But the linker may complain about unresolved symbols which you need to provide. So if that happens, either your setup is missing a lib, or the order is wrong.

Again, this is valid for all third party stuff you want to use. Its heavily ''platform'' and ''compiler'' dependent. The IDE should be less of concern for you. Every IDE can be setup in a way it will compile and link your stuff unless you provide everything needed as explained above.

If you don't understand parts written here it is ''strongly'' recommended you start with a book about general programming in C/C++ that covers library handling in more detail.

For the example wxChart in the end is not easy for starters. Usually you need to compile wxWidgets before, then wxChart and usually not all dependencies are explained in the docs and it behaves differently on different OS'es / compilers. Also, wcChart can be compiled in many flavours - so you need to make sure the flavour matches a) your needs and b) the way you compiled wxWidgets.

==== Q: My simple C++ program throws up lots of errors - what is going on? ====

If you have a C++ program like this:

#include <iostream>
int main() {
std::cout << "hello world\n";
}

and when you compile it you get errors like this:

fatal error: iostream: No such file or directory

then you have probably given your source file a .c extension. If you do that, the GCC compiler (and others) will probably attempt to compile the file as a C program, not as C++. You should always give your C++ source files the extension .cpp to make sure the compiler handles them correctly.

==== Q: I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ====

'''A:''' A little documentation problem ^^;. The "default compiler" is usually GCC, so when you imported it with "the default compiler", you told it to use GCC. To fix this situation, go to "Project", "Build Options" and select VC++ Toolkit as your compiler.

Another possibility is to put the Microsoft compiler as the default one. To do this, choose '''''Settings - Compiler''''', choose the Microsoft compiler in the '''''Selected Compiler''''' section (top of dialog box) and press the '''''Set as default''''' button.

From now onwards, for all new projects the Microsoft compiler will be taken by default.

==== Q: When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? ====

'''A:''' You need to add WXUSINGDLL in "Project->Build options->Compiler #defines" and rebuild your project (or create a new project and use the "Using wxWidgets DLL" project option which adds "-DWXUSINGDLL" to Project->Build options->Other options).
Other errors with the same resolution are:
'unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB)' or similar.
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.

==== Q: I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ====

'''A:''' Sorry, no fix for your problem...

Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which come with Visual C++ (VC) which isn't free, unfortunately.

Try buying a full-fledged VC++, or even better, download [http://www.mingw.org/ MinGW]

The libraries that can be obtained free of charge are:

Paths:
(VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
(PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib
(NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

C runtime libs:
LIBC.LIB Single-threaded, static link (VCT3, NSDK)
LIBCMT.LIB Multithreaded, static link (VCT3, NSDK)
MSVCRT.LIB Multithreaded, dynamic link (import library for MSVCR71.DLL) (NSDK)
LIBCD.LIB Single-threaded, static link (debug) (VCT3, NSDK)
LIBCMTD.LIB Multithreaded, static link (debug) (NSDK)
MSVCRTD.LIB Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)

C++ libs:
LIBCP.LIB Single-threaded, static link (VCT3, PSDK)
LIBCPMT.LIB Multithreaded, static link (VCT3)
MSVCPRT.LIB Multithreaded, dynamic link (import library for MSVCP71.dll) (none)
LIBCPD.LIB Single-threaded, static link (debug) (VCT3)
LIBCPMTD.LIB Multithreaded, static link (debug) (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (debug) (none)

Try setting the library linker directories to:
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
C:\Program Files\Microsoft Platform SDK\Lib
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib
in that order.

The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory. Not sure if these would work on 32-bit windows, however, they may if they are
meant to work in 32-bit compatibility mode on the 64-bit processors. Worth a try. Otherwise, you
can link statically to the C++ library instead of using MSVCP71.dll. If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed. Search google for "exports.sed" for detailed steps.

See also: [http://wiki.tcl.tk/2435 tclsh script to extract import .lib from (any?) DLL (MinGW)]

See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp

See also: http://sapdb.2scale.net/moin.cgi/MS_20C_2b_2b_20Toolkit

==== Q: I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll" ====

'''A:''' Make sure you didn't mix up the MSVC headers or libs with the MinGW ones.

==== Q: My build fails with multiple ''undefined reference'' errors? ====

''Example:''
undefined reference to `WSACleanup@8
undefined reference to `WSACleanup@0

'''A:''' Most of the time it is because the required library is not linked with your project. Go to ''Project->Build options...->Linker settings (tab)'' and add the required library or libraries.

If the error includes a line number, it is likely that this is a problem with your code. Track down down your function declarations and implementations. Ensure they all match up, are spelled correctly, and have the correct scope resolution.

''VERY'' often you can get help by just googling for the name of the undefined reference, for this example its "WSACleanup". Usually one of the first links is the SDK documentation, like [http://msdn.microsoft.com/en-us/library/windows/desktop/ms741549%28v=vs.85%29.aspx this from MSDN for WSACleanup]. You'll find there a lot useful information, including what libraries you need to link against, as for the exsample:
'''Requirements'''
* Minimum supported client: Windows 2000 Professional
* Minimum supported server: Windows 2000 Server
* Header: '''Winsock2.h'''
* Library: '''Ws2_32'''.lib
* DLL: '''Ws2_32.dll'''
The header file '''Winsock2.h''' you need to include in your sources. Most likely you have done that already because otherwise you would have gotten a compiler error unable to find the function declaration. The library you need to link against, you can remove any prefix like "lib" and the file extension like ".lib", ".a" or ".so" - so just type "'''Ws2_32'''" in the linker options. Also make sure you have added the path to that library in the linker include path's options, otherwise the linker will complain that it cannot find that library you want to link against. You also know, that you should distribute '''Ws2_32.dll''' for the runtime version of you app, luckily this one usually ships with Windows anyways, so no need to do something here.

==== Q: My build fails in the compile/link/run step with a ''Permission denied'' error? ====

'''A:''' There are several possible causes for this:

# The output directory does not have read/write access.
#* Either change control settings on the output directory, or move the project to different location.
# A previous instance of the executable failed to terminate properly.
#* Open your system's equivalent of Process/Task Manager, search the list for the name of the executable Code::Blocks is trying to output, and terminate it.
#* Logging off or rebooting will achieve the same effect.
# The executable is open.
#* If the executable is open in a hex-editor or actively being run, close it.
# Security software is interfering.
#* The target file is locked while an antivirus programming is scanning it; either wait a few seconds for the antivirus scan to finish, set an exception in the antivirus settings, or (temporarily) disable the antivirus program.
#* Firewalls with very strict settings sometimes block execution; try reducing the firewall's settings or adding an exception.
#* Switching security software may have left traces behind that are interfering; hunt down the remnants of the old antivirus/firewall software and remove them.
# The file/library cannot be found.
#* Double check all of the compiler and linker [[FAQ-Compiling (general)#Q: I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?|search directories]] (including any [[Global compiler variables|variables]] they may be using) are properly setup.
# Code::Blocks was improperly installed.
#* Mixing binaries from a stable release and a nightly build (or even two different nightly builds) is highly likely to cause a slew of problems; [[Installing Code::Blocks|reinstall Code::Blocks]] in an empty directory.
# Multiple installed compilers are interfering with each other.
#* If they are not required to keep, completely remove all but the most used compiler.
#* If several compilers are required, ensure that '''none''' of them are in the ''system'' path (this is so that Code::Blocks will be able to manage all paths).
#* Also, do not place any compilers in their default installation path (for example <tt>C:\MinGW</tt>), as some compilers are hard-coded to look for headers in a default path ''before'' searching their own respective directories.
# On windows 7, the service "Application Experience" is not running [http://stackoverflow.com/questions/7655471/ld-exe-cannot-open-output-file-permission-denied#answer-7904469 as explained on stackoverflow].
See also: [/index.php/topic,15047.0.html Permission denied forums discussion]

==== Q: My build fails to link due to ''multiple definition of xyz'' errors? ====

'''A:''' GCC 4.6.1 mingw target (Windows) is known to occasionally (and erroneously) report this if link-time optimization (<tt>-flto</tt>) is used.

First, of course, check that no token has been defined multiple times. If the source code is clean, and yet the errors persist, adding linker switch (''Project->Build options...->Linker settings (tab)'')
-Wl,--allow-multiple-definition
will enable the code to link.

See also: [http://sourceware.org/bugzilla/show_bug.cgi?id=12762 Bug 12762]

----

Return to '''[[FAQ]]'''.

FAQ

2012-12-25T12:36:58Z

MortenMacFly: /* Compiling (errors) */

[[Category:Code::Blocks Documentation]]

== [[FAQ-General|General]] ==

* '''[[FAQ-General#Q: What is Code::Blocks?|What is Code::Blocks?]]'''
* '''[[FAQ-General#Q: What Code::Blocks is not?|What Code::Blocks is not?]]'''
* '''[[FAQ-General#Q: What license is Code::Blocks released under?|What license is Code::Blocks released under?]]'''
* '''[[FAQ-General#Q: When will the next stable version of Code::Blocks be released?|When will the next stable version of Code::Blocks be released?]]'''
* '''[[FAQ-General#Q: Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret?|Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret?]]'''

== [[FAQ-Compiling (general)|Compiling (general)]] ==

* '''[[FAQ-Compiling (general)#Q: What compiler can I use with Code::Blocks?|What compiler can I use with Code::Blocks?]]'''
* '''[[FAQ-Compiling (general)#Q: My project should be compiled with a custom makefile. Is it possible with Code::Blocks?|My project should be compiled with a custom makefile. Is it possible with Code::Blocks?]]'''
* '''[[FAQ-Compiling (general)#Q: I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler?|I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler?]]'''
* '''[[FAQ-Compiling (general)#Q: Microsoft calls MSVCRT.DLL a "Known DLL." How do I know if I can/should use it?|Microsoft calls MSVCRT.DLL a "Known DLL." How do I know if I can/should use it?]]'''
* '''[[FAQ-Compiling (general)#Q: How can I use a DLL without DEF or LIB files?|How can I use a DLL without DEF or LIB files?]]'''
* '''[[FAQ-Compiling (general)#Q: Where are the libraries for the OpenGL, Ogre3D, SDL, QT, wxWidgets etc. projects?|Where are the libraries for the OpenGL, Ogre3D, SDL, QT, wxWidgets etc. projects?]]'''
* '''[[FAQ-Compiling (general)#Q: Is it possible to use Visual C++ 6.0 with Code::Blocks?|Is it possible to use Visual C++ 6.0 with Code::Blocks?]]'''
* '''[[FAQ-Compiling (general)#Q: I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?|I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?]]'''
* '''[[FAQ-Compiling (general)#Q: How do I use both Debug and Release builds of wx libraries?|How do I use both Debug and Release builds of wx libraries?]]'''
* '''[[FAQ-Compiling (general)#Q: How do I add version information to windows executables and dll's?|How do I add version information to windows executables and dll's?]]'''
* '''[[FAQ-Compiling (general)#Q: Code::Blocks does not force relink if the library is changed?|Code::Blocks does not force relink if the library is changed?]]'''
* '''[[FAQ-Compiling (general)#Q: How do I report a compilation problem on the forums?|How do I report a compilation problem on the forums?]]'''
* '''[[FAQ-Compiling (general)#Q: All of the Build related options are grayed out?|All of the Build related options are grayed out?]]'''

== [[FAQ-Compiling (errors)|Compiling (errors)]] ==

* '''[[FAQ-Compiling (errors)#Q: How do I troubleshoot a compiler problem?|How do I troubleshoot a compiler problem?]]'''
* '''[[FAQ-Compiling (errors)#Q: What so I need to know when using 3rd party libs?|What so I need to know when using 3rd party libs?]]'''
* '''[[FAQ-Compiling (errors)#Q: My simple C++ program throws up lots of errors - what is going on?|My simple C++ program throws up lots of errors - what is going on?]]'''
* '''[[FAQ-Compiling (errors)#Q: I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong?|I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong?]]'''
* '''[[FAQ-Compiling (errors)#Q: When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong?|When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong?]]'''
* '''[[FAQ-Compiling (errors)#Q: I can't compile a multithreaded app with VC Toolkit! Where are the libraries?|I can't compile a multithreaded app with VC Toolkit! Where are the libraries?]]'''
* '''[[FAQ-Compiling (errors)#Q: I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll"|I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll"]]'''
* '''[[FAQ-Compiling (errors)#Q: My build fails with multiple undefined reference errors?|My build fails with multiple ''undefined reference'' errors?]]'''
* '''[[FAQ-Compiling (errors)#Q: My build fails in the compile/link/run step with a Permission denied error?|My build fails in the compile/link/run step with a ''Permission denied'' error?]]'''
* '''[[FAQ-Compiling (errors)#Q: My build fails to link due to multiple definition of xyz errors?|My build fails to link due to ''multiple definition of xyz'' errors?]]'''

== [[FAQ-Settings|Settings]] ==

* '''[[FAQ-Settings#Q: How do I get Code Completion to work?|How do I get Code Completion to work?]]'''
* '''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|How do I make Code::Blocks portable?]]'''
* '''[[FAQ-Settings#Q: Code::Blocks option xyz is missing?|Code::Blocks option ''xyz'' is missing?]]'''
* '''[[FAQ-Settings#Q: How do I change the default location of the output terminal?|How do I change the default location of the output terminal?]]'''

== [[FAQ-Issues and Workarounds|Issues and Workarounds]] ==

* '''[[FAQ-Issues and Workarounds#Q: Sometime, in the text editor, space bar triggers Code Completion, how do I fix that?|Sometime, in the text editor, space bar triggers Code Completion, how do I fix that?]]'''
* '''[[FAQ-Issues and Workarounds#Q: IDE is drawing the text from Right to Left?|IDE is drawing the text from Right to Left?]]'''
* '''[[FAQ-Issues and Workarounds#Q: All the options in the debug menu are grayed out?|All the options in the debug menu are grayed out?]]'''
* '''[[FAQ-Issues and Workarounds#Q: My project works everywhere except one computer?|My project works everywhere except one computer?]]'''
* '''[[FAQ-Issues and Workarounds#Q: Syntax highlighting is broken; how do I fix it?|Syntax highlighting is broken; how do I fix it?]]'''
* '''[[FAQ-Issues and Workarounds#Q: I posted on the forums that Code::Blocks was not working, but no one could help me?|I posted on the forums that Code::Blocks was not working, but no one could help me?]]'''
* '''[[FAQ-Issues and Workarounds#Q: I cannot find any text in my Code::Blocks logs?|I cannot find any text in my Code::Blocks logs?]]'''
* '''[[FAQ-Issues and Workarounds#Q: Scrolling causes gray areas/distortions to obscure my code in the editor?|Scrolling causes gray areas/distortions to obscure my code in the editor?]]'''
* '''[[FAQ-Issues and Workarounds#Q: I cannot type a greater-than '>' sign?|I cannot type a greater-than '>' sign?]]'''

FAQ-Compiling (errors)

2012-12-25T12:34:46Z

MortenMacFly: /* Q: What so I need to know when using 3rd party libs? */

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: How do I troubleshoot a compiler problem? ====

'''A:''' I would start by turning on full Compiler logging.

This is done by selecting the "Full command line" option Under menu "Settings" -> "Compiler and Debugger" -> Global compiler settings -> [the compiler you use] -> "Other Setting" tab, "Compiler logging".

This option will make Code::Blocks output the exact commands it uses to compile your code.

Things to remember:

* You should review all the commands and their options;
* If you have compiled your app before, do a ''re-''build (or ''clean'' before build) to see all compiling / linking steps;
* If you don't know what an option or a command does please read the documentation for the compiler/linker you're using;
* Look for missing commands;
* For every source file (<tt>.cpp</tt>; <tt>.c</tt>; <tt>.d</tt>; etc) in your project, you must have at least one command in the log. This command must produce an object file (file extension <tt>.o</tt> if using gcc/g++ and <tt>.obj</tt> if using Visual Studio);
* Every object file should be linked in the final executable, if not there are undefined symbols errors;
* Remember the file extension matters: <tt>*.c</tt> is compiled as C file, <tt>*.cpp</tt> is compiled as C++ file. [http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html Read more]

==== Q: What so I need to know when using 3rd party libs? ====
Here are some basics about typical mistakes done when working with third party libs, including wxWidgets. The following is valid for ''every'' third party SDK / toolbox / component you want to use and describes what steps your have to do:

* Download the sources of the component OR a ready-to-use development version. The difference: While the first requires you to compile the component yourself is will definitely work with your compiler. The latter must be compiled in a compatible way: So a compatible compiler, compatible OS, compatible settings. Inspect the components docs about how to get what you want.
* Place the component sources and compiled parts anywhere you want It is not required to copy such parts to any other folder you might think - in fact, this may even be dangerous in case you overwrite existing files.
* Create a project where you want to use your component.
* In the ''compiler'' settings, point to the folder, where the include files of your component are. For WX this is special, as usually you include like #include <wx/foo.h>. So do ''not'' point to [Component_Folder]\include\wx, but to [Component_Folder]\include instead.
* Note that the compiler only needs to know the interfaces / classes / structures / methods, it will not throw an error about undefined references or alike. The compiler will only complain in case it cannot find references in terms of include files. If thats the case, adjust your project's compiler settings. Keep in mind that you do need to fulfil the requirements of your component itself, too. Thus, wxChart for example will need for wxWidgets, too. So - you may need to do the same process for wxWidgets, too before you can use wxChart - unless you have done that already.
* In the ''linker'' settings, point to the folder where you have your compiled library. A library usually ends with *.a or *.lib. Note that there are generally two types of libs: Static libs (after linking you are done) and Dynamic libs (where you link against an import lib but require another dynamic lib at runtime).
* In the linker settings add the library/libraries you need to link against in the ''right order'' to the list of libs to link against. ''Order matters'' - again, dependencies must be taken into account. Inspect the developers guide of the component to know the dependencies. On Windows, this may include the MSDN, too which tells you what libraries you need to link against for certain symbols you or the library may make use of.
* The linker will never complain about includes it cannot find. Because the linker just links object files or library files together. But the linker may complain about unresolved symbols which you need to provide. So if that happens, either your setup is missing a lib, or the order is wrong.

Again, this is valid for all third party stuff you want to use. Its heavily ''platform'' and ''compiler'' dependent. The IDE should be less of concern for you. Every IDE can be setup in a way it will compile and link your stuff unless you provide everything needed as explained above.

If you don't understand parts written here it is ''strongly'' recommended you start with a book about general programming in C/C++ that covers library handling in more detail.

For the example wxChart in the end is not easy for starters. Usually you need to compile wxWidgets before, then wxChart and usually not all dependencies are explained in the docs and it behaves differently on different OS'es / compilers. Also, wcChart can be compiled in many flavours - so you need to make sure the flavour matches a) your needs and b) the way you compiled wxWidgets.

==== Q: My simple C++ program throws up lots of errors - what is going on? ====

If you have a C++ program like this:

#include <iostream>
int main() {
std::cout << "hello world\n";
}

and when you compile it you get errors like this:

fatal error: iostream: No such file or directory

then you have probably given your source file a .c extension. If you do that, the GCC compiler (and others) will probably attempt to compile the file as a C program, not as C++. You should always give your C++ source files the extension .cpp to make sure the compiler handles them correctly.

==== Q: I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ====

'''A:''' A little documentation problem ^^;. The "default compiler" is usually GCC, so when you imported it with "the default compiler", you told it to use GCC. To fix this situation, go to "Project", "Build Options" and select VC++ Toolkit as your compiler.

Another possibility is to put the Microsoft compiler as the default one. To do this, choose '''''Settings - Compiler''''', choose the Microsoft compiler in the '''''Selected Compiler''''' section (top of dialog box) and press the '''''Set as default''''' button.

From now onwards, for all new projects the Microsoft compiler will be taken by default.

==== Q: When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? ====

'''A:''' You need to add WXUSINGDLL in "Project->Build options->Compiler #defines" and rebuild your project (or create a new project and use the "Using wxWidgets DLL" project option which adds "-DWXUSINGDLL" to Project->Build options->Other options).
Other errors with the same resolution are:
'unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB)' or similar.
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.

==== Q: I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ====

'''A:''' Sorry, no fix for your problem...

Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which come with Visual C++ (VC) which isn't free, unfortunately.

Try buying a full-fledged VC++, or even better, download [http://www.mingw.org/ MinGW]

The libraries that can be obtained free of charge are:

Paths:
(VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
(PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib
(NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

C runtime libs:
LIBC.LIB Single-threaded, static link (VCT3, NSDK)
LIBCMT.LIB Multithreaded, static link (VCT3, NSDK)
MSVCRT.LIB Multithreaded, dynamic link (import library for MSVCR71.DLL) (NSDK)
LIBCD.LIB Single-threaded, static link (debug) (VCT3, NSDK)
LIBCMTD.LIB Multithreaded, static link (debug) (NSDK)
MSVCRTD.LIB Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)

C++ libs:
LIBCP.LIB Single-threaded, static link (VCT3, PSDK)
LIBCPMT.LIB Multithreaded, static link (VCT3)
MSVCPRT.LIB Multithreaded, dynamic link (import library for MSVCP71.dll) (none)
LIBCPD.LIB Single-threaded, static link (debug) (VCT3)
LIBCPMTD.LIB Multithreaded, static link (debug) (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (debug) (none)

Try setting the library linker directories to:
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
C:\Program Files\Microsoft Platform SDK\Lib
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib
in that order.

The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory. Not sure if these would work on 32-bit windows, however, they may if they are
meant to work in 32-bit compatibility mode on the 64-bit processors. Worth a try. Otherwise, you
can link statically to the C++ library instead of using MSVCP71.dll. If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed. Search google for "exports.sed" for detailed steps.

See also: [http://wiki.tcl.tk/2435 tclsh script to extract import .lib from (any?) DLL (MinGW)]

See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp

See also: http://sapdb.2scale.net/moin.cgi/MS_20C_2b_2b_20Toolkit

==== Q: I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll" ====

'''A:''' Make sure you didn't mix up the MSVC headers or libs with the MinGW ones.

==== Q: My build fails with multiple ''undefined reference'' errors? ====

''Example:''
undefined reference to `WSACleanup@8
undefined reference to `WSACleanup@0

'''A:''' Most of the time it is because the required library is not linked with your project. Go to ''Project->Build options...->Linker settings (tab)'' and add the required library or libraries.

If the error includes a line number, it is likely that this is a problem with your code. Track down down your function declarations and implementations. Ensure they all match up, are spelled correctly, and have the correct scope resolution.

''VERY'' often you can get help by just googling for the name of the undefined reference, for this example its "WSACleanup". Usually one of the first links is the SDK documentation, like [http://msdn.microsoft.com/en-us/library/windows/desktop/ms741549%28v=vs.85%29.aspx this from MSDN for WSACleanup]. You'll find there a lot useful information, including what libraries you need to link against, as for the exsample:
'''Requirements'''
* Minimum supported client: Windows 2000 Professional
* Minimum supported server: Windows 2000 Server
* Header: '''Winsock2.h'''
* Library: '''Ws2_32'''.lib
* DLL: '''Ws2_32.dll'''
The header file '''Winsock2.h''' you need to include in your sources. Most likely you have done that already because otherwise you would have gotten a compiler error unable to find the function declaration. The library you need to link against, you can remove any prefix like "lib" and the file extension like ".lib", ".a" or ".so" - so just type "'''Ws2_32'''" in the linker options. Also make sure you have added the path to that library in the linker include path's options, otherwise the linker will complain that it cannot find that library you want to link against. You also know, that you should distribute '''Ws2_32.dll''' for the runtime version of you app, luckily this one usually ships with Windows anyways, so no need to do something here.

==== Q: My build fails in the compile/link/run step with a ''Permission denied'' error? ====

'''A:''' There are several possible causes for this:

# The output directory does not have read/write access.
#* Either change control settings on the output directory, or move the project to different location.
# A previous instance of the executable failed to terminate properly.
#* Open your system's equivalent of Process/Task Manager, search the list for the name of the executable Code::Blocks is trying to output, and terminate it.
#* Logging off or rebooting will achieve the same effect.
# The executable is open.
#* If the executable is open in a hex-editor or actively being run, close it.
# Security software is interfering.
#* The target file is locked while an antivirus programming is scanning it; either wait a few seconds for the antivirus scan to finish, set an exception in the antivirus settings, or (temporarily) disable the antivirus program.
#* Firewalls with very strict settings sometimes block execution; try reducing the firewall's settings or adding an exception.
#* Switching security software may have left traces behind that are interfering; hunt down the remnants of the old antivirus/firewall software and remove them.
# The file/library cannot be found.
#* Double check all of the compiler and linker [[FAQ-Compiling (general)#Q: I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?|search directories]] (including any [[Global compiler variables|variables]] they may be using) are properly setup.
# Code::Blocks was improperly installed.
#* Mixing binaries from a stable release and a nightly build (or even two different nightly builds) is highly likely to cause a slew of problems; [[Installing Code::Blocks|reinstall Code::Blocks]] in an empty directory.
# Multiple installed compilers are interfering with each other.
#* If they are not required to keep, completely remove all but the most used compiler.
#* If several compilers are required, ensure that '''none''' of them are in the ''system'' path (this is so that Code::Blocks will be able to manage all paths).
#* Also, do not place any compilers in their default installation path (for example <tt>C:\MinGW</tt>), as some compilers are hard-coded to look for headers in a default path ''before'' searching their own respective directories.
# On windows 7, the service "Application Experience" is not running [http://stackoverflow.com/questions/7655471/ld-exe-cannot-open-output-file-permission-denied#answer-7904469 as explained on stackoverflow].
See also: [/index.php/topic,15047.0.html Permission denied forums discussion]

==== Q: My build fails to link due to ''multiple definition of xyz'' errors? ====

'''A:''' GCC 4.6.1 mingw target (Windows) is known to occasionally (and erroneously) report this if link-time optimization (<tt>-flto</tt>) is used.

First, of course, check that no token has been defined multiple times. If the source code is clean, and yet the errors persist, adding linker switch (''Project->Build options...->Linker settings (tab)'')
-Wl,--allow-multiple-definition
will enable the code to link.

See also: [http://sourceware.org/bugzilla/show_bug.cgi?id=12762 Bug 12762]

----

Return to '''[[FAQ]]'''.

Talk:Compile Code::Blocks plugins based on a nightly

2012-08-23T06:23:51Z

MortenMacFly:

When linking directly to a <tt>dll</tt> (with MinGW), the file extension is not required, so <tt>wxmsw28u_gcc_cb.dll</tt> can be simply <tt>wxmsw28u_gcc_cb</tt> and <tt>codeblocks</tt> can remain the unchanged. [[User:Alpha|Alpha]] 03:26, 23 August 2012 (CEST)

I think the mingw gcc version should match the version build nightlies, other wise, there may be some conflict with symbols or other things, currently our nightlies use tdm gcc 4.5.x. [[User:Ollydbg|Ollydbg]] 03:52, 23 August 2012 (CEST)

Yes and yes - however, for Alphas point I wanted to make sure users really understand they are linking against a DLL. Ollydbg: That is certainly true, so it should be mentioned.

...btw: How do you get this nice tag like "Alpha 03:26, 23 August 2012 (CEST)"??? I guess I am using the talk board in a wrong way?

Compile Code::Blocks plugins based on a nightly

2012-08-23T06:20:40Z

MortenMacFly:

First, a general note: This article applies to '''Windows/MinGW compiler only''' for the moment, feel free to extend the article, if you see a similar possibility on other platforms.

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here] ''but exactly the version, the nightly is built on''.
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The MinGW/GCC compiler used to build the nightly - as written in the nightly section and usually available from here [http://tdm-gcc.tdragon.net here]. Note that the version (i.e. v4.5.2) ''and'' flavour (i.e. sjlj or dwarf) ''must'' match. Usually this information is available [/index.php/topic,3299.msg26011.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a:
svn checkout svn://somepath@1234 working-directory
...on the command line (having the [https://subversion.apache.org Subversion tools] installed properly). For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on. Luckily, the SDK is quite stable and existing (stable) plugins rarely change to make use of new SDK methods.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** Change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** Change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly). Note that this change might actually not be needed as MinGW automatically looks for files with the extension *.dll, too...
* Goto the "search directories" settings
** Change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** Change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.
* Goto the plugin's project options
** Adjust the objects output folder, if desired
** Adjust the plugin's output file name and path, if desired
** Adjust the execution working directory, if desired

Now you should be able to compile and link the plugin successfully. This will create a plugin version compatible to that nightly. Voilà - feel free to share it with others afterwards.

Compile Code::Blocks plugins based on a nightly

2012-08-23T06:19:19Z

MortenMacFly:

First, a general note: This article applies to '''Windows/MinGW compiler only''' for the moment, feel free to extend the article, if you see a similar possibility on other platforms.

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here] ''but exactly the version, the nightly is built on''.
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The MinGW/GCC compiler used to build the nightly - as written in the nightly section and usually available from here [http://tdm-gcc.tdragon.net here]. Note that the version (i.e. v4.5.2) ''and'' flavour (i.e. dwarf) ''must'' match. Usually this information is available [/index.php/topic,3299.msg26011.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a:
svn checkout svn://somepath@1234 working-directory
...on the command line (having the [https://subversion.apache.org Subversion tools] installed properly). For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on. Luckily, the SDK is quite stable and existing (stable) plugins rarely change to make use of new SDK methods.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** Change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** Change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly). Note that this change might actually not be needed as MinGW automatically looks for files with the extension *.dll, too...
* Goto the "search directories" settings
** Change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** Change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.
* Goto the plugin's project options
** Adjust the objects output folder, if desired
** Adjust the plugin's output file name and path, if desired
** Adjust the execution working directory, if desired

Now you should be able to compile and link the plugin successfully. This will create a plugin version compatible to that nightly. Voilà - feel free to share it with others afterwards.

Compile Code::Blocks plugins based on a nightly

2012-08-23T06:16:56Z

MortenMacFly:

First, a general note: This article applies to '''Windows/MinGW compiler only''' for the moment, feel free to extend the article, if you see a similar possibility on other platforms.

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here] ''but exactly the version, the nightly is built on''.
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The MinGW/GCC compiler used to build the nightly - as written in the nightly section and usually available from here [http://tdm-gcc.tdragon.net here]. Note that the version (i.e. v4.5.2 ''and'' flavour (i.e. dwarf) ''must'' match. Usually this information is available [/index.php/topic,3299.msg26011.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a:
svn checkout svn://somepath@1234 working-directory
...on the command line (having the [https://subversion.apache.org Subversion tools] installed properly). For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on. Luckily, the SDK is quite stable and existing (stable) plugins rarely change to make use of new SDK methods.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** Change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** Change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly). Note that this change might actually not be needed as MinGW automatically looks for files with the extension *.dll, too...
* Goto the "search directories" settings
** Change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** Change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.
* Goto the plugin's project options
** Adjust the objects output folder, if desired
** Adjust the plugin's output file name and path, if desired
** Adjust the execution working directory, if desired

Now you should be able to compile and link the plugin successfully. This will create a plugin version compatible to that nightly. Voilà - feel free to share it with others afterwards.

Talk:Compile Code::Blocks plugins based on a nightly

2012-08-23T06:10:17Z

MortenMacFly:

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:30:06Z

MortenMacFly:

First, a general note: This article applies to '''Windows/MinGW compiler only''' for the moment, feel free to extend the article, if you see a similar possibility on other platforms.

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here] ''but exactly the version, the nightly is built on''.
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a:
svn checkout svn://somepath@1234 working-directory
...on the command line (having the [https://subversion.apache.org Subversion tools] installed properly). For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on. Luckily, the SDK is quite stable and existing (stable) plugins rarely change to make use of new SDK methods.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly)
* Goto the "search directories" settings
** change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.
* Goto the plugin's project options
** Adjust the objects output folder, if desired
** Adjust the plugin's output file name and path, if desired
** Adjust the execution working directory, if desired

Now you should be able to compile and link the plugin successfully. This will create a plugin version compatible to that nightly. Voilà - feel free to share it with others afterwards.

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:28:33Z

MortenMacFly:

First, a general note: This article applies to '''Windows/MinGW compiler only''' for the moment, feel free to extend the article, if you see a similar possibility on other platforms.

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here] ''but exactly the version, the nightly is built on''.
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a:
svn checkout svn://somepath@1234 working-directory
...on the command line (having the [https://subversion.apache.org Subversion tools] installed properly). For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly)
* Goto the "search directories" settings
** change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.
* Goto the plugin's project options
** Adjust the objects output folder, if desired
** Adjust the plugin's output file name and path, if desired
** Adjust the execution working directory, if desired

Now you should be able to compile and link the plugin successfully. This will create a plugin version compatible to that nightly. Voilà - feel free to share it with others afterwards.

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:26:58Z

MortenMacFly:

First, a general note: This article applies to '''Windows/MinGW compiler only''' for the moment, feel free to extend the article, if you see a similar possibility on other platforms.

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here] ''but exactly the version, the nightly is built on''.
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a
svn checkout svn://somepath@1234 working-directory
For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly)
* Goto the "search directories" settings
** change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.
* Goto the plugin's project options
** Adjust the objects output folder, if desired
** Adjust the plugin's output file name and path, if desired
** Adjust the execution working directory, if desired

Now you should be able to compile and link the plugin successfully. This will create a plugin version compatible to that nightly. Voilà - feel free to share it with others afterwards.

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:26:34Z

MortenMacFly:

First, a general note: This article applies to '''Windows/MinGW compiler only''' for the moment, feel free to extend the article, if you see a similar possibility on other platforms.

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here].
* A nightly of your choice, download from [/index.php/board,20.0.html here] ''but exactly the version, the nightly is built on''.
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a
svn checkout svn://somepath@1234 working-directory
For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly)
* Goto the "search directories" settings
** change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.
* Goto the plugin's project options
** Adjust the objects output folder, if desired
** Adjust the plugin's output file name and path, if desired
** Adjust the execution working directory, if desired

Now you should be able to compile and link the plugin successfully. This will create a plugin version compatible to that nightly. Voilà - feel free to share it with others afterwards.

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:19:19Z

MortenMacFly:

First, a general note: This article applies to '''Windows/MinGW compiler only''' for the moment, feel free to extend the article, if you see a similar possibility on other platforms.

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here].
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a
svn checkout svn://somepath@1234 working-directory
For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly)
* Goto the "search directories" settings
** change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.
* Goto the plugin's project options
** Adjust the objects output folder, if desired
** Adjust the plugin's output file name and path, if desired
** Adjust the execution working directory, if desired

Now you should be able to compile and link the plugin successfully. This will create a plugin version compatible to that nightly. Voilà - feel free to share it with others afterwards.

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:18:54Z

MortenMacFly:

First, a general note: This article applies to '''Windows/MinGW compiler only''' for the moment, feel free to extend the article, if you see a similar possibility on other platforms.

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here].
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a
svn checkout svn://somepath@1234 working-directory
For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however)) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly)
* Goto the "search directories" settings
** change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.
* Goto the plugin's project options
** Adjust the objects output folder, if desired
** Adjust the plugin's output file name and path, if desired
** Adjust the execution working directory, if desired

Now you should be able to compile and link the plugin successfully. This will create a plugin version compatible to that nightly. Voilà - feel free to share it with others afterwards.

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:14:04Z

MortenMacFly:

'''UNDER CONSTRUCTION'''

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here].
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a
svn checkout svn://somepath@1234 working-directory
For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however)) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly)
* Goto the "search directories" settings
** change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
* Note that you might need to do this at project and target level - depending on how the plugin is setup.
* Try to compile and resolve any remaining issues which can only occur, in case you didn't do the above steps carefully.

Now you should be able tom compile and link successfully the plugin. This will create a plugin version compatible to that nightly. Voila - feel free to share it with others afterwards.

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:10:56Z

MortenMacFly:

'''UNDER CONSTRUCTION'''

So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plugin in your favourite nightly? Its possible. Here is what you need:

* The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here].
* A nightly of your choice, download from [/index.php/board,20.0.html here].
* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a
svn checkout svn://somepath@1234 working-directory
For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
* The sources of the plugin / component you want to change should be included in this checkout, you can (however)) update the specific folder to SVN HEAD, if you like.

One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on.

Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.

Do the following:
* Goto the plugin's build options
* Goto linker settings
** change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
** change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly)
* Goto the "search directories" settings
** change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
** change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).

Note that you might need to do this at project and target level - depending on how the plugin is setup.

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:07:37Z

MortenMacFly:

Compile Code::Blocks plugins based on a nightly

2012-08-22T20:02:25Z

MortenMacFly:

Compile Code::Blocks plugins based on a nightly

2012-08-22T19:57:35Z

MortenMacFly:

Compile Code::Blocks plugins based on a nightly

2012-08-22T19:54:31Z

MortenMacFly:

Compile Code::Blocks plugins based on a nightly

2012-08-22T19:53:43Z

MortenMacFly: Created page with "'''UNDER CONSTRUCTION''' So, you don't want to compile wxWidgets or Code::Blocks core but still want to be able to modify a certain plugin (for example) and use the modified plu..."

Developer documentation

2012-08-22T19:50:47Z

MortenMacFly:

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
{{Layout_box2|1=
'''Code repository''' 
* Web-interface by ViewVC: http://svn.berlios.de/viewcvs/codeblocks/trunk/ 
* Subversion URL: <nowiki>http://svn.berlios.de/svnroot/repos/codeblocks/trunk</nowiki>

'''Mirror''' (Read-only; refreshed every 30 minutes.)
* Subversion URL: <nowiki>svn://cb.biplab.in/codeblocks/trunk</nowiki> 
* Web-interface: http://cb.biplab.in/websvn/
* Git URL: git://cb.biplab.in/codeblocks.git
* Web-interface:http://cb.biplab.in/cgit/
}}

'''Articles for Code::Blocks developers.'''

* '''Documentation'''
:[https://www.codeblocks.org/manual.shtml User's manual] in various formats and languages.
:Also see http://developer.berlios.de/projects/codeblocks/ (under the downloads section).
:Checkout the SDK documentation at http://developer.berlios.de/project/showfiles.php?group_id=5358 as CHM file(s).

* Compile the complete Code::Blocks from sources on '''[[Installing Code::Blocks from source on Windows|Windows]]''' and '''[[Installing Code::Blocks from source on Linux|Linux]]'''

* '''[[Compile Code::Blocks plugins based on a nightly]]''' w/o the need to compile wxWidgets or the Code::Blocks core.

* '''[http://launchpad.net/products/codeblocks/ Translation]'''
:Code::Blocks uses Launchpad to coordinate translation efforts.

* '''[[Coding style]]'''
:The source code formatting style used in the Code::Blocks' source.

* '''[[Creating a custom lexer for Code::Blocks editor]]'''
:How to add support for new syntax lighting schemes.

* '''[[Creating a patch to submit to BerliOS (Patch Tracker)]]'''
:Creating a diff file and then submitting it to the patch tracker.

* '''[[Unicode Standards]]'''
:Information about unicode standards and how unicode is handled in Code::Blocks' source code.

* '''[[Various development tips]]'''
:List of various development tips for Code::Blocks.

* '''[[Scripting Code::Blocks]]'''
:Information about scripting Code::Blocks with [http://www.squirrel-lang.org/ Squirrel].

* '''[[A short overview about Code::Blocks architecture]]'''
:Information about the architecture of Code::Blocks.

* '''[[Code::Blocks SDK events]]'''
:Information about the Code::Blocks SDK events and how to work with them.

* '''[[File formats description]]'''
:Description of the format of each file Code::Blocks produces.

* '''[[Version control]]'''
:Tips and trick for working with our version control system.

== Plug-In development ==

* [[Creating a simple "Hello World" plugin]]
* [[Creating a Plug-in which modifies CB's Menus]]
* [[Creating a plugin that actually does something]]
* [[Linking the plugin to a Nightly Build]]
* [[Managing Plug-in Resources]]

* [[Research on doing a Plug-in for embedded help in CB]]

* [[wxSmith extensions]]
* [[Code::Completion Rewrite]] and [[Code Completion plugin]] and [[Code Completion Design]]

== Scripting ==

Using scripting to extend Code::Blocks' functionality

* [[Wizard scripts|Creating a new project wizard]]

== Debugging C::B ==

When C::B crashed, it will generate a call-stack file "codeblocks.RPT", at the crash point, this is a text file, you can open it, if your C::B contains the debug information, it will have file and line information about each call. If it is a stripped version, but you have the debug version of C::B, you can try to run the [/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is a address2line UI interface works under Windows.

Developer documentation

2012-08-22T19:50:26Z

MortenMacFly:

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
{{Layout_box2|1=
'''Code repository''' 
* Web-interface by ViewVC: http://svn.berlios.de/viewcvs/codeblocks/trunk/ 
* Subversion URL: <nowiki>http://svn.berlios.de/svnroot/repos/codeblocks/trunk</nowiki>

'''Mirror''' (Read-only; refreshed every 30 minutes.)
* Subversion URL: <nowiki>svn://cb.biplab.in/codeblocks/trunk</nowiki> 
* Web-interface: http://cb.biplab.in/websvn/
* Git URL: git://cb.biplab.in/codeblocks.git
* Web-interface:http://cb.biplab.in/cgit/
}}

'''Articles for Code::Blocks developers.'''

* '''Documentation'''
:[https://www.codeblocks.org/manual.shtml User's manual] in various formats and languages.
:Also see http://developer.berlios.de/projects/codeblocks/ (under the downloads section).
:Checkout the SDK documentation at http://developer.berlios.de/project/showfiles.php?group_id=5358 as CHM file(s).

* Compile the complete Code::Blocks from sources on '''[[Installing Code::Blocks from source on Windows|Windows]]''' and '''[[Installing Code::Blocks from source on Linux|Linux]]'''

* '''[[Compile Code::Blocks plugins based on a nightly]]]''' w/o the need to compile wxWidgets or the Code::Blocks core.

* '''[http://launchpad.net/products/codeblocks/ Translation]'''
:Code::Blocks uses Launchpad to coordinate translation efforts.

* '''[[Coding style]]'''
:The source code formatting style used in the Code::Blocks' source.

* '''[[Creating a custom lexer for Code::Blocks editor]]'''
:How to add support for new syntax lighting schemes.

* '''[[Creating a patch to submit to BerliOS (Patch Tracker)]]'''
:Creating a diff file and then submitting it to the patch tracker.

* '''[[Unicode Standards]]'''
:Information about unicode standards and how unicode is handled in Code::Blocks' source code.

* '''[[Various development tips]]'''
:List of various development tips for Code::Blocks.

* '''[[Scripting Code::Blocks]]'''
:Information about scripting Code::Blocks with [http://www.squirrel-lang.org/ Squirrel].

* '''[[A short overview about Code::Blocks architecture]]'''
:Information about the architecture of Code::Blocks.

* '''[[Code::Blocks SDK events]]'''
:Information about the Code::Blocks SDK events and how to work with them.

* '''[[File formats description]]'''
:Description of the format of each file Code::Blocks produces.

* '''[[Version control]]'''
:Tips and trick for working with our version control system.

== Plug-In development ==

* [[Creating a simple "Hello World" plugin]]
* [[Creating a Plug-in which modifies CB's Menus]]
* [[Creating a plugin that actually does something]]
* [[Linking the plugin to a Nightly Build]]
* [[Managing Plug-in Resources]]

* [[Research on doing a Plug-in for embedded help in CB]]

* [[wxSmith extensions]]
* [[Code::Completion Rewrite]] and [[Code Completion plugin]] and [[Code Completion Design]]

== Scripting ==

Using scripting to extend Code::Blocks' functionality

* [[Wizard scripts|Creating a new project wizard]]

== Debugging C::B ==

When C::B crashed, it will generate a call-stack file "codeblocks.RPT", at the crash point, this is a text file, you can open it, if your C::B contains the debug information, it will have file and line information about each call. If it is a stripped version, but you have the debug version of C::B, you can try to run the [/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is a address2line UI interface works under Windows.

Developer documentation

2012-08-22T19:49:52Z

MortenMacFly:

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
{{Layout_box2|1=
'''Code repository''' 
* Web-interface by ViewVC: http://svn.berlios.de/viewcvs/codeblocks/trunk/ 
* Subversion URL: <nowiki>http://svn.berlios.de/svnroot/repos/codeblocks/trunk</nowiki>

'''Mirror''' (Read-only; refreshed every 30 minutes.)
* Subversion URL: <nowiki>svn://cb.biplab.in/codeblocks/trunk</nowiki> 
* Web-interface: http://cb.biplab.in/websvn/
* Git URL: git://cb.biplab.in/codeblocks.git
* Web-interface:http://cb.biplab.in/cgit/
}}

'''Articles for Code::Blocks developers.'''

* '''Documentation'''
:[https://www.codeblocks.org/manual.shtml User's manual] in various formats and languages.
:Also see http://developer.berlios.de/projects/codeblocks/ (under the downloads section).
:Checkout the SDK documentation at http://developer.berlios.de/project/showfiles.php?group_id=5358 as CHM file(s).

* Compile Code::Blocks from sources on '''[[Installing Code::Blocks from source on Windows|Windows]]''' and '''[[Installing Code::Blocks from source on Linux|Linux]]'''

* '''[[Compile Code::Blocks plugins based on a nightly]]]''' w/o the need to compile wxWidgets or the Code::Blocks core.

* '''[http://launchpad.net/products/codeblocks/ Translation]'''
:Code::Blocks uses Launchpad to coordinate translation efforts.

* '''[[Coding style]]'''
:The source code formatting style used in the Code::Blocks' source.

* '''[[Creating a custom lexer for Code::Blocks editor]]'''
:How to add support for new syntax lighting schemes.

* '''[[Creating a patch to submit to BerliOS (Patch Tracker)]]'''
:Creating a diff file and then submitting it to the patch tracker.

* '''[[Unicode Standards]]'''
:Information about unicode standards and how unicode is handled in Code::Blocks' source code.

* '''[[Various development tips]]'''
:List of various development tips for Code::Blocks.

* '''[[Scripting Code::Blocks]]'''
:Information about scripting Code::Blocks with [http://www.squirrel-lang.org/ Squirrel].

* '''[[A short overview about Code::Blocks architecture]]'''
:Information about the architecture of Code::Blocks.

* '''[[Code::Blocks SDK events]]'''
:Information about the Code::Blocks SDK events and how to work with them.

* '''[[File formats description]]'''
:Description of the format of each file Code::Blocks produces.

* '''[[Version control]]'''
:Tips and trick for working with our version control system.

== Plug-In development ==

* [[Creating a simple "Hello World" plugin]]
* [[Creating a Plug-in which modifies CB's Menus]]
* [[Creating a plugin that actually does something]]
* [[Linking the plugin to a Nightly Build]]
* [[Managing Plug-in Resources]]

* [[Research on doing a Plug-in for embedded help in CB]]

* [[wxSmith extensions]]
* [[Code::Completion Rewrite]] and [[Code Completion plugin]] and [[Code Completion Design]]

== Scripting ==

Using scripting to extend Code::Blocks' functionality

* [[Wizard scripts|Creating a new project wizard]]

== Debugging C::B ==

When C::B crashed, it will generate a call-stack file "codeblocks.RPT", at the crash point, this is a text file, you can open it, if your C::B contains the debug information, it will have file and line information about each call. If it is a stripped version, but you have the debug version of C::B, you can try to run the [/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is a address2line UI interface works under Windows.

File:1a.png

2012-08-06T05:06:00Z

MortenMacFly: uploaded a new version of "File:1a.png"

CodeBlocks Opener

FAQ-Compiling (errors)

2012-06-29T12:54:30Z

MortenMacFly: /* Q: My build fails with multiple undefined reference errors? */

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: How do I troubleshoot a compiler problem? ====

'''A:''' I would start by turning on full Compiler logging.

This is done by selecting the "Full command line" option Under menu "Settings" -> "Compiler and Debugger" -> Global compiler settings -> [the compiler you use] -> "Other Setting" tab, "Compiler logging".

This option will make Code::Blocks output the exact commands it uses to compile your code.

Things to remember:

* You should review all the commands and their options;
* If you have compiled your app before, do a ''re-''build (or ''clean'' before build) to see all compiling / linking steps;
* If you don't know what an option or a command does please read the documentation for the compiler/linker you're using;
* Look for missing commands;
* For every source file (<tt>.cpp</tt>; <tt>.c</tt>; <tt>.d</tt>; etc) in your project, you must have at least one command in the log. This command must produce an object file (file extension <tt>.o</tt> if using gcc/g++ and <tt>.obj</tt> if using Visual Studio);
* Every object file should be linked in the final executable, if not there are undefined symbols errors;
* Remember the file extension matters: <tt>*.c</tt> is compiled as C file, <tt>*.cpp</tt> is compiled as C++ file. [http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html Read more]

==== Q: My simple C++ program throws up lots of errors - what is going on? ====

If you have a C++ program like this:

#include <iostream>
int main() {
std::cout << "hello world\n";
}

and when you compile it you get errors like this:

fatal error: iostream: No such file or directory

then you have probably given your source file a .c extension. If you do that, the GCC compiler (and others) will probably attempt to compile the file as a C program, not as C++. You should always give your C++ source files the extension .cpp to make sure the compiler handles them correctly.

==== Q: I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ====

'''A:''' A little documentation problem ^^;. The "default compiler" is usually GCC, so when you imported it with "the default compiler", you told it to use GCC. To fix this situation, go to "Project", "Build Options" and select VC++ Toolkit as your compiler.

Another possibility is to put the Microsoft compiler as the default one. To do this, choose '''''Settings - Compiler''''', choose the Microsoft compiler in the '''''Selected Compiler''''' section (top of dialog box) and press the '''''Set as default''''' button.

From now onwards, for all new projects the Microsoft compiler will be taken by default.

==== Q: When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? ====

'''A:''' You need to add WXUSINGDLL in "Project->Build options->Compiler #defines" and rebuild your project (or create a new project and use the "Using wxWidgets DLL" project option which adds "-DWXUSINGDLL" to Project->Build options->Other options).
Other errors with the same resolution are:
'unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB)' or similar.
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.

==== Q: I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ====

'''A:''' Sorry, no fix for your problem...

Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which come with Visual C++ (VC) which isn't free, unfortunately.

Try buying a full-fledged VC++, or even better, download [http://www.mingw.org/ MinGW]

The libraries that can be obtained free of charge are:

Paths:
(VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
(PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib
(NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

C runtime libs:
LIBC.LIB Single-threaded, static link (VCT3, NSDK)
LIBCMT.LIB Multithreaded, static link (VCT3, NSDK)
MSVCRT.LIB Multithreaded, dynamic link (import library for MSVCR71.DLL) (NSDK)
LIBCD.LIB Single-threaded, static link (debug) (VCT3, NSDK)
LIBCMTD.LIB Multithreaded, static link (debug) (NSDK)
MSVCRTD.LIB Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)

C++ libs:
LIBCP.LIB Single-threaded, static link (VCT3, PSDK)
LIBCPMT.LIB Multithreaded, static link (VCT3)
MSVCPRT.LIB Multithreaded, dynamic link (import library for MSVCP71.dll) (none)
LIBCPD.LIB Single-threaded, static link (debug) (VCT3)
LIBCPMTD.LIB Multithreaded, static link (debug) (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (debug) (none)

Try setting the library linker directories to:
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
C:\Program Files\Microsoft Platform SDK\Lib
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib
in that order.

The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory. Not sure if these would work on 32-bit windows, however, they may if they are
meant to work in 32-bit compatibility mode on the 64-bit processors. Worth a try. Otherwise, you
can link statically to the C++ library instead of using MSVCP71.dll. If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed. Search google for "exports.sed" for detailed steps.

See also: [http://wiki.tcl.tk/2435 tclsh script to extract import .lib from (any?) DLL (MinGW)]

See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp

See also: http://sapdb.2scale.net/moin.cgi/MS_20C_2b_2b_20Toolkit

==== Q: I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll" ====

'''A:''' Make sure you didn't mix up the MSVC headers or libs with the MinGW ones.

==== Q: My build fails with multiple ''undefined reference'' errors? ====

''Example:''
undefined reference to `WSACleanup@8
undefined reference to `WSACleanup@0

'''A:''' Most of the time it is because the required library is not linked with your project. Go to ''Project->Build options...->Linker settings (tab)'' and add the required library or libraries.

If the error includes a line number, it is likely that this is a problem with your code. Track down down your function declarations and implementations. Ensure they all match up, are spelled correctly, and have the correct scope resolution.

''VERY'' often you can get help by just googling for the name of the undefined reference, for this example its "WSACleanup". Usually one of the first links is the SDK documentation, like [http://msdn.microsoft.com/en-us/library/windows/desktop/ms741549%28v=vs.85%29.aspx this from MSDN for WSACleanup]. You'll find there a lot useful information, including what libraries you need to link against, as for the exsample:
'''Requirements'''
* Minimum supported client: Windows 2000 Professional
* Minimum supported server: Windows 2000 Server
* Header: '''Winsock2.h'''
* Library: '''Ws2_32'''.lib
* DLL: '''Ws2_32.dll'''
The header file '''Winsock2.h''' you need to include in your sources. Most likely you have done that already because otherwise you would have gotten a compiler error unable to find the function declaration. The library you need to link against, you can remove any prefix like "lib" and the file extension like ".lib", ".a" or ".so" - so just type "'''Ws2_32'''" in the linker options. Also make sure you have added the path to that library in the linker include path's options, otherwise the linker will complain that it cannot find that library you want to link against. You also know, that you should distribute '''Ws2_32.dll''' for the runtime version of you app, luckily this one usually ships with Windows anyways, so no need to do something here.

==== Q: My build fails in the compile/link/run step with a ''Permission denied'' error? ====

'''A:''' There are several possible causes for this:

# The output directory does not have read/write access.
#* Either change control settings on the output directory, or move the project to different location.
# A previous instance of the executable failed to terminate properly.
#* Open your system's equivalent of Process/Task Manager, search the list for the name of the executable Code::Blocks is trying to output, and terminate it.
#* Logging off or rebooting will achieve the same effect.
# The executable is open.
#* If the executable is open in a hex-editor or actively being run, close it.
# Security software is interfering.
#* The target file is locked while an antivirus programming is scanning it; either wait a few seconds for the antivirus scan to finish, set an exception in the antivirus settings, or (temporarily) disable the antivirus program.
#* Firewalls with very strict settings sometimes block execution; try reducing the firewall's settings or adding an exception.
#* Switching security software may have left traces behind that are interfering; hunt down the remnants of the old antivirus/firewall software and remove them.
# The file/library cannot be found.
#* Double check all of the compiler and linker [[FAQ-Compiling (general)#Q: I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?|search directories]] (including any [[Global compiler variables|variables]] they may be using) are properly setup.
# Code::Blocks was improperly installed.
#* Mixing binaries from a stable release and a nightly build (or even two different nightly builds) is highly likely to cause a slew of problems; [[Installing Code::Blocks|reinstall Code::Blocks]] in an empty directory.
# Multiple installed compilers are interfering with each other.
#* If they are not required to keep, completely remove all but the most used compiler.
#* If several compilers are required, ensure that '''none''' of them are in the ''system'' path (this is so that Code::Blocks will be able to manage all paths).
#* Also, do not place any compilers in their default installation path (for example <tt>C:\MinGW</tt>), as some compilers are hard-coded to look for headers in a default path ''before'' searching their own respective directories.

See also: [/index.php/topic,15047.0.html Permission denied forums discussion]

==== Q: My build fails to link due to ''multiple definition of xyz'' errors? ====

'''A:''' GCC 4.6.1 mingw target (Windows) is known to occasionally (and erroneously) report this if link-time optimization (<tt>-flto</tt>) is used.

First, of course, check that no token has been defined multiple times. If the source code is clean, and yet the errors persist, adding linker switch (''Project->Build options...->Linker settings (tab)'')
-Wl,--allow-multiple-definition
will enable the code to link.

See also: [http://sourceware.org/bugzilla/show_bug.cgi?id=12762 Bug 12762]

----

Return to '''[[FAQ]]'''.

FAQ-Compiling (errors)

2012-06-29T12:52:47Z

MortenMacFly: /* Q: My build fails with multiple undefined reference errors? */

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: How do I troubleshoot a compiler problem? ====

'''A:''' I would start by turning on full Compiler logging.

This is done by selecting the "Full command line" option Under menu "Settings" -> "Compiler and Debugger" -> Global compiler settings -> [the compiler you use] -> "Other Setting" tab, "Compiler logging".

This option will make Code::Blocks output the exact commands it uses to compile your code.

Things to remember:

* You should review all the commands and their options;
* If you have compiled your app before, do a ''re-''build (or ''clean'' before build) to see all compiling / linking steps;
* If you don't know what an option or a command does please read the documentation for the compiler/linker you're using;
* Look for missing commands;
* For every source file (<tt>.cpp</tt>; <tt>.c</tt>; <tt>.d</tt>; etc) in your project, you must have at least one command in the log. This command must produce an object file (file extension <tt>.o</tt> if using gcc/g++ and <tt>.obj</tt> if using Visual Studio);
* Every object file should be linked in the final executable, if not there are undefined symbols errors;
* Remember the file extension matters: <tt>*.c</tt> is compiled as C file, <tt>*.cpp</tt> is compiled as C++ file. [http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html Read more]

==== Q: My simple C++ program throws up lots of errors - what is going on? ====

If you have a C++ program like this:

#include <iostream>
int main() {
std::cout << "hello world\n";
}

and when you compile it you get errors like this:

fatal error: iostream: No such file or directory

then you have probably given your source file a .c extension. If you do that, the GCC compiler (and others) will probably attempt to compile the file as a C program, not as C++. You should always give your C++ source files the extension .cpp to make sure the compiler handles them correctly.

==== Q: I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ====

'''A:''' A little documentation problem ^^;. The "default compiler" is usually GCC, so when you imported it with "the default compiler", you told it to use GCC. To fix this situation, go to "Project", "Build Options" and select VC++ Toolkit as your compiler.

Another possibility is to put the Microsoft compiler as the default one. To do this, choose '''''Settings - Compiler''''', choose the Microsoft compiler in the '''''Selected Compiler''''' section (top of dialog box) and press the '''''Set as default''''' button.

From now onwards, for all new projects the Microsoft compiler will be taken by default.

==== Q: When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? ====

'''A:''' You need to add WXUSINGDLL in "Project->Build options->Compiler #defines" and rebuild your project (or create a new project and use the "Using wxWidgets DLL" project option which adds "-DWXUSINGDLL" to Project->Build options->Other options).
Other errors with the same resolution are:
'unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB)' or similar.
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.

==== Q: I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ====

'''A:''' Sorry, no fix for your problem...

Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which come with Visual C++ (VC) which isn't free, unfortunately.

Try buying a full-fledged VC++, or even better, download [http://www.mingw.org/ MinGW]

The libraries that can be obtained free of charge are:

Paths:
(VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
(PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib
(NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

C runtime libs:
LIBC.LIB Single-threaded, static link (VCT3, NSDK)
LIBCMT.LIB Multithreaded, static link (VCT3, NSDK)
MSVCRT.LIB Multithreaded, dynamic link (import library for MSVCR71.DLL) (NSDK)
LIBCD.LIB Single-threaded, static link (debug) (VCT3, NSDK)
LIBCMTD.LIB Multithreaded, static link (debug) (NSDK)
MSVCRTD.LIB Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)

C++ libs:
LIBCP.LIB Single-threaded, static link (VCT3, PSDK)
LIBCPMT.LIB Multithreaded, static link (VCT3)
MSVCPRT.LIB Multithreaded, dynamic link (import library for MSVCP71.dll) (none)
LIBCPD.LIB Single-threaded, static link (debug) (VCT3)
LIBCPMTD.LIB Multithreaded, static link (debug) (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (debug) (none)

Try setting the library linker directories to:
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
C:\Program Files\Microsoft Platform SDK\Lib
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib
in that order.

The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory. Not sure if these would work on 32-bit windows, however, they may if they are
meant to work in 32-bit compatibility mode on the 64-bit processors. Worth a try. Otherwise, you
can link statically to the C++ library instead of using MSVCP71.dll. If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed. Search google for "exports.sed" for detailed steps.

See also: [http://wiki.tcl.tk/2435 tclsh script to extract import .lib from (any?) DLL (MinGW)]

See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp

See also: http://sapdb.2scale.net/moin.cgi/MS_20C_2b_2b_20Toolkit

==== Q: I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll" ====

'''A:''' Make sure you didn't mix up the MSVC headers or libs with the MinGW ones.

==== Q: My build fails with multiple ''undefined reference'' errors? ====

''Example:''
undefined reference to `WSACleanup@8
undefined reference to `WSACleanup@0

'''A:''' Most of the time it is because the required library is not linked with your project. Go to ''Project->Build options...->Linker settings (tab)'' and add the required library or libraries.

If the error includes a line number, it is likely that this is a problem with your code. Track down down your function declarations and implementations. Ensure they all match up, are spelled correctly, and have the correct scope resolution.

''VERY'' often you can get help by just googling for the name of the undefined reference, for this example its "WSACleanup". Usually one of the first links is the SDK documentation, like [http://msdn.microsoft.com/en-us/library/windows/desktop/ms741549%28v=vs.85%29.aspx this from MSDN for WSACleanup]. You'll find there a lot useful information, including what libraries you need to link against, as for the exsample:
'''Requirements'''
* Minimum supported client: Windows 2000 Professional
* Minimum supported server: Windows 2000 Server
* Header: '''Winsock2.h'''
* Library: '''Ws2_32'''.lib
* DLL: '''Ws2_32.dll'''
The header file '''Winsock2.h''' you need to include in your sources. Most likely you have done that already because otherwise you would have gotten a compiler error unable to find the function declaration. The library you need to link against, you can remove the prefix and type "'''Ws2_32'''" in the linker options (make sure you have added the path to that library in the linker include path's options). You also know, that you should distribute '''Ws2_32.dll''' for the runtime version of you app, luckily this one usually ships with Windows anyways, so no need to do something here.

==== Q: My build fails in the compile/link/run step with a ''Permission denied'' error? ====

'''A:''' There are several possible causes for this:

# The output directory does not have read/write access.
#* Either change control settings on the output directory, or move the project to different location.
# A previous instance of the executable failed to terminate properly.
#* Open your system's equivalent of Process/Task Manager, search the list for the name of the executable Code::Blocks is trying to output, and terminate it.
#* Logging off or rebooting will achieve the same effect.
# The executable is open.
#* If the executable is open in a hex-editor or actively being run, close it.
# Security software is interfering.
#* The target file is locked while an antivirus programming is scanning it; either wait a few seconds for the antivirus scan to finish, set an exception in the antivirus settings, or (temporarily) disable the antivirus program.
#* Firewalls with very strict settings sometimes block execution; try reducing the firewall's settings or adding an exception.
#* Switching security software may have left traces behind that are interfering; hunt down the remnants of the old antivirus/firewall software and remove them.
# The file/library cannot be found.
#* Double check all of the compiler and linker [[FAQ-Compiling (general)#Q: I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?|search directories]] (including any [[Global compiler variables|variables]] they may be using) are properly setup.
# Code::Blocks was improperly installed.
#* Mixing binaries from a stable release and a nightly build (or even two different nightly builds) is highly likely to cause a slew of problems; [[Installing Code::Blocks|reinstall Code::Blocks]] in an empty directory.
# Multiple installed compilers are interfering with each other.
#* If they are not required to keep, completely remove all but the most used compiler.
#* If several compilers are required, ensure that '''none''' of them are in the ''system'' path (this is so that Code::Blocks will be able to manage all paths).
#* Also, do not place any compilers in their default installation path (for example <tt>C:\MinGW</tt>), as some compilers are hard-coded to look for headers in a default path ''before'' searching their own respective directories.

See also: [/index.php/topic,15047.0.html Permission denied forums discussion]

==== Q: My build fails to link due to ''multiple definition of xyz'' errors? ====

'''A:''' GCC 4.6.1 mingw target (Windows) is known to occasionally (and erroneously) report this if link-time optimization (<tt>-flto</tt>) is used.

First, of course, check that no token has been defined multiple times. If the source code is clean, and yet the errors persist, adding linker switch (''Project->Build options...->Linker settings (tab)'')
-Wl,--allow-multiple-definition
will enable the code to link.

See also: [http://sourceware.org/bugzilla/show_bug.cgi?id=12762 Bug 12762]

----

Return to '''[[FAQ]]'''.

FAQ-Compiling (errors)

2012-06-29T12:51:04Z

MortenMacFly: /* Q: My build fails with multiple undefined reference errors? */

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: How do I troubleshoot a compiler problem? ====

'''A:''' I would start by turning on full Compiler logging.

This is done by selecting the "Full command line" option Under menu "Settings" -> "Compiler and Debugger" -> Global compiler settings -> [the compiler you use] -> "Other Setting" tab, "Compiler logging".

This option will make Code::Blocks output the exact commands it uses to compile your code.

Things to remember:

* You should review all the commands and their options;
* If you have compiled your app before, do a ''re-''build (or ''clean'' before build) to see all compiling / linking steps;
* If you don't know what an option or a command does please read the documentation for the compiler/linker you're using;
* Look for missing commands;
* For every source file (<tt>.cpp</tt>; <tt>.c</tt>; <tt>.d</tt>; etc) in your project, you must have at least one command in the log. This command must produce an object file (file extension <tt>.o</tt> if using gcc/g++ and <tt>.obj</tt> if using Visual Studio);
* Every object file should be linked in the final executable, if not there are undefined symbols errors;
* Remember the file extension matters: <tt>*.c</tt> is compiled as C file, <tt>*.cpp</tt> is compiled as C++ file. [http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html Read more]

==== Q: My simple C++ program throws up lots of errors - what is going on? ====

If you have a C++ program like this:

#include <iostream>
int main() {
std::cout << "hello world\n";
}

and when you compile it you get errors like this:

fatal error: iostream: No such file or directory

then you have probably given your source file a .c extension. If you do that, the GCC compiler (and others) will probably attempt to compile the file as a C program, not as C++. You should always give your C++ source files the extension .cpp to make sure the compiler handles them correctly.

==== Q: I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ====

'''A:''' A little documentation problem ^^;. The "default compiler" is usually GCC, so when you imported it with "the default compiler", you told it to use GCC. To fix this situation, go to "Project", "Build Options" and select VC++ Toolkit as your compiler.

Another possibility is to put the Microsoft compiler as the default one. To do this, choose '''''Settings - Compiler''''', choose the Microsoft compiler in the '''''Selected Compiler''''' section (top of dialog box) and press the '''''Set as default''''' button.

From now onwards, for all new projects the Microsoft compiler will be taken by default.

==== Q: When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? ====

'''A:''' You need to add WXUSINGDLL in "Project->Build options->Compiler #defines" and rebuild your project (or create a new project and use the "Using wxWidgets DLL" project option which adds "-DWXUSINGDLL" to Project->Build options->Other options).
Other errors with the same resolution are:
'unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB)' or similar.
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.

==== Q: I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ====

'''A:''' Sorry, no fix for your problem...

Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which come with Visual C++ (VC) which isn't free, unfortunately.

Try buying a full-fledged VC++, or even better, download [http://www.mingw.org/ MinGW]

The libraries that can be obtained free of charge are:

Paths:
(VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
(PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib
(NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

C runtime libs:
LIBC.LIB Single-threaded, static link (VCT3, NSDK)
LIBCMT.LIB Multithreaded, static link (VCT3, NSDK)
MSVCRT.LIB Multithreaded, dynamic link (import library for MSVCR71.DLL) (NSDK)
LIBCD.LIB Single-threaded, static link (debug) (VCT3, NSDK)
LIBCMTD.LIB Multithreaded, static link (debug) (NSDK)
MSVCRTD.LIB Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)

C++ libs:
LIBCP.LIB Single-threaded, static link (VCT3, PSDK)
LIBCPMT.LIB Multithreaded, static link (VCT3)
MSVCPRT.LIB Multithreaded, dynamic link (import library for MSVCP71.dll) (none)
LIBCPD.LIB Single-threaded, static link (debug) (VCT3)
LIBCPMTD.LIB Multithreaded, static link (debug) (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (debug) (none)

Try setting the library linker directories to:
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
C:\Program Files\Microsoft Platform SDK\Lib
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib
in that order.

The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory. Not sure if these would work on 32-bit windows, however, they may if they are
meant to work in 32-bit compatibility mode on the 64-bit processors. Worth a try. Otherwise, you
can link statically to the C++ library instead of using MSVCP71.dll. If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed. Search google for "exports.sed" for detailed steps.

See also: [http://wiki.tcl.tk/2435 tclsh script to extract import .lib from (any?) DLL (MinGW)]

See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp

See also: http://sapdb.2scale.net/moin.cgi/MS_20C_2b_2b_20Toolkit

==== Q: I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll" ====

'''A:''' Make sure you didn't mix up the MSVC headers or libs with the MinGW ones.

==== Q: My build fails with multiple ''undefined reference'' errors? ====

''Example:''
undefined reference to `WSACleanup@8
undefined reference to `WSACleanup@0

'''A:''' Most of the time it is because the required library is not linked with your project. Go to ''Project->Build options...->Linker settings (tab)'' and add the required library or libraries.

If the error includes a line number, it is likely that this is a problem with your code. Track down down your function declarations and implementations. Ensure they all match up, are spelled correctly, and have the correct scope resolution.

''VERY'' often you can get help by just googling for the name of the undefined reference, for this example its "WSACleanup". Usually one of the first links is the SDK documentation, like [http://msdn.microsoft.com/en-us/library/windows/desktop/ms741549%28v=vs.85%29.aspx this from MSDN for WSACleanup]. You'll find there a lot useful information, including what libraries you need to link against, as for the exsample:
'''Requirements'''
* Minimum supported client: Windows 2000 Professional
* Minimum supported server: Windows 2000 Server
* Header: '''Winsock2.h'''
* Library: '''Ws2_32'''.lib
* DLL: '''Ws2_32.dll'''
The header file '''Winsock2.h''' you need to include (most likely you have already in your app). The library you need to link against, you can remove the prefix and type "'''Ws2_32'''" in the linker options (make sure you have added the path to that library in the linker include path's options). You also know, that you should distribute '''Ws2_32.dll''' for the runtime version of you app, luckily this one usually ships with Windows anyways, so no need to do something here.

==== Q: My build fails in the compile/link/run step with a ''Permission denied'' error? ====

'''A:''' There are several possible causes for this:

# The output directory does not have read/write access.
#* Either change control settings on the output directory, or move the project to different location.
# A previous instance of the executable failed to terminate properly.
#* Open your system's equivalent of Process/Task Manager, search the list for the name of the executable Code::Blocks is trying to output, and terminate it.
#* Logging off or rebooting will achieve the same effect.
# The executable is open.
#* If the executable is open in a hex-editor or actively being run, close it.
# Security software is interfering.
#* The target file is locked while an antivirus programming is scanning it; either wait a few seconds for the antivirus scan to finish, set an exception in the antivirus settings, or (temporarily) disable the antivirus program.
#* Firewalls with very strict settings sometimes block execution; try reducing the firewall's settings or adding an exception.
#* Switching security software may have left traces behind that are interfering; hunt down the remnants of the old antivirus/firewall software and remove them.
# The file/library cannot be found.
#* Double check all of the compiler and linker [[FAQ-Compiling (general)#Q: I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?|search directories]] (including any [[Global compiler variables|variables]] they may be using) are properly setup.
# Code::Blocks was improperly installed.
#* Mixing binaries from a stable release and a nightly build (or even two different nightly builds) is highly likely to cause a slew of problems; [[Installing Code::Blocks|reinstall Code::Blocks]] in an empty directory.
# Multiple installed compilers are interfering with each other.
#* If they are not required to keep, completely remove all but the most used compiler.
#* If several compilers are required, ensure that '''none''' of them are in the ''system'' path (this is so that Code::Blocks will be able to manage all paths).
#* Also, do not place any compilers in their default installation path (for example <tt>C:\MinGW</tt>), as some compilers are hard-coded to look for headers in a default path ''before'' searching their own respective directories.

See also: [/index.php/topic,15047.0.html Permission denied forums discussion]

==== Q: My build fails to link due to ''multiple definition of xyz'' errors? ====

'''A:''' GCC 4.6.1 mingw target (Windows) is known to occasionally (and erroneously) report this if link-time optimization (<tt>-flto</tt>) is used.

First, of course, check that no token has been defined multiple times. If the source code is clean, and yet the errors persist, adding linker switch (''Project->Build options...->Linker settings (tab)'')
-Wl,--allow-multiple-definition
will enable the code to link.

See also: [http://sourceware.org/bugzilla/show_bug.cgi?id=12762 Bug 12762]

----

Return to '''[[FAQ]]'''.

FAQ-Compiling (errors)

2012-06-29T12:50:23Z

MortenMacFly: /* Q: My build fails with multiple undefined reference errors? */

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: How do I troubleshoot a compiler problem? ====

'''A:''' I would start by turning on full Compiler logging.

This is done by selecting the "Full command line" option Under menu "Settings" -> "Compiler and Debugger" -> Global compiler settings -> [the compiler you use] -> "Other Setting" tab, "Compiler logging".

This option will make Code::Blocks output the exact commands it uses to compile your code.

Things to remember:

* You should review all the commands and their options;
* If you have compiled your app before, do a ''re-''build (or ''clean'' before build) to see all compiling / linking steps;
* If you don't know what an option or a command does please read the documentation for the compiler/linker you're using;
* Look for missing commands;
* For every source file (<tt>.cpp</tt>; <tt>.c</tt>; <tt>.d</tt>; etc) in your project, you must have at least one command in the log. This command must produce an object file (file extension <tt>.o</tt> if using gcc/g++ and <tt>.obj</tt> if using Visual Studio);
* Every object file should be linked in the final executable, if not there are undefined symbols errors;
* Remember the file extension matters: <tt>*.c</tt> is compiled as C file, <tt>*.cpp</tt> is compiled as C++ file. [http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html Read more]

==== Q: My simple C++ program throws up lots of errors - what is going on? ====

If you have a C++ program like this:

#include <iostream>
int main() {
std::cout << "hello world\n";
}

and when you compile it you get errors like this:

fatal error: iostream: No such file or directory

then you have probably given your source file a .c extension. If you do that, the GCC compiler (and others) will probably attempt to compile the file as a C program, not as C++. You should always give your C++ source files the extension .cpp to make sure the compiler handles them correctly.

==== Q: I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ====

'''A:''' A little documentation problem ^^;. The "default compiler" is usually GCC, so when you imported it with "the default compiler", you told it to use GCC. To fix this situation, go to "Project", "Build Options" and select VC++ Toolkit as your compiler.

Another possibility is to put the Microsoft compiler as the default one. To do this, choose '''''Settings - Compiler''''', choose the Microsoft compiler in the '''''Selected Compiler''''' section (top of dialog box) and press the '''''Set as default''''' button.

From now onwards, for all new projects the Microsoft compiler will be taken by default.

==== Q: When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? ====

'''A:''' You need to add WXUSINGDLL in "Project->Build options->Compiler #defines" and rebuild your project (or create a new project and use the "Using wxWidgets DLL" project option which adds "-DWXUSINGDLL" to Project->Build options->Other options).
Other errors with the same resolution are:
'unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB)' or similar.
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.

==== Q: I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ====

'''A:''' Sorry, no fix for your problem...

Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which come with Visual C++ (VC) which isn't free, unfortunately.

Try buying a full-fledged VC++, or even better, download [http://www.mingw.org/ MinGW]

The libraries that can be obtained free of charge are:

Paths:
(VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
(PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib
(NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

C runtime libs:
LIBC.LIB Single-threaded, static link (VCT3, NSDK)
LIBCMT.LIB Multithreaded, static link (VCT3, NSDK)
MSVCRT.LIB Multithreaded, dynamic link (import library for MSVCR71.DLL) (NSDK)
LIBCD.LIB Single-threaded, static link (debug) (VCT3, NSDK)
LIBCMTD.LIB Multithreaded, static link (debug) (NSDK)
MSVCRTD.LIB Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)

C++ libs:
LIBCP.LIB Single-threaded, static link (VCT3, PSDK)
LIBCPMT.LIB Multithreaded, static link (VCT3)
MSVCPRT.LIB Multithreaded, dynamic link (import library for MSVCP71.dll) (none)
LIBCPD.LIB Single-threaded, static link (debug) (VCT3)
LIBCPMTD.LIB Multithreaded, static link (debug) (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (debug) (none)

Try setting the library linker directories to:
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
C:\Program Files\Microsoft Platform SDK\Lib
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib
in that order.

The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory. Not sure if these would work on 32-bit windows, however, they may if they are
meant to work in 32-bit compatibility mode on the 64-bit processors. Worth a try. Otherwise, you
can link statically to the C++ library instead of using MSVCP71.dll. If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed. Search google for "exports.sed" for detailed steps.

See also: [http://wiki.tcl.tk/2435 tclsh script to extract import .lib from (any?) DLL (MinGW)]

See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp

See also: http://sapdb.2scale.net/moin.cgi/MS_20C_2b_2b_20Toolkit

==== Q: I get this error when compiling: Symbol "isascii" was not found in "codeblocks.dll" ====

'''A:''' Make sure you didn't mix up the MSVC headers or libs with the MinGW ones.

==== Q: My build fails with multiple ''undefined reference'' errors? ====

''Example:''
undefined reference to `WSACleanup@8
undefined reference to `WSACleanup@0

'''A:''' Most of the time it is because the required library is not linked with your project. Go to ''Project->Build options...->Linker settings (tab)'' and add the required library or libraries.

If the error includes a line number, it is likely that this is a problem with your code. Track down down your function declarations and implementations. Ensure they all match up, are spelled correctly, and have the correct scope resolution.

''VERY'' often you can get help by just googling for the name of the undefined reference, for his example "WSACleanup". Usually one of the first links is the SDK documentation, like [http://msdn.microsoft.com/en-us/library/windows/desktop/ms741549%28v=vs.85%29.aspx this from MSDN for WSACleanup]. You'll find there a lot useful information, including what libraries you need to link against, as for the exsample:
'''Requirements'''
* Minimum supported client: Windows 2000 Professional
* Minimum supported server: Windows 2000 Server
* Header: '''Winsock2.h'''
* Library: '''Ws2_32'''.lib
* DLL: '''Ws2_32.dll'''
The header file '''Winsock2.h''' you need to include (most likely you have already in your app). The library you need to link against, you can remove the prefix and type "'''Ws2_32'''" in the linker options (make sure you have added the path to that library in the linker include path's options). You also know, that you should distribute '''Ws2_32.dll''' for the runtime version of you app, luckily this one usually ships with Windows anyways, so no need to do something here.

==== Q: My build fails in the compile/link/run step with a ''Permission denied'' error? ====

'''A:''' There are several possible causes for this:

# The output directory does not have read/write access.
#* Either change control settings on the output directory, or move the project to different location.
# A previous instance of the executable failed to terminate properly.
#* Open your system's equivalent of Process/Task Manager, search the list for the name of the executable Code::Blocks is trying to output, and terminate it.
#* Logging off or rebooting will achieve the same effect.
# The executable is open.
#* If the executable is open in a hex-editor or actively being run, close it.
# Security software is interfering.
#* The target file is locked while an antivirus programming is scanning it; either wait a few seconds for the antivirus scan to finish, set an exception in the antivirus settings, or (temporarily) disable the antivirus program.
#* Firewalls with very strict settings sometimes block execution; try reducing the firewall's settings or adding an exception.
#* Switching security software may have left traces behind that are interfering; hunt down the remnants of the old antivirus/firewall software and remove them.
# The file/library cannot be found.
#* Double check all of the compiler and linker [[FAQ-Compiling (general)#Q: I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?|search directories]] (including any [[Global compiler variables|variables]] they may be using) are properly setup.
# Code::Blocks was improperly installed.
#* Mixing binaries from a stable release and a nightly build (or even two different nightly builds) is highly likely to cause a slew of problems; [[Installing Code::Blocks|reinstall Code::Blocks]] in an empty directory.
# Multiple installed compilers are interfering with each other.
#* If they are not required to keep, completely remove all but the most used compiler.
#* If several compilers are required, ensure that '''none''' of them are in the ''system'' path (this is so that Code::Blocks will be able to manage all paths).
#* Also, do not place any compilers in their default installation path (for example <tt>C:\MinGW</tt>), as some compilers are hard-coded to look for headers in a default path ''before'' searching their own respective directories.

See also: [/index.php/topic,15047.0.html Permission denied forums discussion]

==== Q: My build fails to link due to ''multiple definition of xyz'' errors? ====

'''A:''' GCC 4.6.1 mingw target (Windows) is known to occasionally (and erroneously) report this if link-time optimization (<tt>-flto</tt>) is used.

First, of course, check that no token has been defined multiple times. If the source code is clean, and yet the errors persist, adding linker switch (''Project->Build options...->Linker settings (tab)'')
-Wl,--allow-multiple-definition
will enable the code to link.

See also: [http://sourceware.org/bugzilla/show_bug.cgi?id=12762 Bug 12762]

----

Return to '''[[FAQ]]'''.

Installing Code::Blocks from source on Windows

2012-06-13T10:14:47Z

MortenMacFly: /* Compile wxWidgets in ANSI mode */

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]
== Prerequisites ==

=== Note for RC2 users ===

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.
To build Code::Blocks, you need a post-RC2 build, such as ''8.02'' or any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].

=== MinGW compiler ===

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]] or [http://www.tdragon.net/recentgcc/ TDM-MinGW package].

'''Do not''' use the barebones MinGW with GCC 4.5.1 as you'll run (with this specific version) into [http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43601 a linker bug] (which happened to me on Vista SP1 32-bit on 2011-02-28); the solution is to use the TDM-GCC 4.5.1 package, or later.

=== wxWidgets ===

[http://www.wxwidgets.org/ wxWidgets.org]

Code::Blocks uses
* since 02 April 2011 wxWidgets 2.8.12 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

* since 28 March 2009 wxWidgets 2.8.10 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.10.zip wxMSW-2.8.10.zip]

* since 18 October 2008 wxWidgets 2.8.9 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.9.zip wxMSW-2.8.9.zip]

* since 19 July 2008 wxWidgets 2.8.8 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.8.zip wxMSW-2.8.8.zip]

* since 28 November 2007 wxWidgets 2.8.7 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.7.zip wxMSW-2.8.7.zip]

* since November 2007 wxWidgets 2.8.6 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.6.zip wxMSW-2.8.6.zip]

* since May 2007 wxWidgets 2.8.4 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.4.zip wxMSW-2.8.4.zip]

For latest infos check forum: [/index.php?topic=3299.0 Important changes to the nightly builds]

You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').

=== SVN client ===

In order to check out the Code::Blocks sources you will need a SVN client.
For convenience, it is recommended that you install [http://tortoisesvn.net/downloads 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 command-line client] equally well.

It is generally a good idea to install the command-line 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 preferable to the manual parsing of the entries file that is used as fall-back.

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).

The built-in fall-back mechanism in <tt>autorevision</tt> has been updated to the new 1.4 format and will no longer work with the old format. 
Therefore, if you use a Subversion client from the 1.0-1.3 line, you ''must'' put the command line tool into <tt>PATH</tt> for a successful build. 
If you use Subversion 1.4, then it is good practice nevertheless, but you can do without, too.

=== svn.exe ===
If you want to show the SVN number in your code::blocks dialog box.

[[Image:Svn number.png|300*300px]]

You should also let svn.exe exist in the PATH of your windows system.
A command line SVN package can be download here [http://www.open.collab.net/downloads/subversion/ CollabNet Subversion Command-Line Client v1.6 (for Windows)].

=== zip.exe ===

You'll also need a working 'zip' program.
If you have the version listed on our [[MinGW installation#Other developer tools|tools page]], you'll be fine.

The zip program coming with cygwin will ''not'' work properly. You do ''not'' need WinZip.

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).

The easiest way is to put zip.exe into <tt>bin</tt> inside your MinGW installation directory (that folder is normally in the path).

=== Code::Blocks sources ===

You will also (obviously) need the Code::Blocks sources.

Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".

[[Image:Win svn checkout.png]]

In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.

Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.berlios.de/codeblocks/trunk</nowiki>

== Unicode Build ==

=== Compile wxWidgets in Unicode mode ===

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:

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

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.

If you are using a recent version of MinGW you may find that the object files are too large and that the linker runs out of memory. To fix this problem you need to edit config.gcc so that inline functions are not exported, by modifying the CFLAGS and CXXFLAGS lines to:

CFLAGS ?= -fno-keep-inline-dllexport

CXXFLAGS ?= -fno-keep-inline-dllexport

''remark: If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well.''
''Use the same commands as for the release build, but replace "release" by "debug".''

'''Optional:'''

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.

=== Compile Code::Blocks ===
Now, before this step, you have prepared all the stuff to build code::blocks. It's very interesting that we use code::blocks to build code::blocks binaries.

==== Open project====
Open the project file '''CodeBlocks.cbp'''. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.

[[Image:Global_variable.png]]

[[Image:Global_variable2.png]]

====Compile project====
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.

[[Image:Win build button.png]]

[[Image:Win build target.png]]

[[Image:Win build finish.png]]

====Copy wxWidgets support DLL====
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_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).

[[Image:Win output folder.png]]

[[Image:Win copy dll.png]]

====Runing script file====
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.

[[Image:Win run bat.png]]

The stripped ("production") executable is found in <tt>output</tt> folder 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. 
Congratulations, you own a freshly built version of Code::Blocks!

[[Image:Win final folder.png]]

====Note for future updates====
Go to the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect). 
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>.

=== Install Code::Blocks ===

Copy the folder output to where you want Code::Blocks to reside.

=== Compile contributed (or your own) plugins ===

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). 

[[Image:Contribute plugin.png]]

When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. This is the path that contains the sdk folder normally this is codeblocks\src. 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.

Don't forget to run update.bat again after building the contrib plugins.

== ANSI Build ==

<div style="background-color: #f7d9d9; border: 1px solid #000">
<div style="margin: 5px;">

==== DEPRECATION WARNING: ====
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. 
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''

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.

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.

</div>
</div>

==== Compile wxWidgets in ANSI mode ====

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

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

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.

'''Optional:'''

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.

==== Compile Code::Blocks ====

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.

'''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:
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).

Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.

After the compilation has finished, copy wxmsw28u_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 [[wikipedia:DLL Hell|dll hell]]).
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.
The location of executable is src\output in C::B tree. From here you'll not need the nightly build anymore.

One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).

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 !

==== Install Code::Blocks ====

Copy the folder output to where you want Code::Blocks to reside.

==== Compile contributed (or your own) plugins ====

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.

Note that the Nassi Shneiderman plugin (part of the contrib plugins) has a dependency on [http://www.boost.org boost] which is needed to compile this plugin. Boost does not need to be compiled therefore.

Installing Code::Blocks from source on Windows

2012-06-13T10:14:23Z

MortenMacFly: /* Compile wxWidgets in Unicode mode */

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]
== Prerequisites ==

=== Note for RC2 users ===

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.
To build Code::Blocks, you need a post-RC2 build, such as ''8.02'' or any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].

=== MinGW compiler ===

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]] or [http://www.tdragon.net/recentgcc/ TDM-MinGW package].

'''Do not''' use the barebones MinGW with GCC 4.5.1 as you'll run (with this specific version) into [http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43601 a linker bug] (which happened to me on Vista SP1 32-bit on 2011-02-28); the solution is to use the TDM-GCC 4.5.1 package, or later.

=== wxWidgets ===

[http://www.wxwidgets.org/ wxWidgets.org]

Code::Blocks uses
* since 02 April 2011 wxWidgets 2.8.12 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

* since 28 March 2009 wxWidgets 2.8.10 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.10.zip wxMSW-2.8.10.zip]

* since 18 October 2008 wxWidgets 2.8.9 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.9.zip wxMSW-2.8.9.zip]

* since 19 July 2008 wxWidgets 2.8.8 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.8.zip wxMSW-2.8.8.zip]

* since 28 November 2007 wxWidgets 2.8.7 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.7.zip wxMSW-2.8.7.zip]

* since November 2007 wxWidgets 2.8.6 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.6.zip wxMSW-2.8.6.zip]

* since May 2007 wxWidgets 2.8.4 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.4.zip wxMSW-2.8.4.zip]

For latest infos check forum: [/index.php?topic=3299.0 Important changes to the nightly builds]

You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').

=== SVN client ===

In order to check out the Code::Blocks sources you will need a SVN client.
For convenience, it is recommended that you install [http://tortoisesvn.net/downloads 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 command-line client] equally well.

It is generally a good idea to install the command-line 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 preferable to the manual parsing of the entries file that is used as fall-back.

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).

The built-in fall-back mechanism in <tt>autorevision</tt> has been updated to the new 1.4 format and will no longer work with the old format. 
Therefore, if you use a Subversion client from the 1.0-1.3 line, you ''must'' put the command line tool into <tt>PATH</tt> for a successful build. 
If you use Subversion 1.4, then it is good practice nevertheless, but you can do without, too.

=== svn.exe ===
If you want to show the SVN number in your code::blocks dialog box.

[[Image:Svn number.png|300*300px]]

You should also let svn.exe exist in the PATH of your windows system.
A command line SVN package can be download here [http://www.open.collab.net/downloads/subversion/ CollabNet Subversion Command-Line Client v1.6 (for Windows)].

=== zip.exe ===

You'll also need a working 'zip' program.
If you have the version listed on our [[MinGW installation#Other developer tools|tools page]], you'll be fine.

The zip program coming with cygwin will ''not'' work properly. You do ''not'' need WinZip.

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).

The easiest way is to put zip.exe into <tt>bin</tt> inside your MinGW installation directory (that folder is normally in the path).

=== Code::Blocks sources ===

You will also (obviously) need the Code::Blocks sources.

Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".

[[Image:Win svn checkout.png]]

In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.

Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.berlios.de/codeblocks/trunk</nowiki>

== Unicode Build ==

=== Compile wxWidgets in Unicode mode ===

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:

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

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.

If you are using a recent version of MinGW you may find that the object files are too large and that the linker runs out of memory. To fix this problem you need to edit config.gcc so that inline functions are not exported, by modifying the CFLAGS and CXXFLAGS lines to:

CFLAGS ?= -fno-keep-inline-dllexport

CXXFLAGS ?= -fno-keep-inline-dllexport

''remark: If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well.''
''Use the same commands as for the release build, but replace "release" by "debug".''

'''Optional:'''

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.

=== Compile Code::Blocks ===
Now, before this step, you have prepared all the stuff to build code::blocks. It's very interesting that we use code::blocks to build code::blocks binaries.

==== Open project====
Open the project file '''CodeBlocks.cbp'''. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.

[[Image:Global_variable.png]]

[[Image:Global_variable2.png]]

====Compile project====
Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.

[[Image:Win build button.png]]

[[Image:Win build target.png]]

[[Image:Win build finish.png]]

====Copy wxWidgets support DLL====
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_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).

[[Image:Win output folder.png]]

[[Image:Win copy dll.png]]

====Runing script file====
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.

[[Image:Win run bat.png]]

The stripped ("production") executable is found in <tt>output</tt> folder 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. 
Congratulations, you own a freshly built version of Code::Blocks!

[[Image:Win final folder.png]]

====Note for future updates====
Go to the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect). 
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>.

=== Install Code::Blocks ===

Copy the folder output to where you want Code::Blocks to reside.

=== Compile contributed (or your own) plugins ===

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). 

[[Image:Contribute plugin.png]]

When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. This is the path that contains the sdk folder normally this is codeblocks\src. 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.

Don't forget to run update.bat again after building the contrib plugins.

== ANSI Build ==

<div style="background-color: #f7d9d9; border: 1px solid #000">
<div style="margin: 5px;">

==== DEPRECATION WARNING: ====
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. 
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''

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.

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.

</div>
</div>

==== Compile wxWidgets in ANSI mode ====

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

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

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.

'''Optional:'''

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.

==== Compile Code::Blocks ====

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.

'''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:
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).

Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.

After the compilation has finished, copy wxmsw28u_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 [[wikipedia:DLL Hell|dll hell]]).
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.
The location of executable is src\output in C::B tree. From here you'll not need the nightly build anymore.

One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).

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 !

==== Install Code::Blocks ====

Copy the folder output to where you want Code::Blocks to reside.

==== Compile contributed (or your own) plugins ====

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.

Note that the Nassi Shneiderman plugin (part of the contrib plugins) has a dependency on [http://www.boost.org boost] which is needed to compile this plugin. Boost does not need to be compiled therefore.