Code::Blocks - User contributions [en]

Installing a supported compiler

2010-03-05T03:44:12Z

Seronis: /* (Unofficial) TDM - "Twilight Dragon Media" */

[[Category:User Documentation]]
When you launch Code::Blocks for the first time, it will scan the system for any supported compilers. Once this scan has finished, Code::Blocks will have been correctly configured for any detected compilers. Code::Blocks will also have default configurations even for compilers that were not found.

This article is a guide for obtaining, installing, and configuring the various compilers that Code::Blocks can use.

== Windows ==

Once you've installed a new compiler, be sure to read the Compiler-neutral setup steps at the end of this article.

At the time of this writing, Code::Blocks supports the following compilers in Windows:
* [http://www.mingw.org MinGW GCC C/C++ Free Compiler, including G77 (Fortran)]
** [http://www.cygwin.org Cygwin GCC C/C++ Free Compiler]
*** HOWTO: Use Cygwin 1.7 with Code::Blocks
* [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]

=== MinGW/GCC ===
The official MinGW website is at [http://www.mingw.org mingw.org]. A MinGW-bundled version of the latest Code::Blocks release is available from the [https://www.codeblocks.org/downloads/5#windows Code::Blocks download page]. If you install this version, the GCC compiler will be automatically detected and set as the default. Also you can use the TDM's GCC/mingw32 Builds from [/index.php/topic,10508.0.html] or [http://www.tdragon.net/recentgcc/].

'''Note''': In any case, if you don't install MinGW in C:\MinGW, you'll need to update the configuration of GCC in Code::Blocks.

==== Official MinGW.org ====
You can install '''MinGW''' yourself, by using an automatic downloader/installer or by downloading and unpacking the required packages by hand from [http://www.mingw.org mingw.org], here: [http://sourceforge.net/projects/mingw/files/].

Packages required (suggested) for MinGW/GCC v3.4.5:
* Compiler:
** gcc-build-3.4.5-20060117-3.tar.gz
** gcc-core-3.4.5-20060117-3.tar.gz
** gcc-g++-3.4.5-20060117-3.tar.gz
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz

Packages required (suggested) for MinGW/GCC v4.4.0:
* Compiler:
** gcc-full-4.4.0-mingw32-bin-2.tar.lzma
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz

==== HOWTO: Use Cygwin 1.7 with Code::Blocks ====
Cygwin 1.7 changed the way symlinks were created and handled when invoked from a command prompt. I couldn't find a way to force CB to use a unix-link shell, but was able to find a work around when perusing the Cygwin mailing lists.

The symptom would show up with a message similar to the one below:

Execution of 'g++.exe -Wall -fexceptions -g -c c:/dev/code/cb1/main.cpp -o obj/Debug/main.o' in 'c:\dev\code\cb1' failed.

Executing the same command from the CMD.EXE prompt yields an "Access is denied" message. This was how I was able to track down why the issue occurred. For more info, see this cygwin mailing list thread: http://www.mail-archive.com/cygwin@cygwin.com/msg104088.html

'''[[Solution]]'''

The solution is to point your compiler and linker directly to the version of gcc and g++ that you want to use.

In my case, I wanted to use gcc-4.exe and g++-4.exe and so, I went into Settings->Compiler and Debugger->Toolchain executables. There I changed the "C Complier", "C++ Compiler" and "Linker for dynamic libs" to point to gcc-4.exe, g++-4.exe and g++-4.exe.

After this, compilation and linking worked fine.

It would also be a good idea to add an environment variable CYGWIN with a value of nodosfilewarning in Settings->Environment->Environment Variables. This eliminates the following (harmless) warning message:

MS-DOS style path detected: c:/
Preferred POSIX equivalent is: /c
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames

==== (Unofficial) TDM - "Twilight Dragon Media" ====
These packages are called '''TDM's GCC/mingw32 Builds''' and can be obtained from [/index.php/topic,10508.0.html] or [http://www.tdragon.net/recentgcc/].

Packages required (suggested) for TDM's GCC/mingw32 Builds v4.4.1-tdm-2 SJLJ:
...which can be found here: [http://sourceforge.net/projects/tdm-gcc/files/] under: TDM-GCC 4.4 series -> 4.4.1-tdm-2 SJLJ.
* Compiler:
** gcc-4.4.1-tdm-2-core.zip
** gcc-4.4.1-tdm-2-g++.zip
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326-3.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz
These packages are included in both the [http://sourceforge.net/projects/tdm-gcc/files/TDM-MinGW%20Installer/1.908.0/tdm-mingw-1.908.0-4.4.1-2.exe/download Bundled Installer] and the [http://sourceforge.net/projects/tdm-gcc/files/TDM-MinGW%20Installer/1.908.0/tdm-mingw-1.908.0-webdl.exe/download On-Demand Installer] available via TDMs page referenced above for users who do not wish to download and install them manually.

=== Microsoft Visual C++ ===
The official Visual C++ website is at [http://msdn.microsoft.com/en-us/visualc/default.aspx http://msdn.microsoft.com/en-us/visualc/default.aspx].

Code::Blocks will work with any edition of Visual C++ since the 2003 edition (MSVC 7.1). The commercial editions of Visual Studio may require additional configuration in Code::Blocks to work correctly. You can also download the most recent "Express" edition of Visual C++ for free from [http://www.microsoft.com/express/vc/ microsoft.com/express/vc]. If you choose an "Express" edition of Visual C++, it is highly recommended that you also install Microsoft's Platform SDK in order to develop programs for Windows.

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

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

=== Intel C++ Compiler ===
Please note that on Windows platform, Intel C/C++ compiler requires ''Microsoft Visual C++[http://www.microsoft.com/express/download/offline.aspx]'' to be present in your system in order to function properly. It will not compile any C++ program without it. You should also note that ''Windows SDK[http://www.microsoft.com/downloads/details.aspx?FamilyID=e6e1c3df-a74f-4207-8586-711ebe331cdc&DisplayLang=en]'' shall be installed in order to compile Windows app.

Code::Blocks (C::B) is now able to detect (from svn revision 4967 onwards) Intel C/C++ compiler and it'll then automatically setup the MSVC compiler so that the Intel compiler works as intended. However if you wish to manually install the Intel C/C++ compiler, then follow the following steps.

* Go to '''Settings > Compilers and debuggers''' and then select '''Intel C/C++ compiler'''.
* Click on the '''Toolchain executables''' tab. Point to the installation directory, e.g. <tt>C:\Program Files\Intel\Compiler\C++\10.1.020\IA32</tt> , inside the ''Compiler's installation directory'' textbox.
* Click on the '''Additional Paths''' tab and fill in the directories pointing to MSVC bin directory and the Windows SDK directory. It may look like-
C:\Program Files\Microsoft Visual Studio 8\VC\bin
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE
C:\Program Files\Microsoft SDKs\Windows\v6.0\bin
* Click on the '''Search directories''' tab and add the include directories containing headers offered by Intel C/C++ compiler, MSVC compiler and the Windows SDK headers to '''Compiler''' and '''Resource compiler'''. It may look like-
C:\Program Files\Intel\Compiler\C++\10.1.020\IA32\include
C:\Program Files\Microsoft Visual Studio 8\VC\include
C:\Program Files\Microsoft SDKs\Windows\v6.0\Include
* Click on the '''Linker''' tab under '''Search directories''' tab and add the directories containing libraries offered by Intel C/C++ compiler, MSVC compiler and the Windows SDK. It may look like-
C:\Program Files\Intel\Compiler\C++\10.1.020\IA32\lib
C:\Program Files\Microsoft Visual Studio 8\VC\lib
C:\Program Files\Microsoft SDKs\Windows\v6.0\Lib

Click on the '''OK''' button to save the settings. Now you should be able to use Intel C/C++ compilers on Windows with C::B.

Note: The directories specified above may be different on your PC.

== Linux ==

At the time of this writing, Code::Blocks supports the following compilers in Linux:
* [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.''

== Remote Compilation ==
Remote compilation is not directly supported by Code::Blocks, however, the following articles explain two remote compilation systems, which use 3rd party programs to provide this funcionality:

[[Installing Uniwin remote compiler]] 
[[Using Xming for remote compilation]]

BoostWindowsQuickRef

2010-02-12T02:40:20Z

Seronis: /* Include Boost headers and link with Boost libraries */

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up Boost with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

'''Important Requirements:'''
* '''Windows compiler''' - You need to have correctly installed the free [http://www.mingw.org/ MinGW/GCC] compiler or one of [http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]). The [https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled version which includes all necessary packages; or, if you install it by hand, you need at least the gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages. Also, ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5#windows the latest stable release] or [/index.php/board,20.0.html a recent nightly build].

== Download Boost ==
You can download the Boost source code and compile it yourself, or, ''only if you are using MSVC 2003 (7.1) or later'', you can use a web-based installer to download pre-built libraries.

=== Boost Source Code ===
The Boost libraries are distributed as source code archived in .7z, .tar.bz2, .tar.gz, or .zip format; choose whichever archive format is easiest for you to unpack. The current stable release of Boost is '''1.42.0'''. [http://www.boost.org/users/news/version_1_42_0 Click here to browse the Boost 1.42.0 version info and files]. You can check the Boost home page at [http://www.boost.org/ boost.org] to see if a newer stable version is available.

You also need to download Boost Jam in order to build Boost. The current stable release of Boost Jam is '''3.1.17'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.17-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.17-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack both archives to paths without spaces.''' You should choose a volume with at least 1.5 GB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_42_0" and "<path>\boost-jam-3.1.17-1-ntx86".

=== Boost Installer for MSVC 2003 (7.1) or later ===
BoostPro Computing distributes a free web-based installer that will download and install prebuilt versions of the Boost libraries for MSVC. [http://www.boostpro.com/products/free Click here to browse the BoostPro Free Downloads]. The amount of space used by the installation varies depending on which libraries and variants you choose.

== Build Boost ==
''This step is unnecessary if you are using the '''BoostPro installer''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Ensure that Boost Jam is in the PATH environment variable (where <path> is the path you unpacked Boost Jam to):
set PATH=<path>\boost-jam-3.1.17-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_42_0
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is (where <installpath> is where you want the Boost headers and libraries; typically C:\Program Files\CodeBlocks):
bjam --toolset=gcc "--prefix=<installpath>" install
* The recommended command to use for '''MSVC''' is (where <installpath> is where you want the Boost headers and libraries):
bjam --toolset=msvc "--prefix=<installpath>" install
* This step will generally take 5-20 minutes, depending on the capabilities of your PC.
* The above commands will build release, multithreaded, DLL versions of the Boost libraries. If you want other variants, add --build-type=complete to the command line. This will take a much longer amount of time to build.

== Add Boost to an existing project in Code::Blocks ==
The Boost libraries are usable in nearly any Code::Blocks project. You can create a new project that will use Boost or open an existing project. With your project open, perform these steps.

=== Set up a Code::Blocks global variable for Boost ===
This step only needs to be performed once, after which the global variable you've created will be available for any project.
* Open the Settings menu and select "Global variables..."
* Click the "New" button next to the Current variable list, specify a name like "boost", and hit OK
* In the "base" field of the Builtin fields section, browse for the base of your Boost installation -- the path you specified in the --prefix option of the build command
* In the "include" field, browse for the "include\boost-1_42" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_42" tacked on.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
* Right-click your project's name in the Projects section of the Management window and select "Build options..."
* Highlight the root of your project in the tree on the left side of the Project build options window
* Select the "Search directories" tab
* With the "Compiler" subtab selected, click the Add button, enter "$(#boost.include)" (without the quotes), and hit OK
''If you are using the bundled version of MinGW with Code::Blocks, and you used your C::B installation in the --prefix option as recommended, the following step is unnecessary''
* With the "Linker" subtab selected, click the Add button, enter "$(#boost.lib)" (without the quotes), and hit OK

=== Include Boost headers and link with Boost libraries ===
Your project is now ready to use the Boost libraries. For each library you want to use, do the following:
* #include <boost/*.hpp> in your source file
* In your project's build options, highlight the root of your project, select the "Linker settings" tab, and add "boost_*-mgwXX-mt-1_42" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw44-mt-1_42" and "boost_system-mgw44-mt-1_42" to use boost.filesystem.

== Test boost installation==
After the installation, you can use these [http://beans.seartipy.com/2006/03/16/how-to-test-c-boost-installation/ two examples] to test whether your boost installation and the configuration of your Code::Blocks are successful.

== Frequently Asked Questions ==

'''Do I need to link with a library for every Boost component I use?'''

No. Only some of the Boost components require pre-compilation and additional linked-in code. You can even skip building Boost altogether, if you'll only need components without a link-time library. If you want to know whether a specific component requires a pre-built library, just try including the header(s) without making any linker additions. If you get undefined reference errors, you'll need to add the component's library.

BoostWindowsQuickRef

2010-02-12T02:39:51Z

Seronis: /* Set up a Code::Blocks global variable for Boost */

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up Boost with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

'''Important Requirements:'''
* '''Windows compiler''' - You need to have correctly installed the free [http://www.mingw.org/ MinGW/GCC] compiler or one of [http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]). The [https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled version which includes all necessary packages; or, if you install it by hand, you need at least the gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages. Also, ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5#windows the latest stable release] or [/index.php/board,20.0.html a recent nightly build].

== Download Boost ==
You can download the Boost source code and compile it yourself, or, ''only if you are using MSVC 2003 (7.1) or later'', you can use a web-based installer to download pre-built libraries.

=== Boost Source Code ===
The Boost libraries are distributed as source code archived in .7z, .tar.bz2, .tar.gz, or .zip format; choose whichever archive format is easiest for you to unpack. The current stable release of Boost is '''1.42.0'''. [http://www.boost.org/users/news/version_1_42_0 Click here to browse the Boost 1.42.0 version info and files]. You can check the Boost home page at [http://www.boost.org/ boost.org] to see if a newer stable version is available.

You also need to download Boost Jam in order to build Boost. The current stable release of Boost Jam is '''3.1.17'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.17-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.17-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack both archives to paths without spaces.''' You should choose a volume with at least 1.5 GB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_42_0" and "<path>\boost-jam-3.1.17-1-ntx86".

=== Boost Installer for MSVC 2003 (7.1) or later ===
BoostPro Computing distributes a free web-based installer that will download and install prebuilt versions of the Boost libraries for MSVC. [http://www.boostpro.com/products/free Click here to browse the BoostPro Free Downloads]. The amount of space used by the installation varies depending on which libraries and variants you choose.

== Build Boost ==
''This step is unnecessary if you are using the '''BoostPro installer''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Ensure that Boost Jam is in the PATH environment variable (where <path> is the path you unpacked Boost Jam to):
set PATH=<path>\boost-jam-3.1.17-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_42_0
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is (where <installpath> is where you want the Boost headers and libraries; typically C:\Program Files\CodeBlocks):
bjam --toolset=gcc "--prefix=<installpath>" install
* The recommended command to use for '''MSVC''' is (where <installpath> is where you want the Boost headers and libraries):
bjam --toolset=msvc "--prefix=<installpath>" install
* This step will generally take 5-20 minutes, depending on the capabilities of your PC.
* The above commands will build release, multithreaded, DLL versions of the Boost libraries. If you want other variants, add --build-type=complete to the command line. This will take a much longer amount of time to build.

== Add Boost to an existing project in Code::Blocks ==
The Boost libraries are usable in nearly any Code::Blocks project. You can create a new project that will use Boost or open an existing project. With your project open, perform these steps.

=== Set up a Code::Blocks global variable for Boost ===
This step only needs to be performed once, after which the global variable you've created will be available for any project.
* Open the Settings menu and select "Global variables..."
* Click the "New" button next to the Current variable list, specify a name like "boost", and hit OK
* In the "base" field of the Builtin fields section, browse for the base of your Boost installation -- the path you specified in the --prefix option of the build command
* In the "include" field, browse for the "include\boost-1_42" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_42" tacked on.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
* Right-click your project's name in the Projects section of the Management window and select "Build options..."
* Highlight the root of your project in the tree on the left side of the Project build options window
* Select the "Search directories" tab
* With the "Compiler" subtab selected, click the Add button, enter "$(#boost.include)" (without the quotes), and hit OK
''If you are using the bundled version of MinGW with Code::Blocks, and you used your C::B installation in the --prefix option as recommended, the following step is unnecessary''
* With the "Linker" subtab selected, click the Add button, enter "$(#boost.lib)" (without the quotes), and hit OK

=== Include Boost headers and link with Boost libraries ===
Your project is now ready to use the Boost libraries. For each library you want to use, do the following:
* #include <boost/*.hpp> in your source file
* In your project's build options, highlight the root of your project, select the "Linker settings" tab, and add "boost_*-mgwXX-mt-1_40" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw44-mt-1_40" and "boost_system-mgw44-mt-1_40" to use boost.filesystem.

== Test boost installation==
After the installation, you can use these [http://beans.seartipy.com/2006/03/16/how-to-test-c-boost-installation/ two examples] to test whether your boost installation and the configuration of your Code::Blocks are successful.

== Frequently Asked Questions ==

'''Do I need to link with a library for every Boost component I use?'''

No. Only some of the Boost components require pre-compilation and additional linked-in code. You can even skip building Boost altogether, if you'll only need components without a link-time library. If you want to know whether a specific component requires a pre-built library, just try including the header(s) without making any linker additions. If you get undefined reference errors, you'll need to add the component's library.

BoostWindowsQuickRef

2010-02-12T02:39:25Z

Seronis: /* Build Boost */

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up Boost with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

'''Important Requirements:'''
* '''Windows compiler''' - You need to have correctly installed the free [http://www.mingw.org/ MinGW/GCC] compiler or one of [http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]). The [https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled version which includes all necessary packages; or, if you install it by hand, you need at least the gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages. Also, ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5#windows the latest stable release] or [/index.php/board,20.0.html a recent nightly build].

== Download Boost ==
You can download the Boost source code and compile it yourself, or, ''only if you are using MSVC 2003 (7.1) or later'', you can use a web-based installer to download pre-built libraries.

=== Boost Source Code ===
The Boost libraries are distributed as source code archived in .7z, .tar.bz2, .tar.gz, or .zip format; choose whichever archive format is easiest for you to unpack. The current stable release of Boost is '''1.42.0'''. [http://www.boost.org/users/news/version_1_42_0 Click here to browse the Boost 1.42.0 version info and files]. You can check the Boost home page at [http://www.boost.org/ boost.org] to see if a newer stable version is available.

You also need to download Boost Jam in order to build Boost. The current stable release of Boost Jam is '''3.1.17'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.17-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.17-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack both archives to paths without spaces.''' You should choose a volume with at least 1.5 GB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_42_0" and "<path>\boost-jam-3.1.17-1-ntx86".

=== Boost Installer for MSVC 2003 (7.1) or later ===
BoostPro Computing distributes a free web-based installer that will download and install prebuilt versions of the Boost libraries for MSVC. [http://www.boostpro.com/products/free Click here to browse the BoostPro Free Downloads]. The amount of space used by the installation varies depending on which libraries and variants you choose.

== Build Boost ==
''This step is unnecessary if you are using the '''BoostPro installer''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Ensure that Boost Jam is in the PATH environment variable (where <path> is the path you unpacked Boost Jam to):
set PATH=<path>\boost-jam-3.1.17-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_42_0
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is (where <installpath> is where you want the Boost headers and libraries; typically C:\Program Files\CodeBlocks):
bjam --toolset=gcc "--prefix=<installpath>" install
* The recommended command to use for '''MSVC''' is (where <installpath> is where you want the Boost headers and libraries):
bjam --toolset=msvc "--prefix=<installpath>" install
* This step will generally take 5-20 minutes, depending on the capabilities of your PC.
* The above commands will build release, multithreaded, DLL versions of the Boost libraries. If you want other variants, add --build-type=complete to the command line. This will take a much longer amount of time to build.

== Add Boost to an existing project in Code::Blocks ==
The Boost libraries are usable in nearly any Code::Blocks project. You can create a new project that will use Boost or open an existing project. With your project open, perform these steps.

=== Set up a Code::Blocks global variable for Boost ===
This step only needs to be performed once, after which the global variable you've created will be available for any project.
* Open the Settings menu and select "Global variables..."
* Click the "New" button next to the Current variable list, specify a name like "boost", and hit OK
* In the "base" field of the Builtin fields section, browse for the base of your Boost installation -- the path you specified in the --prefix option of the build command
* In the "include" field, browse for the "include\boost-1_40" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_40" tacked on.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
* Right-click your project's name in the Projects section of the Management window and select "Build options..."
* Highlight the root of your project in the tree on the left side of the Project build options window
* Select the "Search directories" tab
* With the "Compiler" subtab selected, click the Add button, enter "$(#boost.include)" (without the quotes), and hit OK
''If you are using the bundled version of MinGW with Code::Blocks, and you used your C::B installation in the --prefix option as recommended, the following step is unnecessary''
* With the "Linker" subtab selected, click the Add button, enter "$(#boost.lib)" (without the quotes), and hit OK

=== Include Boost headers and link with Boost libraries ===
Your project is now ready to use the Boost libraries. For each library you want to use, do the following:
* #include <boost/*.hpp> in your source file
* In your project's build options, highlight the root of your project, select the "Linker settings" tab, and add "boost_*-mgwXX-mt-1_40" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw44-mt-1_40" and "boost_system-mgw44-mt-1_40" to use boost.filesystem.

== Test boost installation==
After the installation, you can use these [http://beans.seartipy.com/2006/03/16/how-to-test-c-boost-installation/ two examples] to test whether your boost installation and the configuration of your Code::Blocks are successful.

== Frequently Asked Questions ==

'''Do I need to link with a library for every Boost component I use?'''

No. Only some of the Boost components require pre-compilation and additional linked-in code. You can even skip building Boost altogether, if you'll only need components without a link-time library. If you want to know whether a specific component requires a pre-built library, just try including the header(s) without making any linker additions. If you get undefined reference errors, you'll need to add the component's library.

BoostWindowsQuickRef

2010-02-12T02:38:36Z

Seronis: /* Boost Source Code */

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up Boost with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

'''Important Requirements:'''
* '''Windows compiler''' - You need to have correctly installed the free [http://www.mingw.org/ MinGW/GCC] compiler or one of [http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]). The [https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled version which includes all necessary packages; or, if you install it by hand, you need at least the gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages. Also, ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5#windows the latest stable release] or [/index.php/board,20.0.html a recent nightly build].

== Download Boost ==
You can download the Boost source code and compile it yourself, or, ''only if you are using MSVC 2003 (7.1) or later'', you can use a web-based installer to download pre-built libraries.

=== Boost Source Code ===
The Boost libraries are distributed as source code archived in .7z, .tar.bz2, .tar.gz, or .zip format; choose whichever archive format is easiest for you to unpack. The current stable release of Boost is '''1.42.0'''. [http://www.boost.org/users/news/version_1_42_0 Click here to browse the Boost 1.42.0 version info and files]. You can check the Boost home page at [http://www.boost.org/ boost.org] to see if a newer stable version is available.

You also need to download Boost Jam in order to build Boost. The current stable release of Boost Jam is '''3.1.17'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.17-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.17-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack both archives to paths without spaces.''' You should choose a volume with at least 1.5 GB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_42_0" and "<path>\boost-jam-3.1.17-1-ntx86".

=== Boost Installer for MSVC 2003 (7.1) or later ===
BoostPro Computing distributes a free web-based installer that will download and install prebuilt versions of the Boost libraries for MSVC. [http://www.boostpro.com/products/free Click here to browse the BoostPro Free Downloads]. The amount of space used by the installation varies depending on which libraries and variants you choose.

== Build Boost ==
''This step is unnecessary if you are using the '''BoostPro installer''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Ensure that Boost Jam is in the PATH environment variable (where <path> is the path you unpacked Boost Jam to):
set PATH=<path>\boost-jam-3.1.17-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_40_0
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is (where <installpath> is where you want the Boost headers and libraries; typically C:\Program Files\CodeBlocks):
bjam --toolset=gcc "--prefix=<installpath>" install
* The recommended command to use for '''MSVC''' is (where <installpath> is where you want the Boost headers and libraries):
bjam --toolset=msvc "--prefix=<installpath>" install
* This step will generally take 5-20 minutes, depending on the capabilities of your PC.
* The above commands will build release, multithreaded, DLL versions of the Boost libraries. If you want other variants, add --build-type=complete to the command line. This will take a much longer amount of time to build.

== Add Boost to an existing project in Code::Blocks ==
The Boost libraries are usable in nearly any Code::Blocks project. You can create a new project that will use Boost or open an existing project. With your project open, perform these steps.

=== Set up a Code::Blocks global variable for Boost ===
This step only needs to be performed once, after which the global variable you've created will be available for any project.
* Open the Settings menu and select "Global variables..."
* Click the "New" button next to the Current variable list, specify a name like "boost", and hit OK
* In the "base" field of the Builtin fields section, browse for the base of your Boost installation -- the path you specified in the --prefix option of the build command
* In the "include" field, browse for the "include\boost-1_40" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_40" tacked on.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
* Right-click your project's name in the Projects section of the Management window and select "Build options..."
* Highlight the root of your project in the tree on the left side of the Project build options window
* Select the "Search directories" tab
* With the "Compiler" subtab selected, click the Add button, enter "$(#boost.include)" (without the quotes), and hit OK
''If you are using the bundled version of MinGW with Code::Blocks, and you used your C::B installation in the --prefix option as recommended, the following step is unnecessary''
* With the "Linker" subtab selected, click the Add button, enter "$(#boost.lib)" (without the quotes), and hit OK

=== Include Boost headers and link with Boost libraries ===
Your project is now ready to use the Boost libraries. For each library you want to use, do the following:
* #include <boost/*.hpp> in your source file
* In your project's build options, highlight the root of your project, select the "Linker settings" tab, and add "boost_*-mgwXX-mt-1_40" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw44-mt-1_40" and "boost_system-mgw44-mt-1_40" to use boost.filesystem.

== Test boost installation==
After the installation, you can use these [http://beans.seartipy.com/2006/03/16/how-to-test-c-boost-installation/ two examples] to test whether your boost installation and the configuration of your Code::Blocks are successful.

== Frequently Asked Questions ==

'''Do I need to link with a library for every Boost component I use?'''

No. Only some of the Boost components require pre-compilation and additional linked-in code. You can even skip building Boost altogether, if you'll only need components without a link-time library. If you want to know whether a specific component requires a pre-built library, just try including the header(s) without making any linker additions. If you get undefined reference errors, you'll need to add the component's library.

Installing Code::Blocks nightly build on Windows

2010-02-10T03:51:44Z

Seronis: /* Examples */

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks nightly build]]
This article describes how to install a nightly build of ''Code::Blocks''.

:''NOTE'': If you have installed ''Code::Blocks'' RC1, RC1-1, or RC2; please either uninstall it or make sure you use a different directory. '''Do not''' install the nightly build on top of these release candidates.

=== Install steps ===

# [[MinGW_installation|Install ''MinGW'' and the ''GDB debugger'']].
# Download and install [http://www.7-zip.org/ 7-Zip]. You need it to extract the nightly build.
# Download the latest nightly build from the [/index.php?board=20.0 Nightly Builds forum].
# Download the according ''wxWidgets Unicode DLL'' for your nightly build (download link in forum).
# Download the ''mingw10.dll'' for ''Code::Blocks'' [http://download.berlios.de/codeblocks/mingwm10.7z mingwm10.7z] (also mentioned at the nightly build).
#* This step is optional if the bin directory of ''MinGW'' is in your PATH variable '''or''' if you copy ''mingw10.dll'' from <tt>…\"MinGW"\bin</tt> directory to your unzip-directory of ''Code::Blocks'' an ''wxWidgets DLL''.
# Unzip ''Code::Blocks'' and the ''wxWidgets DLL'' to the same directory.
# Start ''Code::Blocks'' and configure ''GNU GCC compiler''.

=== Examples ===
Downloads for one Nightly Install from 2010.01.16 see [/index.php/topic,11875.0.html Nightly Builds forum (build 6088)]:
[http://sourceforge.net/projects/tdm-gcc/files/TDM-MinGW%20Installer/1.908.0/tdm-mingw-1.908.0-4.4.1-2.exe/download TDM MinGW v4.4.1-2]
Note: The GDB debugger is also handled with the previously linked installer and doesnt require a seperate download.
[http://prdownload.berlios.de/codeblocks/CB_20100116_rev6088_win32.7z CB_20100116_rev6088_win32.7z]
[http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2810.7z wxmsw28u_gcc_cb_wx2810.7z]

Downloads for one Nightly Install from 2007.08.16 see [/index.php/topic,6705.0.html Nightly Builds forum (build 4399)]:
[http://prdownloads.sf.net/mingw/MinGW-5.1.3.exe MinGW-5.1.3.exe]
[http://prdownloads.sf.net/mingw/gdb-6.6.tar.bz2 gdb-6.6.tar.bz2]
Note: If you don't install to C:\MinGW you have to change the 5 path entries inside
''Code::Blocks'' under settings->compiler and debugger.
[http://prdownload.berlios.de/codeblocks/mingwm10.7z mingwm10.7z]
[http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx284.7z wxmsw28u_gcc_cb_wx284.7z]
[http://prdownload.berlios.de/codeblocks/CB_20070816_rev4399_win32.7z CB_20070816_rev4399_win32.7z]

Downloads for one Nightly Install from 2006.08.26 (build 2910):
[http://prdownloads.sf.net/mingw/MinGW-5.1.3.exe MinGW-5.1.3.exe]
[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe gdb-6.3-2.exe]
Note: If you don't install to C:\MinGW you have to change the 5 path entries inside
Code::Blocks under settings->compiler and debugger.
[http://download.berlios.de/codeblocks/mingwm10.7z mingwm10.7z]
[http://download.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3p2.7z wxmsw26u_gcc_cb_wx2.6.3p2.7z]
[http://download.berlios.de/codeblocks/CB_20060826_rev2910_win32.7z CB_20060826_rev2910_win32.7z]

Installing Code::Blocks from source on Windows

2010-02-09T14:09:08Z

Seronis: /* wxWidgets */

[[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 GCC 4.4.1]

=== wxWidgets ===

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

Code::Blocks uses
* 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 [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...".

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

== 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:
<pre>
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
</pre>
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 ===
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> 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 [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 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.

Installing Code::Blocks from source on Windows

2010-02-09T14:04:57Z

Seronis: /* MinGW compiler */

[[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 GCC 4.4.1]

=== wxWidgets ===

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

Code::Blocks uses
* 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 [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...".

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

== 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:
<pre>
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
</pre>
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 ===
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> 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 [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 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.

Using Allegro with Code::Blocks

2009-09-17T22:19:59Z

Seronis:

[[Category:User Documentation]]

==What is Allegro==
<blockquote>"Allegro is a game programming library for C/C++ developers distributed freely, supporting the following platforms: DOS, Unix (Linux, FreeBSD, Irix, Solaris, Darwin), Windows, QNX, BeOS and MacOS X. It provides many functions for graphics, sounds, player input (keyboard, mouse and joystick) and timers. It also provides fixed and floating point mathematical functions, 3d functions, file management functions, compressed datafile and a GUI. Read more details on the introductory page."</blockquote>

'''Important Links:'''
* '''[http://alleg.sourceforge.net/readme.html Official Site]''' - Readme / Introduction
* '''[http://alleg.sourceforge.net/wip.html Download]''' - Stable and Developement branches
* '''[http://wiki.allegro.cc/index.php?title=Getting_Started Getting Started]''' - Unofficial wiki with information on how to set up many popular IDEs for use with Allegro

==Important Note==
<blockquote>The links provided here are for convenience only. For any problems compiling, installing and using allegro, the right place to ask is [http://www.allegro.cc/ THEIR FORUMS].</blockquote>

User documentation

2009-09-06T17:32:04Z

Seronis: /* Third-party libraries */

[[Category:Code::Blocks Documentation]]
[[Category:User Documentation]]
== Official user document ==
The Official Code::Blocks user document can be found [https://www.codeblocks.org/user-manual here]

== Articles for Code::Blocks users ==

'''[[Installing Code::Blocks]]'''

:How to install Code::Blocks (from binary or source)

'''[[Keyboard Shortcuts]]'''

:List of keyboard shortcuts that can be used in Code::Blocks

'''[[Command line arguments]]'''

:List of command-line arguments that can be used with Code::Blocks.

'''[[Personalities]]'''

:Customize the Code::Blocks user interface for different workflows.

'''[[Code::Blocks Plugins]]'''

:List of plugins that come with Code::Blocks.

'''[[The build process of Code::Blocks]]'''

:Information about how Code::Blocks actually builds your source code.

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

'''[[wxSmith tutorials]]'''
:Information about how to use wxSmith RAD editor

'''[[Building an Non-Unicode Win32 Code::Blocks]]'''
:Information about how to modify the Code::Blocks project files for an Non-Unicode build of Code::Blocks.

'''[[Miscellaneous]]'''
:Miscellaneous things related to the user development experience. This is a catch all place.

== Application development ==

* [[Builtin variables]]
* [[Recommended global variables]]
* [[Code::Blocks variable types synthesis]]
* [[Debugging with Code::Blocks]]
* [[Adding support for non C/C++ files to the build system]]

== Compilers ==

* [[Global compiler variables]]
* [[Precompiled headers]]
* [[Installing a supported compiler]]
* [[Installing Cygwin Compiler]]
* [[Installing Fortran Compiler]]
* [[Installing Uniwin remote compiler]]
* [[Code::Blocks_and_Cross_Compilers|Using cross compilers]]
* [[Cross_Compiling_wxWidgets_Applications_on_Linux|Cross compiling wxWidgets applications on Linux]]
* [[Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE]]
* [[Integrating Microsoft Visual C 6 with Code::Blocks IDE]]
* [[64Bit Windows|Setting up for 64-bit windows development with Mirosoft compilers]]
* [[Using the Code::Blocks IDE with SDCC on PIC MCUs]]
* [[Using Code::Blocks with Open Watcom]]

== User interface development ==

* [[WxSmith Tutorial & Pointers|Creating a dialog for wxWidgets with wxSmith]]

== Third-party libraries ==

* [[BoostWindowsQuickRef|Using Boost with Code::Blocks (Windows)]]
* [[WxWindowsQuickRef|Using wxWidgets with Code::Blocks (Windows)]]
* [[Using SDL with Code::Blocks]]
* [[Using GLFW with Code::Blocks]]
* [[Using Allegro with Code::Blocks]]

== Third-party Applications ==

* [[KiCadBuildQuickRef|How-to build KiCad with Code::Blocks]]

Using Allegro with Code::Blocks

2009-09-06T17:30:46Z

Seronis: New page: Category:User Documentation ==What is Allegro== <blockquote>"Allegro is a game programming library for C/C++ developers distributed freely, supporting the following platforms: DOS, Un...

BoostWindowsQuickRef

2009-07-26T19:26:00Z

Seronis: /* Include Boost headers and link with Boost libraries */

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up Boost with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

'''Important Requirements:'''
* '''Windows compiler''' - You need to have correctly installed the free [http://www.mingw.org/ MinGW/GCC] compiler or one of [http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]). The [https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled version which includes all necessary packages; or, if you install it by hand, you need at least the gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages. Also, ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5#windows the latest stable release] or [/index.php/board,20.0.html a recent nightly build].

== Download Boost ==
You can download the Boost source code and compile it yourself, or, ''only if you are using MSVC 2003 (7.1) or later'', you can use a web-based installer to download pre-built libraries.

=== Boost Source Code ===
The Boost libraries are distributed as source code archived in .7z, .tar.bz2, .tar.gz, or .zip format; choose whichever archive format is easiest for you to unpack. The current stable release of Boost is '''1.39.0'''. [http://sourceforge.net/projects/boost/files/ Click here to browse the Boost 1.39.0 downloadable files] (26.6 MB). You can check [http://www.boost.org/users/download/ the Boost download page] to see if a newer stable version is available.

You also need to download Boost Jam in order to build Boost. The current stable release of Boost Jam is '''3.1.17'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.17-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.17-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack both archives to paths without spaces.''' You should choose a volume with at least 1.4 GB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_39_0" and "<path>\boost-jam-3.1.17-1-ntx86".

=== Boost Installer for MSVC 2003 (7.1) or later ===
BoostPro Computing distributes a free web-based installer that will download and install prebuilt versions of the Boost libraries for MSVC. [http://www.boostpro.com/products/free Click here to browse the BoostPro Free Downloads]. The amount of space used by the installation varies depending on which libraries and variants you choose.

== Build Boost ==
''This step is unnecessary if you are using the '''BoostPro installer''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Ensure that Boost Jam is in the PATH environment variable (where <path> is the path you unpacked Boost Jam to):
set PATH=<path>\boost-jam-3.1.17-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_39_0
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is (where <installpath> is where you want the Boost headers and libraries; typically C:\Program Files\CodeBlocks):
bjam --toolset=gcc "--prefix=<installpath>" install
* The recommended command to use for '''MSVC''' is (where <installpath> is where you want the Boost headers and libraries):
bjam --toolset=msvc "--prefix=<installpath>" install
* This step will generally take 5-20 minutes, depending on the capabilities of your PC.
* The above commands will build release, multithreaded, DLL versions of the Boost libraries. If you want other variants, add --build-type=complete to the command line. This will take a much longer amount of time to build.

== Add Boost to an existing project in Code::Blocks ==
The Boost libraries are usable in nearly any Code::Blocks project. You can create a new project that will use Boost or open an existing project. With your project open, perform these steps.

=== Set up a Code::Blocks global variable for Boost ===
This step only needs to be performed once, after which the global variable you've created will be available for any project.
* Open the Settings menu and select "Global variables..."
* Click the "New" button next to the Current variable list, specify a name like "boost", and hit OK
* In the "base" field of the Builtin fields section, browse for the base of your Boost installation -- the path you specified in the --prefix option of the build command
* In the "include" field, browse for the "include\boost-1_39" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_39" tacked on.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
* Right-click your project's name in the Projects section of the Management window and select "Build options..."
* Highlight the root of your project in the tree on the left side of the Project build options window
* Select the "Search directories" tab
* With the "Compiler" subtab selected, click the Add button, enter "$(#boost.include)" (without the quotes), and hit OK
''If you are using the bundled version of MinGW with Code::Blocks, and you used your C::B installation in the --prefix option as recommended, the following step is unnecessary''
* With the "Linker" subtab selected, click the Add button, enter "$(#boost.lib)" (without the quotes), and hit OK

=== Include Boost headers and link with Boost libraries ===
Your project is now ready to use the Boost libraries. For each library you want to use, do the following:
* #include <boost/*.hpp> in your source file
* In your project's build options, highlight the root of your project, select the "Linker settings" tab, and add "boost_*-mgw44-mt-1_39" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw44-mt-1_39.lib" and "boost_system-mgw44-mt-1_39.lib" to use boost.filesystem.

== Test boost installation==
After the installation, you can use these [http://beans.seartipy.com/2006/03/16/how-to-test-c-boost-installation/ two examples] to test whether your boost installation and the configuration of your Code::Blocks are successful.

== Frequently Asked Questions ==

No Frequently Asked Questions (or Frequently Given Answers) have been entered yet.

BoostWindowsQuickRef

2009-07-26T19:24:00Z

Seronis: /* Set up a Code::Blocks global variable for Boost */

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up Boost with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

'''Important Requirements:'''
* '''Windows compiler''' - You need to have correctly installed the free [http://www.mingw.org/ MinGW/GCC] compiler or one of [http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]). The [https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled version which includes all necessary packages; or, if you install it by hand, you need at least the gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages. Also, ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5#windows the latest stable release] or [/index.php/board,20.0.html a recent nightly build].

== Download Boost ==
You can download the Boost source code and compile it yourself, or, ''only if you are using MSVC 2003 (7.1) or later'', you can use a web-based installer to download pre-built libraries.

=== Boost Source Code ===
The Boost libraries are distributed as source code archived in .7z, .tar.bz2, .tar.gz, or .zip format; choose whichever archive format is easiest for you to unpack. The current stable release of Boost is '''1.39.0'''. [http://sourceforge.net/projects/boost/files/ Click here to browse the Boost 1.39.0 downloadable files] (26.6 MB). You can check [http://www.boost.org/users/download/ the Boost download page] to see if a newer stable version is available.

You also need to download Boost Jam in order to build Boost. The current stable release of Boost Jam is '''3.1.17'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.17-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.17-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack both archives to paths without spaces.''' You should choose a volume with at least 1.4 GB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_39_0" and "<path>\boost-jam-3.1.17-1-ntx86".

=== Boost Installer for MSVC 2003 (7.1) or later ===
BoostPro Computing distributes a free web-based installer that will download and install prebuilt versions of the Boost libraries for MSVC. [http://www.boostpro.com/products/free Click here to browse the BoostPro Free Downloads]. The amount of space used by the installation varies depending on which libraries and variants you choose.

== Build Boost ==
''This step is unnecessary if you are using the '''BoostPro installer''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Ensure that Boost Jam is in the PATH environment variable (where <path> is the path you unpacked Boost Jam to):
set PATH=<path>\boost-jam-3.1.17-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_39_0
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is (where <installpath> is where you want the Boost headers and libraries; typically C:\Program Files\CodeBlocks):
bjam --toolset=gcc "--prefix=<installpath>" install
* The recommended command to use for '''MSVC''' is (where <installpath> is where you want the Boost headers and libraries):
bjam --toolset=msvc "--prefix=<installpath>" install
* This step will generally take 5-20 minutes, depending on the capabilities of your PC.
* The above commands will build release, multithreaded, DLL versions of the Boost libraries. If you want other variants, add --build-type=complete to the command line. This will take a much longer amount of time to build.

== Add Boost to an existing project in Code::Blocks ==
The Boost libraries are usable in nearly any Code::Blocks project. You can create a new project that will use Boost or open an existing project. With your project open, perform these steps.

=== Set up a Code::Blocks global variable for Boost ===
This step only needs to be performed once, after which the global variable you've created will be available for any project.
* Open the Settings menu and select "Global variables..."
* Click the "New" button next to the Current variable list, specify a name like "boost", and hit OK
* In the "base" field of the Builtin fields section, browse for the base of your Boost installation -- the path you specified in the --prefix option of the build command
* In the "include" field, browse for the "include\boost-1_39" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_39" tacked on.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
* Right-click your project's name in the Projects section of the Management window and select "Build options..."
* Highlight the root of your project in the tree on the left side of the Project build options window
* Select the "Search directories" tab
* With the "Compiler" subtab selected, click the Add button, enter "$(#boost.include)" (without the quotes), and hit OK
''If you are using the bundled version of MinGW with Code::Blocks, and you used your C::B installation in the --prefix option as recommended, the following step is unnecessary''
* With the "Linker" subtab selected, click the Add button, enter "$(#boost.lib)" (without the quotes), and hit OK

=== Include Boost headers and link with Boost libraries ===
Your project is now ready to use the Boost libraries. For each library you want to use, do the following:
* #include <boost/*.hpp> in your source file
* In your project's build options, highlight the root of your project, select the "Linker settings" tab, and add "boost_*-mgw34-mt-1_37" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw34-mt-1_37.lib" and "boost_system-mgw34-mt-1_37.lib" to use boost.filesystem.

== Test boost installation==
After the installation, you can use these [http://beans.seartipy.com/2006/03/16/how-to-test-c-boost-installation/ two examples] to test whether your boost installation and the configuration of your Code::Blocks are successful.

== Frequently Asked Questions ==

No Frequently Asked Questions (or Frequently Given Answers) have been entered yet.

BoostWindowsQuickRef

2009-07-26T19:22:42Z

Seronis: /* Build Boost */

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up Boost with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

'''Important Requirements:'''
* '''Windows compiler''' - You need to have correctly installed the free [http://www.mingw.org/ MinGW/GCC] compiler or one of [http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]). The [https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled version which includes all necessary packages; or, if you install it by hand, you need at least the gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages. Also, ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5#windows the latest stable release] or [/index.php/board,20.0.html a recent nightly build].

== Download Boost ==
You can download the Boost source code and compile it yourself, or, ''only if you are using MSVC 2003 (7.1) or later'', you can use a web-based installer to download pre-built libraries.

=== Boost Source Code ===
The Boost libraries are distributed as source code archived in .7z, .tar.bz2, .tar.gz, or .zip format; choose whichever archive format is easiest for you to unpack. The current stable release of Boost is '''1.39.0'''. [http://sourceforge.net/projects/boost/files/ Click here to browse the Boost 1.39.0 downloadable files] (26.6 MB). You can check [http://www.boost.org/users/download/ the Boost download page] to see if a newer stable version is available.

You also need to download Boost Jam in order to build Boost. The current stable release of Boost Jam is '''3.1.17'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.17-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.17-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack both archives to paths without spaces.''' You should choose a volume with at least 1.4 GB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_39_0" and "<path>\boost-jam-3.1.17-1-ntx86".

=== Boost Installer for MSVC 2003 (7.1) or later ===
BoostPro Computing distributes a free web-based installer that will download and install prebuilt versions of the Boost libraries for MSVC. [http://www.boostpro.com/products/free Click here to browse the BoostPro Free Downloads]. The amount of space used by the installation varies depending on which libraries and variants you choose.

== Build Boost ==
''This step is unnecessary if you are using the '''BoostPro installer''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Ensure that Boost Jam is in the PATH environment variable (where <path> is the path you unpacked Boost Jam to):
set PATH=<path>\boost-jam-3.1.17-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_39_0
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is (where <installpath> is where you want the Boost headers and libraries; typically C:\Program Files\CodeBlocks):
bjam --toolset=gcc "--prefix=<installpath>" install
* The recommended command to use for '''MSVC''' is (where <installpath> is where you want the Boost headers and libraries):
bjam --toolset=msvc "--prefix=<installpath>" install
* This step will generally take 5-20 minutes, depending on the capabilities of your PC.
* The above commands will build release, multithreaded, DLL versions of the Boost libraries. If you want other variants, add --build-type=complete to the command line. This will take a much longer amount of time to build.

== Add Boost to an existing project in Code::Blocks ==
The Boost libraries are usable in nearly any Code::Blocks project. You can create a new project that will use Boost or open an existing project. With your project open, perform these steps.

=== Set up a Code::Blocks global variable for Boost ===
This step only needs to be performed once, after which the global variable you've created will be available for any project.
* Open the Settings menu and select "Global variables..."
* Click the "New" button next to the Current variable list, specify a name like "boost", and hit OK
* In the "base" field of the Builtin fields section, browse for the base of your Boost installation -- the path you specified in the --prefix option of the build command
* In the "include" field, browse for the "include\boost-1_37" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_37" tacked on.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
* Right-click your project's name in the Projects section of the Management window and select "Build options..."
* Highlight the root of your project in the tree on the left side of the Project build options window
* Select the "Search directories" tab
* With the "Compiler" subtab selected, click the Add button, enter "$(#boost.include)" (without the quotes), and hit OK
''If you are using the bundled version of MinGW with Code::Blocks, and you used your C::B installation in the --prefix option as recommended, the following step is unnecessary''
* With the "Linker" subtab selected, click the Add button, enter "$(#boost.lib)" (without the quotes), and hit OK

=== Include Boost headers and link with Boost libraries ===
Your project is now ready to use the Boost libraries. For each library you want to use, do the following:
* #include <boost/*.hpp> in your source file
* In your project's build options, highlight the root of your project, select the "Linker settings" tab, and add "boost_*-mgw34-mt-1_37" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw34-mt-1_37.lib" and "boost_system-mgw34-mt-1_37.lib" to use boost.filesystem.

== Test boost installation==
After the installation, you can use these [http://beans.seartipy.com/2006/03/16/how-to-test-c-boost-installation/ two examples] to test whether your boost installation and the configuration of your Code::Blocks are successful.

== Frequently Asked Questions ==

No Frequently Asked Questions (or Frequently Given Answers) have been entered yet.

BoostWindowsQuickRef

2009-07-26T19:21:29Z

Seronis: /* Boost Source Code */

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up Boost with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

'''Important Requirements:'''
* '''Windows compiler''' - You need to have correctly installed the free [http://www.mingw.org/ MinGW/GCC] compiler or one of [http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]). The [https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled version which includes all necessary packages; or, if you install it by hand, you need at least the gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages. Also, ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5#windows the latest stable release] or [/index.php/board,20.0.html a recent nightly build].

== Download Boost ==
You can download the Boost source code and compile it yourself, or, ''only if you are using MSVC 2003 (7.1) or later'', you can use a web-based installer to download pre-built libraries.

=== Boost Source Code ===
The Boost libraries are distributed as source code archived in .7z, .tar.bz2, .tar.gz, or .zip format; choose whichever archive format is easiest for you to unpack. The current stable release of Boost is '''1.39.0'''. [http://sourceforge.net/projects/boost/files/ Click here to browse the Boost 1.39.0 downloadable files] (26.6 MB). You can check [http://www.boost.org/users/download/ the Boost download page] to see if a newer stable version is available.

You also need to download Boost Jam in order to build Boost. The current stable release of Boost Jam is '''3.1.17'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.17-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.17-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack both archives to paths without spaces.''' You should choose a volume with at least 1.4 GB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_39_0" and "<path>\boost-jam-3.1.17-1-ntx86".

=== Boost Installer for MSVC 2003 (7.1) or later ===
BoostPro Computing distributes a free web-based installer that will download and install prebuilt versions of the Boost libraries for MSVC. [http://www.boostpro.com/products/free Click here to browse the BoostPro Free Downloads]. The amount of space used by the installation varies depending on which libraries and variants you choose.

== Build Boost ==
''This step is unnecessary if you are using the '''BoostPro installer''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Ensure that Boost Jam is in the PATH environment variable (where <path> is the path you unpacked Boost Jam to):
set PATH=<path>\boost-jam-3.1.17-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_37_0
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is (where <installpath> is where you want the Boost headers and libraries; typically C:\Program Files\CodeBlocks):
bjam --toolset=gcc "--prefix=<installpath>" install
* The recommended command to use for '''MSVC''' is (where <installpath> is where you want the Boost headers and libraries):
bjam --toolset=msvc "--prefix=<installpath>" install
* This step will generally take 5-20 minutes, depending on the capabilities of your PC.
* The above commands will build release, multithreaded, DLL versions of the Boost libraries. If you want other variants, add --build-type=complete to the command line. This will take a much longer amount of time to build.

== Add Boost to an existing project in Code::Blocks ==
The Boost libraries are usable in nearly any Code::Blocks project. You can create a new project that will use Boost or open an existing project. With your project open, perform these steps.

=== Set up a Code::Blocks global variable for Boost ===
This step only needs to be performed once, after which the global variable you've created will be available for any project.
* Open the Settings menu and select "Global variables..."
* Click the "New" button next to the Current variable list, specify a name like "boost", and hit OK
* In the "base" field of the Builtin fields section, browse for the base of your Boost installation -- the path you specified in the --prefix option of the build command
* In the "include" field, browse for the "include\boost-1_37" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_37" tacked on.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
* Right-click your project's name in the Projects section of the Management window and select "Build options..."
* Highlight the root of your project in the tree on the left side of the Project build options window
* Select the "Search directories" tab
* With the "Compiler" subtab selected, click the Add button, enter "$(#boost.include)" (without the quotes), and hit OK
''If you are using the bundled version of MinGW with Code::Blocks, and you used your C::B installation in the --prefix option as recommended, the following step is unnecessary''
* With the "Linker" subtab selected, click the Add button, enter "$(#boost.lib)" (without the quotes), and hit OK

=== Include Boost headers and link with Boost libraries ===
Your project is now ready to use the Boost libraries. For each library you want to use, do the following:
* #include <boost/*.hpp> in your source file
* In your project's build options, highlight the root of your project, select the "Linker settings" tab, and add "boost_*-mgw34-mt-1_37" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw34-mt-1_37.lib" and "boost_system-mgw34-mt-1_37.lib" to use boost.filesystem.

== Test boost installation==
After the installation, you can use these [http://beans.seartipy.com/2006/03/16/how-to-test-c-boost-installation/ two examples] to test whether your boost installation and the configuration of your Code::Blocks are successful.

== Frequently Asked Questions ==

No Frequently Asked Questions (or Frequently Given Answers) have been entered yet.

WxWindowsQuickRef

2009-07-26T18:50:46Z

Seronis: /* wxWidgets Sources */

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up wxWidgets with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

[http://shiningray.cn/windows-shang-pei-zhi-codeblocks-wxwidgets.html Chinese Translation]

'''Important Requirements:'''
* '''Windows compiler''' - You need to have correctly installed the free [http://www.mingw.org/ MinGW/GCC] compiler or one of [http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]). The [https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled version which includes all necessary packages; or, if you install it by hand, you need at least the gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages. Also, ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5 the 8.02 release] or [/index.php/board,20.0.html a recent nightly build].

== Download wxWidgets ==
You can choose to download the wxWidgets source code and compile it yourself, or download the "wxPack", a precompiled version.
* '''The wxWidgets sources''' are a much smaller download, but you must also spend some time compiling them.
* '''wxPack''' is a much larger download, but you don't have to spend time compiling it or worry about build options.

=== wxWidgets Sources ===
The current recommended version of wxWidgets to use is '''2.8.10'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.10-Setup.exe Click here to download the wxWidgets 2.8.10 sources for Windows] (wxMSW-2.8.10-Setup.exe; 12.2 MB). You can check [http://www.wxwidgets.org/downloads/ the wxWidgets download page] to see if a newer stable version is available. '''It is highly recommended that you install the sources to a path without spaces.''' You should choose a volume with at least 300 MB of free space.

=== wxPack ===
The current stable release of wxPack is '''v2.8.8.04''', based on wxWidgets 2.8.8. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.8.04.exe?download Click here to download wxPack v2.8.8.04] (wxPack_v2.8.8.04.exe, 315.9 MB). You can check [http://wxpack.sourceforge.net/Main/Downloads the wxPack download page] to see if a newer stable version is available. '''It is highly recommended that you install wxPack in a path without spaces.''' You should choose a volume with at least 700 MB of free space for MSVC, or 2.2 GB of free space for MinGW/GCC.

== Build wxWidgets ==
''This step is unnecessary if you are using '''wxPack''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Change to the wxWidgets build directory (where <wxWidgets> is the path you extracted the sources to; typically C:\wxWidgets-2.8.9):
cd <wxWidgets>\build\msw
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is:
mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1
* The recommended command to use for '''MSVC''' is:
nmake -f makefile.vc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1
* This step will generally take a long time; faster PCs may expect 30-minute build times, and slower PCs can take as much as several hours.
* If using more recent versions of GCC, many warnings will occur during the build. This can slow the build process noticeably; you may want to redirect the warnings to a text file by appending "2>errlog.txt" to the build command, or supress them entirely by appending "2>nul".

See the section below titled "wxWidgets build options explained" for details on the meaning of the BUILD, SHARED, MONOLITHIC, and UNICODE options. These options are critically important, because they define the basic wxWidgets development environment you will be using. You must duplicate them exactly when running Code::Blocks' wxWidgets project wizard.

== Create a wxWidgets project in Code::Blocks ==
* On the Code::Blocks Start Page, select "Create a new project"; alternatively, open the File menu, highlight "New" and select "Project..."
* Select "wxWidgets project"
# The first page is an introduction, which you can choose to skip in the future.
# Select which version of wxWidgets you will be using. If you followed the instructions above, you should select "wxWidgets 2.8.x".
# Set your project title and location.
# Enter author details if you wish (not required).
# Select options for automatic code and file generation.
# Select wxWidgets' location. It's highly recommended that you use a global variable for this: enter "$(#wx)" (without quotes). If you haven't already defined this global variable, the global variables dialog will appear; for the base path, select your wxWidgets installation location. You don't need to fill in the other paths.
# Select debug and/or release configurations for your project. The debug configuration at least is recommended.
# Choose your wxWidgets build options. '''These must match the options used when you built wxWidgets!''' If you followed the directions above, select all three of the options under "wxWidgets Library Settings". '''If you are using wxPack:''' wxPack includes each version, so you may select whichever options you prefer. The other settings on this page are not related to the wxWidgets build options; you may use them or not as you prefer. In order to avoid using a debug wxWidgets build (as recommended), you must select "Configure Advanced options" and then leave "Use __WXDEBUG__ and Debug wxWidgets lib" unchecked on the next page.
# Select additional libraries if required. You should not need to select any of these for normal usage.

== Build and Run ==
Select "Build and run" (F9) to, well, build and run. If all goes well, your wxWidgets basic program should appear.

== wxWidgets Build Options Explained ==
''What do the BUILD, SHARED, MONOLITHIC, and UNICODE options mean?''

=== BUILD ===
BUILD controls whether a debug version (BUILD=debug) or release version (BUILD=release) of wxWidgets itself is built. In the vast majority of cases you will only need a release version of wxWidgets, since you won't be interesting in debugging wxWidgets itself. You can still create debug builds of your own programs that link to a release build of wxWidgets.
* A '''debug''' build of wxWidgets creates libraries with a "d" suffix -- for example, "libwxmsw28d.a"/"wxmsw28d_gcc_custom.dll".
* A '''debug''' build of wxWidgets creates the folder "mswd" or "mswud" in the wxWidgets library output folder.
* A '''release''' build of wxWidgets creates libraries ''without'' the "d" suffix -- for example, "libwxmsw28.a"/"wxmsw28_gcc_custom.dll".
* A '''release''' build of wxWidgets creates the folder "msw" or "mswu" in the wxWidgets library output folder.

=== SHARED ===
SHARED controls whether a DLL (SHARED=1) or static (SHARED=0) version of wxWidgets is built. With a DLL build, compile times are faster and the executable size is smaller. The total size of a single executable plus the wxWidgets DLL is greater, but multiple executables can use the same DLL.
* A '''DLL''' build of wxWidgets creates import libraries (such as libwxmsw28.a) and DLLs (such as wxmsw28_gcc_custom.dll). You must include the DLL when you distribute your program.
* A '''static''' build of wxWidgets creates static libraries only (such as libwxmsw28.a), and you do not need to distribute a wxWidgets DLL.

=== MONOLITHIC ===
MONOLITHIC controls whether a single library (MONOLITHIC=1) or multiple component libraries (MONOLITHIC=0) are built. With a monolithic build, project setup and development are much easier, and you only have one DLL to distribute if you're using a DLL build. With a non-monolithic (multilib) build, several different libraries are built and you can avoid linking with the entire wxWidgets codebase for programs that don't need it. You do have to ensure that you choose the correct component libraries.
* A '''monolithic''' build of wxWidgets creates a single wxWidgets import library (such as libwxmsw28.a) and a single DLL (such as wxmsw28_gcc_custom.dll).
* A '''multilib''' build of wxWidgets creates multiple import libraries (libwx28_base.a, etc.) and multiple DLLs.
* Additional '''static''' libraries are always created with any wxWidgets build (libwxexpat.a, libwxjpeg.a, etc.). These libraries do not normally need to be used with DLL builds of wxWidgets, but they are required when using static builds.

=== UNICODE ===
UNICODE controls whether wxWidgets and your program use wide-character strings with Unicode support. Most programs for Windows 2000 and later should do so. Earlier versions of Windows don't have the necessary Unicode support. You should always use wxWidget's _("string") and _T("string") macros to ensure that your hardcoded strings are the correct type.
* A '''Unicode''' (UNICODE=1) build of wxWidgets creates libraries with a "u" suffix -- for example, "libwxmsw28u.a"/"wxmsw28u_gcc_custom.dll".
* A '''Unicode''' build of wxWidgets creates the folder "mswu" or "mswud" in the wxWidgets library output folder.
* An '''ANSI''' (UNICODE=0) build of wxWidgets creates libraries ''without'' the "u" suffix -- for example, "libwxmsw28.a"/"wxmsw28_gcc_custom.dll".
* An '''ANSI''' build of wxWidgets creates the folder "msw" or "mswd" in the wxWidgets library output folder.

== Frequently Asked Questions ==

'''I get errors like "wx/setup.h: No such file or directory"'''

You're missing an important compiler search path in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, then open your project's build options and add "$(#wx.lib)\gcc_dll\mswu" (assuming a monolithic Unicode DLL build) to the compiler search paths.

'''I get errors like "cannot find -lwxmsw28u"'''

You have an incorrect link library in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, determine which version of the library is built and adjust the library name in your build options accordingly.

Installing Code::Blocks from source on Windows

2008-08-24T22:01:37Z

Seronis: /* wxWidgets */

[[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]

* 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 19 July 2008 wxWidgets 2.8.8 Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.8.zip wxMSW-2.8.8.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 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.

Installing MinGW with Vista

2008-04-09T15:25:37Z

Seronis: /* Compiler */ Added additional compiler search directory so that locale.h, required by clocale, is available

[[Category:User Documentation]]
--[[User:Darthdespotism|Darthdespotism]] 07:23, 29 June 2007 (UTC)
== Before we start ==

Before starting to install MinGW under Windows Vista there are some things to remember:

* MinGW '''must''' be located on the same partition as the files you want to compile
* There may be issues if you don't install MinGW in the toplevel folder (e.g. C:\MinGW) but in some folder (e.g. C:\Compilers\MinGW). There is a possible solution to this problem (see the "Troubleshooting" section at the bottom of this page).

For this HOWTO I used some Conventions:

* I assumed you are going to install in C:, if you want to install on another partition (which may be clever as the sources must be on the same partition) you'll have to modifie the path acordingly
* I used ''MinGW-Version'' to indicate that you must use your Version of MinGW here. As you can see on my pictures it is for me 4.2.0 and for those who downloaded on [http://mingw.org http://mingw.org] it is most probably 3.4.2

Just one thing left: I've done this under Vista Business and a friend of mine reported it working with Home Premium. I hope it works on the other versions, too.

== Getting MinGW ==
First of all you need the MinGW Compiler to be installed. I used the installer but all methods desciribed under [[MinGW installation]] should work fine. You may althoug want to upgrade your Version of MinGW to 4.* though. When you finished installing the basic MinGW we'll start making it work with Windows Vista. (Note: There is no need to set any %PATH% - variables when you use only Codeblocks, this is the way I'll focuse on)

== Actual Setup ==

=== Executeables ===
If you haven't already done it it is time to install and start Code::Blocks. It's a good idea to create a sample "console application" so you have a basic "Hello world" to test your progress. As I first tried to run "Compile" without any Modifications I got the following Error:

-------------- Build: Debug in test --------------- 
Compiling: main.cpp 
mingw32-g++.exe: CreateProcess: No such file or directory 
Process terminated with status 1 (0 minutes, 0 seconds) 
0 errors, 0 warnings

This doesn't tell us very much. The problem here actually is, that MinGW is unable to find its helper executeables, in this case cc1plus.exe. To fix this go to your "Settings" -> "Compiler and Debugger" -> "Toolchain executeables" -> "Additional paths" and add there the Directory "C:\MinGW\libexec\gcc\mingw32\''MinGW-Version'' where ''MinGW-Version'' is the Version of MinGW you are using. If you use a unmodified Version this is most probably 3.4.2, as I have the newer 4.2.0 I use this.

[[Image:mingw_vista_01.png]][[Image:mingw_vista_02.png]]

Let's try to compile again and see the progress.

=== Compiler ===

Hm still doesn't work, but the error changed:

-------------- Build: Debug in test --------------- 
Compiling: main.cpp 
C:\Users\Christoph\Projects\test\main.cpp:1:20: error: iostream: No such file or directory 
C:\Users\Christoph\Projects\test\main.cpp: In function 'int main()': 
C:\Users\Christoph\Projects\test\main.cpp:7: error: 'cout' was not declared in this scope 
C:\Users\Christoph\Projects\test\main.cpp:7: error: 'endl' was not declared in this scope 
Process terminated with status 1 (0 minutes, 1 seconds) 
3 errors, 0 warnings

So MinGW is not able to find <iostream>. Let's tell him where to search:

Still in the Compiler and Debugger dialogue go to "Search directories" -> "Compiler" and add:

C:\MinGW\include\ 
C:\MinGW\include\c++\''MinGW-Version'' 
C:\MinGW\include\c++\''MinGW-Version''\backward 
C:\MinGW\include\c++\''MinGW-Version''\mingw32 
C:\MinGW\lib\gcc\mingw32\''MinGW-Version''\include 

There are not necessarily all of them needed, but these are the directories MinGW searches in normally.

Try again to compile. The compiler should now execute nurmally, but there is a Linker error left:

=== Linker ===

Linking console executable: bin\Debug\test.exe 
ld: cannot find -lgcc 
Process terminated with status 1 (0 minutes, 1 seconds) 
1 errors, 0 warnings 

So we apparently need to tell MinGW where to search for it's librarys. This is again done by adding some "Search directories", but now we use the section "Linker"

: C:\MinGW\lib\gcc\mingw32\''MinGW-Version''

Try to compile, it should work.

[[Image:mingw_vista_03.png]][[Image:mingw_vista_04.png]]

=== Trouble shooting ===

If this does not work out for you there is some advice to figure it out on your own:

* If there is a file not found by MinGW use your search function to look for it, and add it where it belongs
** If it's an executeable (.exe) add it to the "additional paths" under "toolchain executeables"
** If it's a header (.h, .hpp or without extension) add it to "compiler" under "search directories"
** If it's a library (.o, .a) add it to "linker" under "search directories"
* Compile with the -v flag. You can do this by simply adding -v to "Build options" -> "Compiler" -> "Other options"
* Try entering the complete path to each program (for example, changing "mingw32-g++.exe" to "D:\toolkits\MinGW513\bin\mingw32-g++.exe"). This may allow projects to be compiled, regardless of which partition and folder MinGW is installed to. See [/index.php/topic,6422.0.html this forum thread] for more details.
--------------------------------------------

== '''An Easy Fix''' ==

I have been using this fix that was made available in the Mingw-Users list, by a kind a person. It works fine without having to do any abnormal modifications to your CodeBlocks setups.

----------------------------------
If it helps anyone else, I took the three patched drivers that Danny
posted (gcc, g++, collect2) and copied them to their various aliases
(e.g. c++, mingw-g++, etc) and put them in the appropriate directory
structure, and made it a tarball:

http://dessent.net/tmp/gcc-vista-3.4.5-20060117-1.tar.gz

$ tar ztvf gcc-vista-3.4.5-20060117-1.tar.gz
-rwxr-xr-x brian/None 86016 2007-05-18 18:41 bin/c++.exe
-rwxr-xr-x brian/None 86016 2007-05-18 18:41 bin/g++.exe
-rwxr-xr-x brian/None 83456 2007-05-18 18:40 bin/gcc.exe
-rwxr-xr-x brian/None 86016 2007-05-18 18:41 bin/mingw32-c++.exe
-rwxr-xr-x brian/None 86016 2007-05-18 18:41 bin/mingw32-g++.exe
-rwxr-xr-x brian/None 83456 2007-05-18 18:40 bin/mingw32-gcc-3.4.5
-rwxr-xr-x brian/None 83456 2007-05-18 18:40 bin/mingw32-gcc.exe
-rwx------ brian/None 85504 2007-05-18 18:41
libexec/gcc/mingw32/3.4.5/collect2.exe

If you unpack this in your MinGW root folder (e.g. /mingw) just like all
the other gcc-foo tarballs it should install the files in all the right
places. I tested this on a Vista copy running VMware and it worked fine
for compiling and linking C and C++.

(That's for 3.4.5 only.)

MinGW installation

2007-08-23T14:49:55Z

Seronis: /* UnxUtils */

[[Category:User Documentation]]
==Using the MinGW installer==
Note: At the present time, it is still preferrable to download the packages by hand, as the installers are not production quality (unless you really feel unsure unpacking a couple of archives).

Also, the installer reportedly does not work on Windows Vista, follow the [[MinGW_installation#GCC_3.4.5_manual_install | manual installation instructions]]. 
''(In general, MinGW is not confirmed to work for any Windows Vista betas or RCs)''

'''MinGW has been confirmed working in Windows Vista Business!''' Thanks to [http://aarongiles.com/?p=199 Aaron Giles' Solving the Windows Vista Build Issues] for the solution.
In summary, the MinGW folder must be "a directory immediately off the root of your hard disk for some reason. So c:\mingw works fine, but c:\tools\mingw won’t." (You can use mklink to symlink the folder, which also works). Secondly, set the GCC_EXEC_PREFIX environment variable to the MinGW root folder. Finally, add %GCC_EXEC_PREFIX%\libexec\gcc\mingw32\3.4.5 and %GCC_EXEC_PREFIX%\lib\bin to the PATH environment variable.

'''A HowTo exists [[Installing_MinGW_with_Vista | here]]'''

MinGW Installer 5.02 allows to choose the SF mirror while 5.03 does not (automatically picks one randomly).

MinGW Installer 5.0.x are broken because of changes done by sf.net; please use the MinGW Installer 5.1.x

Installers allows to downloads/installs "previous", "current" and "candidate" mingw packages.

*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.2.exe MinGW Installer 5.0.2]
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.0.3.exe MinGW Installer 5.0.3]
*[http://prdownloads.sourceforge.net/mingw/MinGW-5.1.3.exe MinGW Installer 5.1.3]

'''Note that the MinGW version number is not related to the actual compiler version.'''

Please do note that the installer applications require an internet connection and will download the actual MinGW packages at the time of installation.

The required MinGW Components are "MinGW Base Tools", "g++ compiler" and "MinGW make".

==GCC 3.4.5 manual install==
This is the "candidate" release of MinGW, so it is not considered "stable" officially. Personally, I have not had any kind of problem with this release.

To do a manual install, simply download the desired files and extract them all into the same directory. If you have WinZip, PowerArchiver, or any other similar program, this is as easy as selecting all the archives simultaneously and choosing "unpack here" from the context menu.

For clarity, I recommend to put MinGW into C:\MinGW, but almost any other locations should do equally well. Avoid pathnames with spaces or exotic characters, as this may confuse some commandline tools (most notably <tt>gdb</tt>).
===Base system with C++===
*[http://prdownloads.sf.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz http://prdownloads.sf.net/mingw/gcc-core-3.4.5-20060117-1.tar.gz]
*[http://prdownloads.sf.net/mingw/gcc-g%2B%2B-3.4.5-20060117-1.tar.gz http://prdownloads.sf.net/mingw/gcc-g++-3.4.5-20060117-1.tar.gz]
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz]
*[http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz]
*[http://prdownloads.sf.net/mingw/w32api-3.6.tar.gz http://prdownloads.sf.net/mingw/w32api-3.6.tar.gz]
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz]
*[http://prdownloads.sf.net/mingw/mingw32-make-3.81-1.tar.gz http://prdownloads.sf.net/mingw/mingw32-make-3.81-1.tar.gz]

===Optionally:===
====Fortran77 compiler====
*[http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz http://prdownloads.sf.net/mingw/gcc-g77-3.4.5-20060117-1.tar.gz]
====gdb debugger====
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe http://prdownloads.sf.net/mingw/gdb-6.3-2.exe]
====Other developer tools====
=====UnxUtils=====
Ports of the most often used Unix utilities. Note that some tools in UnxUtils are quite a bit outdated, so make sure you do not overwrite already existing MinGW files with their UnxUtils counterparts.
*[http://prdownloads.sf.net/unxutils/UnxUtils.zip UnxUtils]
*[http://prdownloads.sf.net/unxutils/UnxUpdates.zip UnxUtils-Latest-Updates]

=====GnuWin32=====
''More recent'' versions of commonly used Unix utilities. Also: utilities not found in UnxUtils at all.
*[http://prdownloads.sf.net/gnuwin32/coreutils-5.3.0-bin.zip coreutils-5.3.0]
*[http://prdownloads.sf.net/gnuwin32/zip-2.3-3-bin.zip zip-2.3.3]
*[http://prdownloads.sf.net/gnuwin32/tar-1.13-1-bin.zip tar-1.13-1]
*[http://prdownloads.sf.net/gnuwin32/gzip-1.3.5-3-bin.zip gzip-1.3.5]
*[http://prdownloads.sf.net/gnuwin32/bzip2-1.0.3-1-bin.zip bzip2-1.0.0-1]
*[http://prdownloads.sf.net/gnuwin32/autoconf-2.59-bin.zip autoconf-2.59]
*[http://prdownloads.sf.net/gnuwin32/automake-1.9.4-bin.zip automake-1.9.4]
*[http://prdownloads.sf.net/gnuwin32/bison-2.1-bin.zip bison-2.1 (includes m4)]
*[http://prdownloads.sf.net/gnuwin32/flex-2.5.4a-1-bin.zip flex-2.5.4a]
*[http://prdownloads.sf.net/gnuwin32/gperf-3.0.1-bin.zip gperf-3.0.1]
*[http://prdownloads.sf.net/gnuwin32/diffutils-2.8.7-1-bin.zip diffutils-2.8.7]
*[http://prdownloads.sf.net/gnuwin32/patch-2.5.9-6-bin.zip patch-2.5.9-6] Note: The version 2.5.9 of patch from GnuWin32 seems to have a problem with unified diffs
*[http://prdownloads.sf.net/gnuwin32/grep-2.5.1a-bin.zip grep-2.5.1]
*[http://prdownloads.sf.net/gnuwin32/sed-4.1.4-bin.zip sed-4.1.4]
*[http://prdownloads.sf.net/gnuwin32/hextools-1.0-bin.zip hextools-1.0]
*[http://prdownloads.sf.net/gnuwin32/findutils-4.2.20-2-bin.zip findutils-4.2.20]
*[http://prdownloads.sf.net/gnuwin32/less-394-bin.zip less 3.94]
*[http://prdownloads.sf.net/gnuwin32/which-2.16-4.exe which 2.16-4]
*[http://prdownloads.sf.net/mingw/wget-1.9.1-mingwPORT.tar.bz2 wget-1.9.1]
*[http://www.gimp.org/~tml/gimp/win32/gettext-0.14.5.zip gettext-0.14.5]
*[http://www.gimp.org/~tml/gimp/win32/gettext-dev-0.14.5.zip gettext-dev-0.14.5]

Dependencies:
*[http://prdownloads.sf.net/gnuwin32/pcre-6.4-1-bin.zip pcre-6.4.1 (needed by grep and less)]
*[http://prdownloads.sf.net/gnuwin32/libintl-0.14.4-bin.zip libintl-0.14.4 (needed by most tools)]
*[http://prdownloads.sf.net/gnuwin32/libiconv-1.9.2-1-bin.zip libiconv-1.9.2-1 (needed by most tools)]

==Resulting Folder Layout==
[[Image:Lay.png]]

==GCC 3.4.4 manual install==
Some people have reported various problems with gcc version 3.4.4, so it may be worth a consideration to use the either the 3.4.5 or 3.4.2 releases until a build from the 4.x branch is available. Personally, I have not had any kind of problem with either 3.4.4 or 3.4.5.
===Base system with C++===
*[http://prdownloads.sf.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz http://prdownloads.sf.net/mingw/gcc-core-3.4.4-20050522-1.tar.gz]
*[http://prdownloads.sf.net/mingw/gcc-g%2B%2B-3.4.4-20050522-1.tar.gz http://prdownloads.sf.net/mingw/gcc-g++-3.4.4-20050522-1.tar.gz]
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz]
*[http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz]
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz]
*[http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz http://prdownloads.sf.net/mingw/binutils-2.17.50-20060824-1.tar.gz]
*[http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.tar.gz http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.tar.gz]

===Optionally:===
====gdb debugger====
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe http://prdownloads.sf.net/mingw/gdb-6.3-2.exe]
====Objective-C====
*[http://prdownloads.sf.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz http://prdownloads.sf.net/mingw/gcc-objc-3.4.4-20050522-1.tar.gz]
====Native Java (experimental)====
*[http://prdownloads.sf.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz http://prdownloads.sf.net/mingw/gcc-java-3.4.4-20050522-1.tar.gz]
====Fortran-77====
*[http://prdownloads.sf.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz http://prdownloads.sf.net/mingw/gcc-g77-3.4.4-20050522-1.tar.gz]
====Ada====
*[http://prdownloads.sf.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz http://prdownloads.sf.net/mingw/gcc-ada-3.4.4-20050522-1.tar.gz]

==GCC 3.4.2 manual install==
Installing MinGW can be quite intimidating the first time because it is not obvious what you have to do. Luckily, it is actually pretty simple. 
To do a manual install, simply download the required files and extract them all into the same directory. For simplicity, I recommend <tt>C:\MinGW</tt>.
===Base system with C++===
*[http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz]
*[http://prdownloads.sf.net/mingw/gcc-g%2B%2B-3.4.2-20040916-1.tar.gz http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz]
*[http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz http://prdownloads.sf.net/mingw/mingw-runtime-3.9.tar.gz]
*[http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz]
*[http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz http://prdownloads.sf.net/mingw/w32api-3.5.tar.gz]
*[http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz http://prdownloads.sf.net/mingw/binutils-2.16.91-20050827-1.tar.gz]
*[http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.tar.gz http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.tar.gz]

===Optionally:===
====gdb debugger====
*[http://prdownloads.sf.net/mingw/gdb-6.3-2.exe http://prdownloads.sf.net/mingw/gdb-6.3-2.exe]
====Objective-C====
*[http://prdownloads.sf.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz http://prdownloads.sf.net/mingw/gcc-objc-3.4.2-20040916-1.tar.gz]
====Native Java (experimental)====
*[http://prdownloads.sf.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz http://prdownloads.sf.net/mingw/gcc-java-3.4.2-20040916-1.tar.gz]
====Fortran77 compiler====
*[http://prdownloads.sf.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz http://prdownloads.sf.net/mingw/gcc-g77-3.4.2-20040916-1.tar.gz]

====Ada====
*[http://prdownloads.sf.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz http://prdownloads.sf.net/mingw/gcc-ada-3.4.2-20040916-1.tar.gz]