Code::Blocks - User contributions [en]

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2007-12-23T11:25:13Z

Wobien: /* Installing MinGW */ made link to Installing wxWidgets 2.8.6

These are the instructions for compiling wxWidgets for use with Code::Blocks. They are primarily intended in preparation for compiling Code::Blocks itself but (hopefully) may also help installing wxWidgets for general development using that framework.

Although these instructions are targeted at the Windows operating system, it should be possible to apply them with slight adjustments to other platforms, since we make use of MinGW.

==Warning==
From november 2007 onwards you need wxWidgets 2.8.6 to develop Code::Blocks. See: [[Compiling wxWidgets 2.8.6 to develop Code::Blocks (MSW)]]

== Installing MinGW ==
'''If you have installed the Code::Blocks and MinGW bundle, or already installed MinGW on your own, you can skip this section.'''

Grab the latest MinGW files from the [http://www.mingw.org/download.shtml MinGW download site] and install them into a directory of your choice.

'''NOTE:''' In these instructions we call the MinGW directory ''<MINGW>'', therefore you have to replace it with your corresponding directory.

'''NOTE:''' The files are compressed tarballs. You may need a third-party extraction utility like [http://www.7-zip.org/ 7-Zip] in order to extract them.

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]
* [http://prdownloads.sourceforge.net/mingw/gdb-6.3-2.exe?download?download gdb-6.3-2.exe] (GDB is not mandatory, but useful for debugging purposes)

After successful installation of the above, make sure you have the following directories included in your PATH environment variable:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

(You can add them by right-clicking the ''My Computer'' icon on your desktop and selecting ''Properties''. Then select the ''Advanced'' tab and choose ''Environment Variables''.)

== Installing the wxWidgets source code ==
The wxWidgets 2.6.2 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets download site]. (Note that there is also a winhelp file available.) You can choose between an installer and a zip file. You can just get the zip file because the installer is also a zipped version.

If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.

'''NOTE:''' For the remainder of these instructions we call the wxWidgets directory ''<WXWIN>''. You have to change it to your corresponding directory (e.g. "c:\wxWidgets-2.6.2").

'''NOTE:''' You do not need MSYS. Furthermore, you cannot have MSYS in your path, or the wxWidgets compilation will fail. Thus, if you have MSYS installed, ensure that ''<MSYS>\bin'' '''is not''' in your path before compiling wxWidgets. wxWidgets must be compiled from a "regular" command line (like cmd.exe), not from a Unix-like shell. The same problem could arise if Cygwin is in the path.

== Checking make version ==
If you didn't install MinGW yourself you have to ensure you are using a recent enough version of the make utility. Open a command prompt and type:
<tt>mingw32-make -v</tt>
The version should read 3.80 or greater, else you need to install a newer version.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>

'''NOTE: The following instructions do not work with MSYS, or other forms of Unix on Windows.'''

Now the first thing to do is to clean up the source:
mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 BUILD=release clean
'''NOTE:''' Make sure you use exactly the same options for this step and for the build step below. The clean target uses these variables and only cleans the specified version of the generated object and library files (so it will actually not clean the intended files if these variables are not identical).

'''NOTE:''' If you still have problems with compiling after cleaning, you could try to manually remove the gcc_msw directory under the build\msw directory. This directory is the place where the object files are stored.

When everything is clean you can start actually compiling wxWidgets:
mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 BUILD=release

'''NOTE:''' These options are the officially supported Code::Blocks options. If you want another version of wxWidgets (debug or non-unicode) you still have to make sure you build a MONOLITHIC version (one big DLL) for linking Code::Blocks against.

Now you can get a cup of coffee or do something else because this step takes some time. Make sure there was no compilation error before you continue.

'''NOTE:''' If you're having errors because of libjpeg, you might want to look at [http://sourceforge.net/tracker/?func=detail&atid=309863&aid=1606032&group_id=9863 this patch]

== Compiling Code::Blocks ==
=== Setting up paths ===
Before finally compiling Code::Blocks itself, you need to setup the paths:
*Open the Code::Blocks project (CodeBlocks.cbp).
*It will ask you to define a [[Global compiler variables|Global variable]]
*Set the path to where you have wxWidgets installed (e.g. "c:\wxWidgets-2.6.2").
*Compile Code::Blocks.

=== Post compilation steps ===
When the compilation process is finished, simply run the update.bat script. It will ensure that all resource files Code::Blocks uses are in the right place and up to date.

== Building wxWidgets 2.6.2 using VC++ Toolkit 2003 ==
I'll just throw in my notes on the process for both compiler versions as getting VC++ toolkit to work is quite a pain. Code::Blocks needs a couple of changes to support wxWidgets with the VC++ toolkit seamlessly.

install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->'''Run all''' Windows XP 32-bit Build Environment (Retail) batch files '''(find them in '''PlatformSDK\Setup''')''' 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\'''Vc7\bin'''\vcvars32.bat (not needed) 
 
'''The following environment vars must be set/modified/added via 'Control Panel | System | Advanced | Environment Variables'.'''
 
 
set DOTNETSDK=C:\Program Files\Microsoft.NET\SDK\v1.1 (not needed) 
set MSVC=C:\Program Files\Microsoft Visual C++ Toolkit 2003 
set MSSDK=C:\Program Files\Microsoft Platform SDK 
set VC7=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7 
set INCLUDE=%MSVC%\include;%MSSDK%\include 
set LIB=%MSVC%\lib;%MSSDK%\lib;%VC7%\lib 
set PATH=%MSVC%\bin;%MSSDK%\bin;%PATH% 
set PATH=%PATH%;%MSSDK%\bin\Win64 
 

cd <WXWIN>\build\msw 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 CFG=NonUnicode clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 CFG=NonUnicode 



cd <WXWIN>\lib; move vc_dll codeblocks_vc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_vc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_vc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL
compiler->compiler flags
enable c++ exception handling (or other options: /GX [same as /EHsc])
compiler->other options
delete -D__GNUWIN32__
linker->link libraries
delete ctl3d32

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.2\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26_vc_custom.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.2\lib\codeblocks_vc (not recommended)

compile->compiler options
programs->additional paths
C:\Program Files\Microsoft Platform SDK\Bin
directories->compiler
add C:\Program Files\Microsoft Platform SDK\Include
directories->linker
add C:\Program Files\Microsoft Platform SDK\Lib

copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release

Installing Code::Blocks from source on Windows

2007-12-23T11:04:49Z

Wobien: /* 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 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]].

Since November 2007 MinGW-GCC 4.2.1

=== wxWidgets ===

[http://wxwidgets.org/ wxWidgets.org]

Code::Blocks officially supports wxWidgets 2.6.3 (although any 2.6+ version probably works). 
Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.3-1.zip wxMSW-2.6.3-1.zip].

Code::Blocks uses
* since May 2007 wxWidgets 2.8.4 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.4.zip wxMSW-2.8.4.zip]

* since November 2007 wxWidgets 2.8.6 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.6.zip wxMSW-2.8.6.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'').
[http://www.beispiel.de Link-Text]

=== 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 preferrable to the manual parsing of the entries file that is used as fallback.

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 builtin fallback mechanism in <tt>autorevision</tt> has been updated to the new 1.4 format and will no longer work with the old format. 
Therefore, if you use a Subversion client from the 1.0-1.3 line, you ''must'' put the commandline tool into <tt>PATH</tt> for a successful build. 
If you use Subversion 1.4, then it is good practice nevertheless, but you can do without, too.

=== zip.exe ===

You'll also need a working 'zip' program.
If you have the version listed on our [https://wiki.codeblocks.org/index.php?title=Mingw#Other_developer_tools tools page], you'll be fine.

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...".

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 svn://svn.berlios.de/codeblocks/trunk

== Building ==

=== 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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc USE_XRC=1 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.

''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 ====

Open the project CodeBlocks.cbp. You will be prompted to define the global variable $(#wx). Enter the location where you unpacked wxWidgets.

Hit the blue gear and lean back. Compilation may take 3-5 minutes, depending on the speed of your computer.

After the compilaton has finished, copy <tt>lib\gcc_dll\wxmsw26u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>src\devel</tt> directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into dll hell).

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.
The stripped ("production") executable is found in <tt>output</tt> together with all libraries and data files. If you want a version with debug symbols instead (caution: huge size!), use the one found in the <tt>devel</tt> folder. 
Congratulations, you own a freshly built version of Code::Blocks!

For future updates, go into 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). 
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 compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).
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 nighty 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.

Talk:Main Page

2007-12-14T22:19:46Z

Wobien:

just a suggestion, but you may want to enable posting only by users of the wiki in order to save your front page, judging by the number of reverts due to spam it has.

Done. mandrav took care of it. :D

/index.php?topic=2733.0

Next suggestion: under "Downloads and Installation", this main page says, "Nightly Cookbook - How to install a nightly build". But when I click on "Nightly Cookbook", I find instructions for collecting tools to _create_ a nightly build. I see nothing about how to install a nightly build downloaded from the forum.

Now I realize that 'killerbot' is not finished with the page, but in the meantime, can we call a spade a spade? Please list it as "How to Create a Nightly Build", not as "How to _install_ one".

Finally, may I suggest making a separate, but clearly related link on how to install one. After all, many users will surely want to install a nightly build, but surely only a few will need to make one.

[[Installing_Code::Blocks#Alternative_method_for_installing_a_nightly_build |Here]] are instructions for installing a nightly build. :)

[[User:Sethjackson|Sethjackson]] 07:48, 29 May 2006 (EDT)

----

Other suggestions:

I have tried to compile the hello world example from the first tutorial, and "like always" ran into some problems: I had installed wxWindows, but I was not aware that it has to be compiled (=> "Unable to open wx/setup.h"). Besides as I recently read in the forum, it has to be compiled using the code blocks install instructions. It would be good to have a trouble shooting page that addresses all these typical newbie problems, and the link to this should be close to the download link.

Maybe even a better solution for this: have a "requirements" page that clearly lists everything which is not obvious, and which is read _before_ users start downloading codeblocks.

Category list in navigation pane:

I suggest to put a link to the file "Categories" in the navigation pane.
It is a very handy list if you are searching information. As it is now I get it via Special pages, but it has taken some time before I found it.
If you are new to the Wiki you don't expect to find elementary information for newbies on special pages.
[[User:Wobien|Wobien]] 22:17, 14 December 2007 (UTC)

Talk:Main Page

2007-12-14T22:18:36Z

Wobien:

just a suggestion, but you may want to enable posting only by users of the wiki in order to save your front page, judging by the number of reverts due to spam it has.

Done. mandrav took care of it. :D

/index.php?topic=2733.0

Next suggestion: under "Downloads and Installation", this main page says, "Nightly Cookbook - How to install a nightly build". But when I click on "Nightly Cookbook", I find instructions for collecting tools to _create_ a nightly build. I see nothing about how to install a nightly build downloaded from the forum.

Now I realize that 'killerbot' is not finished with the page, but in the meantime, can we call a spade a spade? Please list it as "How to Create a Nightly Build", not as "How to _install_ one".

Finally, may I suggest making a separate, but clearly related link on how to install one. After all, many users will surely want to install a nightly build, but surely only a few will need to make one.

[[Installing_Code::Blocks#Alternative_method_for_installing_a_nightly_build |Here]] are instructions for installing a nightly build. :)

[[User:Sethjackson|Sethjackson]] 07:48, 29 May 2006 (EDT)

----

Other suggestions:

I have tried to compile the hello world example from the first tutorial, and "like always" ran into some problems: I had installed wxWindows, but I was not aware that it has to be compiled (=> "Unable to open wx/setup.h"). Besides as I recently read in the forum, it has to be compiled using the code blocks install instructions. It would be good to have a trouble shooting page that addresses all these typical newbie problems, and the link to this should be close to the download link.

Maybe even a better solution for this: have a "requirements" page that clearly lists everything which is not obvious, and which is read _before_ users start downloading codeblocks.

Category list in navigation pane:

I suggest to put a link to the file Categories in the navigation pane.
It is a very handy list if you are searching information. As it is now I get it via Special pages, but it has taken some time before I found it.
If you are new to the Wiki you don't expect to find elementary information for newbies on special pages.
[[User:Wobien|Wobien]] 22:17, 14 December 2007 (UTC)

Talk:Main Page

2007-12-14T22:17:52Z

Wobien: Category list in navigation pane

just a suggestion, but you may want to enable posting only by users of the wiki in order to save your front page, judging by the number of reverts due to spam it has.

Done. mandrav took care of it. :D

/index.php?topic=2733.0

Next suggestion: under "Downloads and Installation", this main page says, "Nightly Cookbook - How to install a nightly build". But when I click on "Nightly Cookbook", I find instructions for collecting tools to _create_ a nightly build. I see nothing about how to install a nightly build downloaded from the forum.

Now I realize that 'killerbot' is not finished with the page, but in the meantime, can we call a spade a spade? Please list it as "How to Create a Nightly Build", not as "How to _install_ one".

Finally, may I suggest making a separate, but clearly related link on how to install one. After all, many users will surely want to install a nightly build, but surely only a few will need to make one.

[[Installing_Code::Blocks#Alternative_method_for_installing_a_nightly_build |Here]] are instructions for installing a nightly build. :)

[[User:Sethjackson|Sethjackson]] 07:48, 29 May 2006 (EDT)

----

Other suggestions:

I have tried to compile the hello world example from the first tutorial, and "like always" ran into some problems: I had installed wxWindows, but I was not aware that it has to be compiled (=> "Unable to open wx/setup.h"). Besides as I recently read in the forum, it has to be compiled using the code blocks install instructions. It would be good to have a trouble shooting page that addresses all these typical newbie problems, and the link to this should be close to the download link.

Maybe even a better solution for this: have a "requirements" page that clearly lists everything which is not obvious, and which is read _before_ users start downloading codeblocks.

== Category list in navigation pane ==

I suggest to put a link to the file Categories in the navigation pane.
It is a very handy list if you are searching information. As it is now I get it via Special pages, but it has taken some time before I found it.
If you are new to the Wiki you don't expect to find elementary information for newbies on special pages.
[[User:Wobien|Wobien]] 22:17, 14 December 2007 (UTC)

Talk:Creating a simple "Hello World" plugin

2007-12-14T22:06:59Z

Wobien:

I changed the first paragraph. I deleted outdated text and I added a link to the articles about installing C::B from source.

I think the pararaph "Letting the compilor know where to find the SDK" should be changed as well.
I know that for Windows users this is not necessary, if you compiled C::B it's allready done.
I suppose that is also true for other platforms, but I don't want to delete this paragraph without knowing for sure.

[[User:Wobien|Wobien]] 22:06, 14 December 2007 (UTC)

Talk:Creating a simple "Hello World" plugin

2007-12-14T22:03:55Z

Wobien: New page: I changed the first paragraph. I deleted outdated text and I added a link to the articles about installing C::B from source. I think the pararaph "Letting the compilor know where to find ...

Using STLFilt with MinGW

2007-12-14T20:36:13Z

Wobien: /* Links */ changed links

Welcome to the '''Sandbox''' where you can edit until your heart's content. Check out the 'edit' link at the top of this page to play around in here.

== Italic Text ==

Look at the ''italic text''.

== Bold Text ==

Look at the '''bold text'''.

== Lists ==

*Lists are easy.
**Really easy.

== Images ==

Some images....

[[Image:Chk.png]]
[[Image:Nop.png]]

== Links ==

Links to other pages, external sites. etc

Link to page in this wiki
[[Installing Code::Blocks from source]]

Link with no title
[http://www.google.com]
Link with title
[http://www.google.com The Google Search engine]

Link to category (note the initial colon)
[[:Category:Installation\Build Instructions]]

To categorize a page, remove the initial colon like this: <nowiki>[[Category:Installation\Build_Instructions]]</nowiki>

Creating a simple "Hello World" plugin

2007-12-14T20:31:24Z

Wobien: /* Prerequisites */ You need to all the source files od C::B and compile them, so better link to pages about how to do that

[[Category:Plugin development]]
[[Category:Outdated]]
{{outdated}}
'''NOTE''': This tutorial was written using the Code::Blocks final beta under windows.

==Prerequisites==

This tutorial assumes you have a working version of Code::Blocks installed and some knowledge of how to deal with projects, in particular how to compile them.

Also you need the source files of Code::Blocks and of wxWidgets. You have to compile them before you can compile a plugin. Here you can find instructions:
[[:Category:Installing Code::Blocks from source ]]

==Overview==

This tutorial will guide you through the creation of a simple "Hello World" plugin, which when activated displays "Hello World!" in the Code::Blocks log tab below the editor. This could be done completely by hand, but Code::Blocks contains a very useful plugin project generator (which, incidentally, is a plugin itself), so we'll use that.

==Creating the Plugin Project==

Select the '''File->New->Project''' option from the main menu bar and choose the Code::Blocks Plugin Wizard. You will see a dialog box with some information but you can skip that after reading it. Now you will see the following dialog box:

[[Image:Plugindevelop_2.jpg]]

In the first edit field write the title of your project. You can see that we denoted the project title as '''HelloWordPlugin'''. The other field are self-explanatory. If you click the Next button you will see the next plugin property dialog:

[[Image:Plugindevelop_3.jpg]]

Let's denote the plugin name with '''HelloWorld'''. After clicking the next button a new dialog apears and you can edit a bunch of information about your plugin. In the next step you can choose which compiler you want to use for your plugin project.

===Plugin Type===

The Code::Blocks SDK contains interfaces for various different types of plugins in the ''cbPlugin.h'' file. The drop down ''Plugin type'' list in the wizard allows you to select which type of plugin you wish to build - essentially which class the main plugin interface class will inherit from. We want to build a Tool plugin, so select that from the list. Tool type plugins are added to the Plugins main menu submenu automatically, and their ''Execute'' method is called when they are selected by the user. We will use this later in order to display our message.

===Plugin Info===

The ''Plugin name'' field is the name of the plugin interface class which the wizard will create. Enter "HelloWorldPlugin" here. More information can be provided by clicking on the ''Enter Plugin Info'' button. The fields here are fairly self explanitory, but one which you should pay particular attention to is the ''Title'' field, since this is what Code::Blocks will use to refer to the plugin in the menus. In the generated code, the plugin info is kept in the plugin class' ''m_PluginInfo'' member, which is of the type ''PluginInfo'' and is set in the plugin interface class' constructor. ''PluginInfo'' is detailed in ''cbPlugin.h'', if you want to go take a look.

===Provides Configuration Dialog===

This indicates whether or not the plugin is to provide a configuration dialog which can be accessed through the '''Settings->Configure Plugins''' submenu. We don't need one, so leave this box unchecked.

===Filenames===

The filenames should have been filled in automatically by the dialog when you entered the Plugin name, if you used the name "HelloWorldPlugin", for example, these should be helloworldplugin.h and helloworldplugin.cpp respectively. If you want to change the names of the files generated, this is where to do it (this tutorial will assume you have left them as the default values).

The guard-block box is simply if you wish to place inclusion guards in the header file, and if you do what symbol to use. If you don't know what these are then just leave it as it is.

Click '''Create''' and take note of the next dialog box's message about the SDK include and library directories, that's what we'll be dealing with next.

==Letting the project know where to find the SDK==

Code::Blocks should have created a new project called "Custom Plugin". Before we can compile anything we need to make sure that the compiler knows where the sdk files are in order to include headers and link the libraries. If your compiler has not been setup to know where wxWidgets is yet then this must also be done (see the links in Prerequisites for more details).

Right click on the project and select '''Build Options''' then the '''Directories''' tab. Here, make sure the '''Compiler''' tab is selected then click on the '''Add''' button. Browse to where you unzipped the SDK and select the ''include'' directory (for example ''C:\CodeBlocks\sdk\include'' if you installed the SDK there), then click okay and select whether or not the path should remain relative. Go to the "Linker" tab and add the "lib" directory under where the SDK was installed in similar fashion (following my install, this would be in ''C:\CodeBlocks\sdk\lib'').

===Linker Options===

If you click on the '''Linker Options''' tab at the top level in the Build Options dialog, you will see that the plugin is being linked to the Code::Blocks core library (codeblocks) and the wxWidgets library (wxmsw242 under windows ''NOTE: The plugin generator uses 2.4.2, if you're using a different version of wxWidgets then change this'').

===Compiler Options===

The '''Compiler Options''' tab shows that several symbols have been defined when the plugin is compiled: ''__GNUWIN32__'', ''WXUSINGDLL'' and ''BUILDING_PLUGIN'' in this case (using windows). The first two are indicators to wxWidgets of the compiler and DLL options to use, and the last is an indicator to the Code::Blocks SDK headers that they are being used to build a plugin (which affects whether or not symbols are exported or imported for the DLL - see ''cbPlugin.h'' for example).

==Adding Functionality==

The plugin wizard should have generated us helloworldplugin.h and helloworldplugin.cpp. The header file contains the class definition; what we're interested in, however, is the definition of the class methods in helloworldplugin.cpp. The plugin wizard has generated a constructor, a destructor and three methods. ''OnAttatch'' and ''OnRelease'' are methods called to inform the plugin when it is attached (the user has selected it and Code::Blocks has loaded it) or released (Code::Blocks no longer has a use for it or is shutting down). Since our plugin does not need to perform any actions on loading or shutting down, we can leave these as they are.

The ''Execute'' method, as mentioned earlier, is what we are really interested in. We are going to use the ''LogManager'' class to add a log message in the window beneath the editor. To do this we will need access to both the Manager class and the LogManager class. Manager is and internal Code::Blocks class which is used to keep track of internal information and the various task specific managers (like the LogManager and EditorManager - which is used to keep track of all the open files and their editors). LogManager is responsible for both normal output and debugging output (see ''logmanager.h'' for more details). Replace the generated Execute method with this new one:

int HelloWorldPlugin::Execute()
{
if( !IsAttached() )
return -1;
Manager::Get()->GetLogManager()->Log( _("Hello World!") );
return 0;
}

This new method uses the Manager's static Get method to return the singleton Manager object, then uses that to access the LogManager through the GetLogManager method. LogManager has a method called ''Log'' which appends a string to the bottom of the output log, so we use this to add the "Hello World!" message. The _() construct is part of wxWidgets' internationalisation utilities, and more information on it can be found in the wxWidgets [http://wiki.wxwidgets.org/wiki.pl?WxWidgets_Source_Oddities documentation].

The first two lines check to see if the plugin has been attatched (in other words selected by the user in the '''Plugins->Manage plugins''' menu), and thus whether it should perform any action at all. Currently the return value of Execute is not used anywhere, but all the default plugins use -1 for failure and 0 for success.

==Compile! (And test)==

(New)
The time is right and we should compile the project. The next step is to install the plugin. Go to the '''Plugins->Manage plugins''' option. Hit the '''Install new''' button. The manager ask you where the plugin lies. Go to that folder and select the *.cbplugin file. Code::Blocks imports your plugin automatically. If this procedure was successful you can see your plugin in the ''Installed plugins'' list. To execute your plugin go to the '''Plugins''' menu and choose your plugin. That's all.

(Old)
This should produce a file called HelloWorldPlugin.dll, which can be tested by copying to the ''CodeBlocks\share\CodeBlocks\plugins\'' directory and restarting Code::Blocks. There should now be an option in the '''Plugins''' menu for "Hello World" (or whatever the title field was set to when the plugin was generated - or in ''m_PluginInfo''). Click on this and "Hello World!" should appear in the Code::Blocks logging window. Congratulations, you've just created your first plugin!

==Further Information==

It is essential to learn how wxWidgets works if you seriously plan on working on plugins, since most of Code::Blocks depends on it, and you will find it easier to add and manipulate components if you have a firm grasp of its principles. More information on this can be found in the wxWidgets [http://www.wxwidgets.org/docs.htm documentation]. Another good place to learn from is the source code from the existing Code::Blocks plugins, which can be downloaded along with the rest of the Code::Blocks source code from the [https://www.codeblocks.org/downloads.shtml download page].

Hopefully this tutorial has helped you work through a few fundamentals in terms of creating plugins, happy coding!

Using STLFilt with MinGW

2007-12-14T20:09:39Z

Wobien:

Welcome to the '''Sandbox''' where you can edit until your heart's content. Check out the 'edit' link at the top of this page to play around in here.

== Italic Text ==

Look at the ''italic text''.

== Bold Text ==

Look at the '''bold text'''.

== Lists ==

*Lists are easy.
**Really easy.

== Images ==

Some images....

[[Image:Chk.png]]
[[Image:Nop.png]]

== Links ==

Links to other pages, external sites. etc

Link to page in this wiki
[[Installing Code::Blocks from source]]

Link with no title
[http://www.google.com]

Link with title
[http://www.google.com The Google Search engine]

Link to category (note the initial colon)
[[:Category:Installation\Build Instructions]]

To categorize a page, remove the initial colon like this: <nowiki>[[Category:Installation\Build_Instructions]]</nowiki>

File:Foto wobien.jpg

2007-12-14T11:40:25Z

Wobien:

i uploaded this not knowing how to delete it: please delete!

File:Foto wobien.jpg

2007-12-14T11:00:39Z

Wobien:

Installing a supported compiler

2007-12-13T16:59:46Z

Wobien: /* Compiler-neutral setup steps */

[[Category:User Documentation]]
When you launch Code::Blocks for the first time, it will scan the system for any supported compilers (it takes virtually no time). After this scan completes, Code::Blocks will have been configured for the found compiler(s). Code::Blocks will also be configured even for compilers that were not found (default installation settings will be used for each of those compilers).

For more info on how to download and install each of the above compilers, please read on.

==Windows==
Currently supported compilers, at the time of this writing are:
* [http://www.mingw.org MinGW GCC C/C++ Free Compiler, including G77 (Fortran)]
* [http://mspgcc.sourceforge.net/ MSP430 GCC C/C++]
* [http://www.hightec-rt.com/ TriCore GCC C/C++]
* [http://www.hightec-rt.com/ PowerPC GCC C/C++]
* [http://msdn.microsoft.com/visualc/vctoolkit2003 Microsoft's Visual C++ Free Toolkit 2003]
* [http://www.borland.com/products/downloads/download_cbuilder.html Borland's C/C++ Free Compiler 5.5]
* [http://www.digitalmars.com/ Digital Mars Free C/C++ Compiler]
* [http://store.scitechsoft.com/product_info.php?products_id=37/ OpenWatcom Free C/C++ Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]

=== Downloading the GNU GCC compiler & GDB debugger ===

Go to MinGW's [http://www.mingw.org/download.shtml downloads] page and download the file named <code>MinGW-x.y.z.exe</code>, where x, y and z are version numbers. At the time of this writing, this file is <code>MinGW-3.1.0-1.exe</code>. If you consider yourself lucky, you might also try <code>MinGW-3.2.0-rc-3.exe</code>. It's not a stable release yet, but it works and lacks some bugs the older version has.
These setup files contain everything needed to compile and debug windows programs.

=== Downloading the Microsoft Visual C++ Free Toolkit 2003 ===

====This no longer works as discribed since the Toolkit was removed in favor of the 2005 release.====

Go to this [http://msdn.microsoft.com/visualc/vctoolkit2003 MSDN site] and click on the link labeled "Download the Visual C++ Toolkit 2003". This will download the setup file.

NOTE: ''This download is not sufficient for building windows programs. You will also have to download and install the [http://www.microsoft.com/msdownload/platformsdk/instmsi.htm Microsoft Platform SDK]''...

=== Downloading the Borland C++ Compiler 5.5 ===

NOTE: ''At some point, you will be asked to register with Borland and fill out a survey. Registration is free.''

Go to [http://www.borland.com/products/downloads/download_cbuilder.html# Borland's downloads] and click on the link labeled "Compiler". After you accept the license agreement, you will be provided with download links to the setup file.

=== Downloading the Digital Mars C/C++ Free Compiler ===

Go to [http://www.digitalmars.com/download/dmcpp.html DigitalMars]. Accept the license agreement and you'll be redirected to a page containing download links.

In that page, download:
*The '''Digital Mars C/C++ Compiler''' (<tt>dm8**c.zip</tt>)
*The '''Basic Utilities''' (<tt>bup.zip</tt>)
*The '''STLport''' library (<tt>stlport.zip</tt>)

Open <tt>dm\bin\sc.ini</tt> in a text editor, and replace the line
INCLUDE="%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%
with
INCLUDE="%@P%\..\stlport\stlport";"%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%

=== Configuring CodeBlocks to use the Intel C++ Compiler ===
''Note: this info is for 1.0RC1 and previous versions, now C::B haves direct support for Intel C++.''

After various user requests, we decided to post here the info to support the Intel Compiler on CodeBlocks. This should be easy, since the Intel Compiler can emulate the MSVC++ compiler.

* change MS Toolkit linker from cl.exe to icl.exe
* add (installation path to the Intel C++)\Ia32\Bin to the "Programs -> Extra paths"
* add "-D_USE_INTEL_COMPILER" to "Compiler options"
* add (installation path to the Intel C++)\Ia32\Include and \lib to the "Global compiler options -> Directories"
* add some options like "/QaxK" to the "Compiler options" (icl -help)

==Linux==
Currently supported compilers, at the time of this writing are:
* [http://gcc.gnu.org/ GNU GCC C/C++ Free Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Linux you'll, most probably, already have everything that is needed in order to compile. All major Linux distributions (RedHat, Debian, SuSE, Mandriva, Gentoo, ArchLinux, etc) come with GCC & GDB preinstalled. To make sure you have have gcc installed, go to your terminal and type 'gcc -v'. In case you have GCC installed, you will get GCC's compile options and version number.

==Mac OS X==
The Mac OS X port efforts has began recently, but it should be a matter of time until these compilers will be supported:
* [http://gcc.gnu.org/ GNU GCC]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel Compiler beta (not yet released to public)]
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Mac you'll need to install Xcode Tools from http://developer.apple.com/tools/

This will install Apple versions of:

http://www.gnu.org/software/gcc/
http://www.gnu.org/software/gdb/
http://www.gnu.org/software/make/

== Compiler-neutral setup steps ==

Now that you have downloaded the setup file of the compiler of your choice, launch its installation by double-clicking on the setup file. The actual installation process is really simple. Just press "Next" all the way and you 're done.

If you installed the compiler on its default installation directory, there is nothing more to configure. Launch Code::Blocks and you 're all set :)

If that is not the case, launch Code::Blocks. If it is the first time you launch it, the compiler auto-detection will be launched.
If your compiler was not auto-detected, go to "Settings->Compiler and Debugger->Global Compiler settings->Toolchain executables", select the compiler you installed and press "Auto-detect".
If you get a message saying that the compiler was auto-detected, congratulations!
If not, then press the button with the three dots next to the "Auto-detect" button and select the installation directory of your compiler manually.

NOTE: ''The compiler's installation directory is exactly this: the installation directory. Not the "bin" subdirectory nor any other.''

Installing a supported compiler

2007-12-13T16:58:32Z

Wobien: updated steps to set compilor folder

[[Category:User Documentation]]
When you launch Code::Blocks for the first time, it will scan the system for any supported compilers (it takes virtually no time). After this scan completes, Code::Blocks will have been configured for the found compiler(s). Code::Blocks will also be configured even for compilers that were not found (default installation settings will be used for each of those compilers).

For more info on how to download and install each of the above compilers, please read on.

==Windows==
Currently supported compilers, at the time of this writing are:
* [http://www.mingw.org MinGW GCC C/C++ Free Compiler, including G77 (Fortran)]
* [http://mspgcc.sourceforge.net/ MSP430 GCC C/C++]
* [http://www.hightec-rt.com/ TriCore GCC C/C++]
* [http://www.hightec-rt.com/ PowerPC GCC C/C++]
* [http://msdn.microsoft.com/visualc/vctoolkit2003 Microsoft's Visual C++ Free Toolkit 2003]
* [http://www.borland.com/products/downloads/download_cbuilder.html Borland's C/C++ Free Compiler 5.5]
* [http://www.digitalmars.com/ Digital Mars Free C/C++ Compiler]
* [http://store.scitechsoft.com/product_info.php?products_id=37/ OpenWatcom Free C/C++ Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]

=== Downloading the GNU GCC compiler & GDB debugger ===

Go to MinGW's [http://www.mingw.org/download.shtml downloads] page and download the file named <code>MinGW-x.y.z.exe</code>, where x, y and z are version numbers. At the time of this writing, this file is <code>MinGW-3.1.0-1.exe</code>. If you consider yourself lucky, you might also try <code>MinGW-3.2.0-rc-3.exe</code>. It's not a stable release yet, but it works and lacks some bugs the older version has.
These setup files contain everything needed to compile and debug windows programs.

=== Downloading the Microsoft Visual C++ Free Toolkit 2003 ===

====This no longer works as discribed since the Toolkit was removed in favor of the 2005 release.====

Go to this [http://msdn.microsoft.com/visualc/vctoolkit2003 MSDN site] and click on the link labeled "Download the Visual C++ Toolkit 2003". This will download the setup file.

NOTE: ''This download is not sufficient for building windows programs. You will also have to download and install the [http://www.microsoft.com/msdownload/platformsdk/instmsi.htm Microsoft Platform SDK]''...

=== Downloading the Borland C++ Compiler 5.5 ===

NOTE: ''At some point, you will be asked to register with Borland and fill out a survey. Registration is free.''

Go to [http://www.borland.com/products/downloads/download_cbuilder.html# Borland's downloads] and click on the link labeled "Compiler". After you accept the license agreement, you will be provided with download links to the setup file.

=== Downloading the Digital Mars C/C++ Free Compiler ===

Go to [http://www.digitalmars.com/download/dmcpp.html DigitalMars]. Accept the license agreement and you'll be redirected to a page containing download links.

In that page, download:
*The '''Digital Mars C/C++ Compiler''' (<tt>dm8**c.zip</tt>)
*The '''Basic Utilities''' (<tt>bup.zip</tt>)
*The '''STLport''' library (<tt>stlport.zip</tt>)

Open <tt>dm\bin\sc.ini</tt> in a text editor, and replace the line
INCLUDE="%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%
with
INCLUDE="%@P%\..\stlport\stlport";"%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%

=== Configuring CodeBlocks to use the Intel C++ Compiler ===
''Note: this info is for 1.0RC1 and previous versions, now C::B haves direct support for Intel C++.''

After various user requests, we decided to post here the info to support the Intel Compiler on CodeBlocks. This should be easy, since the Intel Compiler can emulate the MSVC++ compiler.

* change MS Toolkit linker from cl.exe to icl.exe
* add (installation path to the Intel C++)\Ia32\Bin to the "Programs -> Extra paths"
* add "-D_USE_INTEL_COMPILER" to "Compiler options"
* add (installation path to the Intel C++)\Ia32\Include and \lib to the "Global compiler options -> Directories"
* add some options like "/QaxK" to the "Compiler options" (icl -help)

==Linux==
Currently supported compilers, at the time of this writing are:
* [http://gcc.gnu.org/ GNU GCC C/C++ Free Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Linux you'll, most probably, already have everything that is needed in order to compile. All major Linux distributions (RedHat, Debian, SuSE, Mandriva, Gentoo, ArchLinux, etc) come with GCC & GDB preinstalled. To make sure you have have gcc installed, go to your terminal and type 'gcc -v'. In case you have GCC installed, you will get GCC's compile options and version number.

==Mac OS X==
The Mac OS X port efforts has began recently, but it should be a matter of time until these compilers will be supported:
* [http://gcc.gnu.org/ GNU GCC]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel Compiler beta (not yet released to public)]
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Mac you'll need to install Xcode Tools from http://developer.apple.com/tools/

This will install Apple versions of:

http://www.gnu.org/software/gcc/
http://www.gnu.org/software/gdb/
http://www.gnu.org/software/make/

== Compiler-neutral setup steps ==

Now that you have downloaded the setup file of the compiler of your choice, launch its installation by double-clicking on the setup file. The actual installation process is really simple. Just press "Next" all the way and you 're done.

If you installed the compiler on its default installation directory, there is nothing more to configure. Launch Code::Blocks and you 're all set :)

If that is not the case, launch Code::Blocks. If it is the first time you launch it, the compiler auto-detection will be launched.
If your compiler was not auto-detected, go to "Settings->Compilor and Debugger->Global Compilor settings->Toolchain executables", select the compiler you installed and press "Auto-detect".
If you get a message saying that the compiler was auto-detected, congratulations!
If not, then press the button with the three dots next to the "Auto-detect" button and select the installation directory of your compiler manually.

NOTE: ''The compiler's installation directory is exactly this: the installation directory. Not the "bin" subdirectory nor any other.''