Code::Blocks - User contributions [en]

WxWindowsQuickRef

2013-01-30T00:53:51Z

TDragon: Condense unnecessary introductory info; remove wxPack as it uses outdated GCC; update links to external components including wxWidgets

[[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:'''
* '''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/26 the 12.11 release] or [/index.php/board,20.0.html a recent nightly build].

* '''Windows compiler''' - You need to have correctly installed either
**the [http://www.mingw.org/ MinGW/GCC] free compiler (or one of its forks), or
**[http://msdn.microsoft.com/vstudio/ Microsoft Visual C++] (the [http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-products Express editions] are free, but you must also install the [http://www.microsoft.com/en-us/download/details.aspx?id=8279 Platform SDK]).
When downloading an official Code::Blocks release, you have the option of downloading a bundle package that includes a full MinGW/GCC toolchain.

* '''Path properly defined''' - Ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin, or C:\MinGW32\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].

== Download wxWidgets Source Code ==
wxWidgets is distributed in source code format, and you need to compile it into a library before you can use it in your own programs.

The current recommended version of wxWidgets to use is '''2.8.12'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.12-Setup.exe Click here to download the wxWidgets 2.8.12 sources for Windows] (wxMSW-2.8.12-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''' is no longer recommended for use, as it is built with a much older version of GCC.''

== Build wxWidgets ==
* 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.12):
cd /D <wxWidgets>\build\msw
''Note: the <code>/D</code> flag after <code>cd</code> may be omitted from the command; it simply allows command prompt to change drives if necessary.
* 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 CXXFLAGS=-fno-keep-inline-dllexport
* 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".

The "CXXFLAGS=-fno-keep-inline-dllexport" option is necessary with recent versions of GCC (not with MSVC), to prevent problems with memory usage when performing the final link step on the monolithic DLL.

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

'''I get errors like "undefined reference to _Unwind_*"'''

wxWidgets was built with a different version of GCC than the one you're currently using. You need to rebuild wxWidgets with the same version of GCC that you use to compile your program.

==See also==
Forum thread - [/index.php?topic=5359.0 Newbie problem in setting up wxwidgets and Codeblocks]

WxWindowsQuickRef

2010-09-05T14:54:04Z

TDragon: /* Frequently Asked Questions */ Errors for differing GCC unwind versions

[[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:'''
* '''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/26 the 10.05 release] or [/index.php/board,20.0.html a recent nightly build].


* '''Windows compiler''' - You need to have correctly installed one of three options
**[http://www.mingw.org/ MinGW/GCC] free compiler, gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages are required, or
**[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]), or
**[https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled compiler which includes all necessary packages

* '''Path properly defined.'''
** 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]. The path environment variable is changed by
***right-clicking on 'my computer',
***selecting properties,
***click the advanced tab,
***click the 'Environment Variables' button at the bottom.

To verify the path is set correctly, open a DOS prompt and enter the command: mingw32-gcc, a reply of 'Not recognized' indicates a problem. 'no input files' means that the program was found and that the path environment variable is correct. For example...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>mingw32-gcc
mingw32-gcc: no input files
C:\>

== 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 ===
wxPack makes the next step of building wxWidgets unnecessary. 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.

'''I get errors like "undefined reference to _Unwind_*"'''

wxWidgets was built with a different version of GCC than the one you're currently using. You need to rebuild wxWidgets with the same version of GCC that you use to compile your program.

WxWindowsQuickRef

2009-11-24T14:35:49Z

TDragon: Objections to recent changes - see Discussion page

[[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:'''
* '''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].


* '''Windows compiler''' - You need to have correctly installed one of three options
**[http://www.mingw.org/ MinGW/GCC] free compiler, gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages are required, or
**[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]), or
**[https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled compiler which includes all necessary packages

* '''Path properly defined.'''
** 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]. The path environment variable is changed by
***right-clicking on 'my computer',
***selecting properties,
***click the advanced tab,
***click the 'Environment Variables' button at the bottom.

To verify the path is set correctly, open a DOS prompt and enter the command: mingw32-gcc, a reply of 'Not recognized' indicates a problem. 'no input files' means that the program was found and that the path environment variable is correct. For example...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>mingw32-gcc
mingw32-gcc: no input files
C:\>

== 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 ===
wxPack makes the next step of building wxWidgets unnecessary. 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.

Talk:WxWindowsQuickRef

2009-11-24T14:29:22Z

TDragon: Created page with 'Troyf, I feel that the changes you've made on 2009-11-23 detract from the purpose of providing a *succinct* (quick) guide to getting started with wxWidgets on Windows. * Instruct…'

Troyf,
I feel that the changes you've made on 2009-11-23 detract from the purpose of providing a *succinct* (quick) guide to getting started with wxWidgets on Windows.
* Instructions on how to change the PATH variable in Windows are provided in my original link for the very purpose of avoiding reiteration within the guide.
* The new layout pushes the table of contents quite a bit further down the page: the preface is inappropriately long.
* The guide is designed for both MinGW/GCC users and Visual C++ users, but you haven't included the appropriate corresponding information for the Visual C++ users.
* The line you added about wxPack making a wxWidgets build unnecessary is itself completely unnecessary, as the same information has already been presented in the summary of options and will be reiterated for good measure at the beginning of the build step.
If you feel that it's important to display this additional information, perhaps it would be more appropriate at the foot of the article in a note or FAQ. What are your thoughts?

- [[User:TDragon|TDragon]] 14:29, 24 November 2009 (UTC)

BoostWindowsQuickRef

2009-09-04T15:17:05Z

TDragon: Update for Boost 1.40.0; add FAQ about components and link 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.40.0'''. [http://sourceforge.net/projects/boost/files/boost/1.40.0/ Click here to browse the Boost 1.40.0 downloadable 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_40_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.

BoostWindowsQuickRef

2009-09-04T14:59:30Z

TDragon: /* Include Boost headers and link with Boost libraries */ Corrected by removing .lib extension

[[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_*-mgwXX-mt-1_39" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw44-mt-1_39" and "boost_system-mgw44-mt-1_39" 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.

Main Page

2009-03-19T14:10:17Z

TDragon: Moved Compiled_packages link from documentation to downloads

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

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

}}

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


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

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

|-

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

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


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

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


|-

|align="center"|
'''...create a new project?''' (Coming soon)

|align="center"|
'''...debug my program?''' (Coming soon)

|-

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

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


|}
</div>

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

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

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

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

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

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

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

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

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

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
}}

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

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

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

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

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

Talk:Main Page

2009-01-07T00:31:08Z

TDragon: /* Restructuring '08 */ Ambiguous

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

Done. mandrav took care of it. :D

/index.php?topic=2733.0

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

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

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

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

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

----

Other suggestions:

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

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

Category list in navigation pane:

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

== Restructuring '08 ==

I've started in on a project of some basic restructuring and (hopefully) a lot of new content for the Wiki in an attempt to provide documentation that is "newb-friendly" -- in other words, accessible to beginning programmers and first-time Code::Blocks users. This Wiki is currently the most powerful source of C::B reference material there is and will probably remain so unless a team of professional documentation writers signs on.

This being a Wiki, I've taken the initiative and will proceed with the aforesaid overhaul unless asked not to. Since I can't do this full time, changes will take place gradually. And, of course, feel free to correct, amend, or suggest improvement as appropriate.

- [[User:TDragon|TDragon]] 22:01, 19 July 2008 (CEST)

----

Hi, TDragon.
I find your comments on the page This page.
There are still two links not implemented. I'm not sure using "video tutorial" is a good idea. But I do create some video tutorials. These links are
[http://sites.google.com/site/studycodeblocks/Home/test_video.swf?attredirects=0 simple_introduction]
and
[http://sites.google.com/site/studycodeblocks/Home/wx.swf?attredirects=0 wxWidgets_introduction]

I think it is useful for a beginner or newbie.

But this wiki does not support "flash", because it is a commercial software. See a discussion at the forum here: [/index.php/topic,9827.0.html SWF supported?]
[[User:Ollydbg|Ollydbg]] 17:20, 6 January 2009 (CET)

----

I don't have any feelings one way or the other on the usefulness of a video tutorial. However, this is a wiki, and if you place those same external links on appropriate pages here in the Wiki (I would recommend [[Using_wxWidgets]] for the second one), I'm not going to cause a fuss.

- [[User:TDragon|TDragon]] 01:31, 7 January 2009 (CET)

----

=== Milestones ===
2008-07-19: Main page restructured, "How do I..." added

BoostWindowsQuickRef

2008-12-01T19:32:02Z

TDragon: Update for Boost 1.37.0 and bjam 3.1.17

[[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.37.0'''. [http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=637761 Click here to browse the Boost 1.37.0 downloadable files]. 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 X MB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_37_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.

BoostWindowsQuickRef

2008-12-01T19:30:52Z

TDragon: /* Boost Source Code */ Update for 1.37.0

[[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.37.0'''. [http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=637761 Click here to browse the Boost 1.37.0 downloadable files]. 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 X MB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_37_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.16-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_36_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_36" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_36" 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_36" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>", "boost_filesystem-mgw34-mt-1_36.lib" and "boost_system-mgw34-mt-1_36.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

2008-10-20T19:33:45Z

TDragon: Updated for Boost 1.36.0

[[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.36.0'''. [http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=619445 Click here to browse the Boost 1.36.0 downloadable files]. 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.16'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.16-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.16-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack the sources to a path without spaces.''' You should choose a volume with at least XXX MB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_36_0" and "<path>\boost-jam-3.1.16-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.16-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_36_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_36" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_36" 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_36" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>" and "boost_filesystem-mgw34-mt-1_36" to use boost.filesystem.

== Frequently Asked Questions ==

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

WxWindowsQuickRef

2008-10-20T19:30:43Z

TDragon: /* Build wxWidgets */ Updated for wx 2.8.9

[[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.9'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.9-Setup.exe Click here to download the wxWidgets 2.8.9 sources for Windows] (wxMSW-2.8.9-Setup.exe; 11.9 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.

WxWindowsQuickRef

2008-09-29T13:33:11Z

TDragon: Update for wxWidgets 2.8.9

[[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.9'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.9-Setup.exe Click here to download the wxWidgets 2.8.9 sources for Windows] (wxMSW-2.8.9-Setup.exe; 11.9 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.8):
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.

WxWindowsQuickRef

2008-09-17T00:05:16Z

TDragon: Updated for wxPack 2.8.8.04

[[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.8'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.8-Setup.exe Click here to download the wxWidgets 2.8.8 sources for Windows] (wxMSW-2.8.8-Setup.exe; 12.0 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.8):
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.

Main Page

2008-08-13T19:21:36Z

TDragon: Link to FC install

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

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

}}

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


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

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

|-

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

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


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

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


|-

|align="center"|
'''...create a new project?''' (Coming soon)

|align="center"|
'''...debug my program?''' (Coming soon)

|-

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

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


|}
</div>

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

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

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

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

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

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

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

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

{{Layout_box4|1=
=== Download Code::Blocks ===
* Last official release: [https://www.codeblocks.org/downloads/5 8.02]
* [/index.php?board=20.0 Nightly builds] (updated each night)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
}}

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

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

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

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

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

Main Page

2008-08-13T19:21:00Z

TDragon: Link to Mac OS X install

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

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

}}

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


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

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

|-

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

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


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

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


|-

|align="center"|
'''...create a new project?''' (Coming soon)

|align="center"|
'''...debug my program?''' (Coming soon)

|-

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

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


|}
</div>

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

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

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

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

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

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

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

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

{{Layout_box4|1=
=== Download Code::Blocks ===
* Last official release: [https://www.codeblocks.org/downloads/5 8.02]
* [/index.php?board=20.0 Nightly builds] (updated each night)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
}}

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

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

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

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

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

Main Page

2008-08-13T19:20:09Z

TDragon: Link to Ubuntu install

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

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

}}

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


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

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

|-

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

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


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

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


|-

|align="center"|
'''...create a new project?''' (Coming soon)

|align="center"|
'''...debug my program?''' (Coming soon)

|-

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

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


|}
</div>

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

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

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

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

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

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

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

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

{{Layout_box4|1=
=== Download Code::Blocks ===
* Last official release: [https://www.codeblocks.org/downloads/5 8.02]
* [/index.php?board=20.0 Nightly builds] (updated each night)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
}}

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

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

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

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

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

Main Page

2008-07-21T18:33:46Z

TDragon: Update MinGW and MSVC setup links in How To

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

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

}}

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


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

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

|-

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

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] ·
[[Installing_in_Ubuntu|Ubuntu]] ·
[[Installing_in_Mac_OS_X|Mac OS X]] ·
[[Installing_in_Fedora_Core|Fedora Core]] ·
[[Installing_Code::Blocks|more...]]


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

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


|-

|align="center"|
'''...create a new project?''' (Coming soon)

|align="center"|
'''...debug my program?''' (Coming soon)

|-

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

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


|}
</div>

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

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

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

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

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

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

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

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

{{Layout_box4|1=
=== Download Code::Blocks ===
* Last official release: [https://www.codeblocks.org/downloads/5 8.02]
* [/index.php?board=20.0 Nightly builds] (updated each night)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
}}

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

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

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

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

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

Installing a supported compiler

2008-07-21T18:30:14Z

TDragon: Cleanup, some updating to Windows category

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

You can also install MinGW yourself, by using an automatic downloader/installer or by downloading and unpacking the desired packages by hand. If you don't install MinGW in C:\MinGW, you'll need to update the configuration of GCC in Code::Blocks.

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

BoostWindowsQuickRef

2008-07-20T14:41:18Z

TDragon: /* Include Boost headers and link with Boost libraries */ Corrected for C::B library autocorrect

[[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.35.0'''. [http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=587936 Click here to browse the Boost 1.35.0 downloadable files]. 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.16'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.16-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.16-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack the sources to a path without spaces.''' You should choose a volume with at least XXX MB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_35_0" and "<path>\boost-jam-3.1.16-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.16-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_35_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_35" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_35" 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_35" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>" and "boost_filesystem-mgw34-mt-1_35" to use boost.filesystem.

== Frequently Asked Questions ==

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

Talk:Main Page

2008-07-19T20:01:26Z

TDragon: Restructuring '08

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

Done. mandrav took care of it. :D

/index.php?topic=2733.0

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

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

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

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

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

----

Other suggestions:

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

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

Category list in navigation pane:

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

== Restructuring '08 ==

I've started in on a project of some basic restructuring and (hopefully) a lot of new content for the Wiki in an attempt to provide documentation that is "newb-friendly" -- in other words, accessible to beginning programmers and first-time Code::Blocks users. This Wiki is currently the most powerful source of C::B reference material there is and will probably remain so unless a team of professional documentation writers signs on.

This being a Wiki, I've taken the initiative and will proceed with the aforesaid overhaul unless asked not to. Since I can't do this full time, changes will take place gradually. And, of course, feel free to correct, amend, or suggest improvement as appropriate.

- [[User:TDragon|TDragon]] 22:01, 19 July 2008 (CEST)

=== Milestones ===
2008-07-19: Main page restructured, "How do I..." added

Main Page

2008-07-19T19:51:48Z

TDragon: Begun some restructuring for clarity and newb-friendliness

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

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

}}

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


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

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

|-

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

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] ·
[[Installing_in_Ubuntu|Ubuntu]] ·
[[Installing_in_Mac_OS_X|Mac OS X]] ·
[[Installing_in_Fedora_Core|Fedora Core]] ·
[[Installing_Code::Blocks|more...]]


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

[[Installing_a_supported_compiler#Downloading_the_GNU_GCC_compiler_.26_GDB_debugger|MinGW]] ·
[[Installing_a_supported_compiler#Downloading_the_Microsoft_Visual_C.2B.2B_Free_Toolkit_2003|MS Visual C++]] ·
[[Installing_a_supported_compiler|more...]]


|-

|align="center"|
'''...create a new project?''' (Coming soon)

|align="center"|
'''...debug my program?''' (Coming soon)

|-

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

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


|}
</div>

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

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

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

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

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

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

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

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

{{Layout_box4|1=
=== Download Code::Blocks ===
* Last official release: [https://www.codeblocks.org/downloads/5 8.02]
* [/index.php?board=20.0 Nightly builds] (updated each night)
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [ Community forums]
}}

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

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

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

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

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

User:TDragon

2008-07-19T19:35:25Z

TDragon: More work

Hello, world!

{{Layout_box2|1=
=== How do I... ===
'''[[Installing_Code::Blocks|...install Code::Blocks?]]''' 

[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] |
[[Installing_in_Ubuntu|Ubuntu]] |
[[Installing_in_Mac_OS_X|Mac OS X]] |
[[Installing_in_Fedora_Core|Fedora Core]] |
[[Installing_Code::Blocks|more...]]


'''[[Installing_a_supported_compiler|...set up a compiler in Code::Blocks?]]''' 

[[Installing_a_supported_compiler#Downloading_the_GNU_GCC_compiler_.26_GDB_debugger|MinGW]] |
[[Installing_a_supported_compiler#Downloading_the_Microsoft_Visual_C.2B.2B_Free_Toolkit_2003|MS Visual C++]] |
[[Installing_a_supported_compiler|more...]]


'''...create a new project?''' (Coming soon)

'''...debug my program?''' (Coming soon)

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

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

}}

[[WxWindowsQuickRef|Code::Blocks and wxWidgets on Windows Quick Reference]]

[[BoostWindowsQuickRef|Code::Blocks and Boost on Windows Quick Reference]]

User:TDragon

2008-07-19T18:23:38Z

TDragon: Continued linkification and restructuring

Hello, world!

{{Layout_box2|1=
=== How do I... ===
'''[[Installing_Code::Blocks|...install Code::Blocks?]]''' 
[[Installing_the_latest_official_version_of_Code::Blocks_on_Windows|Windows]] | [[Installing_in_Ubuntu|Ubuntu]] | [[Installing_in_Mac_OS_X|Mac OS X]] | [[Installing_in_Fedora_Core|Fedora Core]] | [[Installing_Code::Blocks|more...]]

'''...set up a compiler in Code::Blocks?''' (Coming soon) 
MinGW | MS Visual C++ | more...

'''...create a new project?''' (Coming soon)

'''...debug my program?''' (Coming soon)

'''[[User_documentation#Third-party_libraries|...use a 3rd-party library?]]''' 
[[Using_wxWidgets|wxWidgets]] | [[Using_Boost|Boost]] | [[Using_SDL|SDL]] | [[User_documentation#Third-party_libraries|more...]]
}}

[[WxWindowsQuickRef|Code::Blocks and wxWidgets on Windows Quick Reference]]

[[BoostWindowsQuickRef|Code::Blocks and Boost on Windows Quick Reference]]

Using Boost

2008-07-19T18:18:08Z

TDragon: Created

[[Category:User Documentation]]

Boost is a popular set of peer-reviewed, portable C++ libraries for a wide variety of general purpose data structures and algorithms. For more information about Boost, see [http://www.boost.org/ boost.org].

== Windows ==
* [[BoostWindowsQuickRef]]: A beginner's quick reference for setting up Boost with Code::Blocks in Windows

Using wxWidgets

2008-07-19T18:15:14Z

TDragon: Created

[[Category:User Documentation]]

wxWidgets is a cross-platform toolkit that helps developers create programs with native GUI controls. For more information about wxWidgets, see [http://www.wxwidgets.org/ wxwidgets.org].

== Windows ==
* [[WxWindowsQuickRef]]: A beginner's quick reference for setting up wxWidgets with Code::Blocks in Windows
* [[Compiling wxWidgets 2.8.6 to develop Code::Blocks (MSW)]]

== Linux (General) ==
* [[Cross Compiling wxWidgets Applications on Linux]]

User:TDragon

2008-07-19T15:51:45Z

TDragon: Start How Do I stuff

Hello, world!

{{Layout_box2|1=
=== How do I... ===
'''...install Code::Blocks?''' 
Windows | Ubuntu | Fedora Core | more...

'''...set up a compiler in Code::Blocks?''' 
MinGW | MS Visual C++ | more...

'''...create a new project?'''

'''...debug my program?'''

'''...use a 3rd-party library?''' 
wxWidgets | Boost | SDL | more...
}}

[[WxWindowsQuickRef|Code::Blocks and wxWidgets on Windows Quick Reference]]

[[BoostWindowsQuickRef|Code::Blocks and Boost on Windows Quick Reference]]

BoostWindowsQuickRef

2008-07-19T15:19:46Z

TDragon: Fixed mistake in include paths searching

[[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.35.0'''. [http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=587936 Click here to browse the Boost 1.35.0 downloadable files]. 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.16'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.16-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.16-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack the sources to a path without spaces.''' You should choose a volume with at least XXX MB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_35_0" and "<path>\boost-jam-3.1.16-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.16-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_35_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_35" subfolder of your Boost installation -- it should be the path in the "base" field with "\include\boost-1_35" 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 "libboost_*-mgw34-mt-1_35.lib" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>" and "libboost_filesystem-mgw34-mt-1_35.lib" to use boost.filesystem.

== Frequently Asked Questions ==

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

WxWindowsQuickRef

2008-07-18T21:25:09Z

TDragon: Updated to mention MinGW-bundled C::B

[[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.8'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.8-Setup.exe Click here to download the wxWidgets 2.8.8 sources for Windows] (wxMSW-2.8.8-Setup.exe; 12.0 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.7.03''', based on wxWidgets 2.8.7. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.7.03.exe?download Click here to download wxPack v2.8.7.03] (wxPack_v2.8.7.03.exe, 236.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.8):
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.

BoostWindowsQuickRef

2008-07-18T16:50:06Z

TDragon: Changed build time estimate

[[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.35.0'''. [http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=587936 Click here to browse the Boost 1.35.0 downloadable files]. 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.16'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.16-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.16-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack the sources to a path without spaces.''' You should choose a volume with at least XXX MB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_35_0" and "<path>\boost-jam-3.1.16-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.16-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_35_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 ===
''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, this step is unnecessary''

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_35" subfolder of your Boost installation -- it should look something like C:\<path>\boost-1.35\include\boost-1_35.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
''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, this step is unnecessary''

* 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
* 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 "libboost_*-mgw34-mt-1_35.lib" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>" and "libboost_filesystem-mgw34-mt-1_35.lib" to use boost.filesystem.

== Frequently Asked Questions ==

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

WxWindowsQuickRef

2008-07-18T16:46:54Z

TDragon: Added supported compilers notation, removed self-credit

[[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]). If using MinGW/GCC, 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:\MinGW\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.8'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.8-Setup.exe Click here to download the wxWidgets 2.8.8 sources for Windows] (wxMSW-2.8.8-Setup.exe; 12.0 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.7.03''', based on wxWidgets 2.8.7. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.7.03.exe?download Click here to download wxPack v2.8.7.03] (wxPack_v2.8.7.03.exe, 236.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.8):
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.

User:TDragon

2008-07-18T16:44:41Z

TDragon: Updated for Boost quickref

Hello, world!

[[WxWindowsQuickRef|Code::Blocks and wxWidgets on Windows Quick Reference]]

[[BoostWindowsQuickRef|Code::Blocks and Boost on Windows Quick Reference]]

BoostWindowsQuickRef

2008-07-18T16:43:15Z

TDragon: Created the BoostWindowsQuickRef

[[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.35.0'''. [http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=587936 Click here to browse the Boost 1.35.0 downloadable files]. 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.16'''. [http://downloads.sourceforge.net/boost/boost-jam-3.1.16-1-ntx86.zip Click here to download Boost Jam for Windows] (boost-jam-3.1.16-1-ntx86.zip; 115 KB).

'''It is highly recommended that you unpack the sources to a path without spaces.''' You should choose a volume with at least XXX MB of free space. Typically, the Boost sources and Boost Jam are unpacked in separate locations, ending up with "<path>\boost_1_35_0" and "<path>\boost-jam-3.1.16-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.16-1-ntx86;%PATH%
* Change to the Boost sources directory (where <path> is the path you unpacked the Boost sources to):
cd <path>\boost_1_35_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 10-30 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 ===
''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, this step is unnecessary''

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_35" subfolder of your Boost installation -- it should look something like C:\<path>\boost-1.35\include\boost-1_35.
* Hit the Close button to save your global variable

=== Add Boost search directories to your project ===
''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, this step is unnecessary''

* 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
* 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 "libboost_*-mgw34-mt-1_35.lib" to your Link libraries
For examle, use "#include <boost/filesystem.hpp>" and "libboost_filesystem-mgw34-mt-1_35.lib" to use boost.filesystem.

== Frequently Asked Questions ==

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

User documentation

2008-07-18T15:15:03Z

TDragon: Add link for new BoostWindowsQuickRef article

[[Category:Code::Blocks Documentation]]
[[Category:User Documentation]]
__TOC__
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

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

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

== User interface development ==

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

WxWindowsQuickRef

2008-07-09T16:25:23Z

TDragon: Updated for wxWidgets 2.8.8

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

by JohnE / TDragon (TDM)

[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]). If using MinGW/GCC, 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:\MinGW\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.8'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.8-Setup.exe Click here to download the wxWidgets 2.8.8 sources for Windows] (wxMSW-2.8.8-Setup.exe; 12.0 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.7.03''', based on wxWidgets 2.8.7. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.7.03.exe?download Click here to download wxPack v2.8.7.03] (wxPack_v2.8.7.03.exe, 236.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.8):
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.

WxWindowsQuickRef

2008-03-26T19:37:03Z

TDragon: /* Create a wxWidgets project in Code::Blocks */ Updated to reflect minor bug in C::B project wizard

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

by JohnE / TDragon (TDM)

[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]). If using MinGW/GCC, 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:\MinGW\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.7'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.7-Setup.exe Click here to download the wxWidgets 2.8.7 sources for Windows] (wxMSW-2.8.7-Setup.exe; 12.0 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.7.03''', based on wxWidgets 2.8.7. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.7.03.exe?download Click here to download wxPack v2.8.7.03] (wxPack_v2.8.7.03.exe, 236.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.7):
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.

Main Page

2008-02-28T20:40:16Z

TDragon: Updated for 8.02 release

WxWindowsQuickRef

2008-02-28T20:35:47Z

TDragon:

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\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.7'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.7-Setup.exe Click here to download the wxWidgets 2.8.7 sources for Windows] (wxMSW-2.8.7-Setup.exe; 12.0 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.7.03''', based on wxWidgets 2.8.7. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.7.03.exe?download Click here to download wxPack v2.8.7.03] (wxPack_v2.8.7.03.exe, 236.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.7):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2008-02-28T20:35:09Z

TDragon: Updated for 8.02 release

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\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 of Code::Blocks].

== 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.7'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.7-Setup.exe Click here to download the wxWidgets 2.8.7 sources for Windows] (wxMSW-2.8.7-Setup.exe; 12.0 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.7.03''', based on wxWidgets 2.8.7. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.7.03.exe?download Click here to download wxPack v2.8.7.03] (wxPack_v2.8.7.03.exe, 236.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.7):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-12-24T16:08:46Z

TDragon: /* Build wxWidgets */ Updated for wxWidgets 2.8.7

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.7'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.7-Setup.exe Click here to download the wxWidgets 2.8.7 sources for Windows] (wxMSW-2.8.7-Setup.exe; 12.0 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.7.03''', based on wxWidgets 2.8.7. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.7.03.exe?download Click here to download wxPack v2.8.7.03] (wxPack_v2.8.7.03.exe, 236.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.7):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-12-24T16:07:56Z

TDragon: /* wxPack */ Updated for wxPack 2.8.7.03

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.7'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.7-Setup.exe Click here to download the wxWidgets 2.8.7 sources for Windows] (wxMSW-2.8.7-Setup.exe; 12.0 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.7.03''', based on wxWidgets 2.8.7. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.7.03.exe?download Click here to download wxPack v2.8.7.03] (wxPack_v2.8.7.03.exe, 236.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.6):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-12-01T18:01:29Z

TDragon: /* wxWidgets Sources */ Updated to wx2.8.7

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.7'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.7-Setup.exe Click here to download the wxWidgets 2.8.7 sources for Windows] (wxMSW-2.8.7-Setup.exe; 12.0 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.6.05''', based on wxWidgets 2.8.6. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.6.05.exe?download Click here to download wxPack v2.8.6.05] (wxPack_v2.8.6.05.exe, 224.4 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.6):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-11-23T21:39:28Z

TDragon: /* wxPack */ Updated wxPack versions

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.6'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.6-Setup.exe Click here to download the wxWidgets 2.8.6 sources for Windows] (wxMSW-2.8.6-Setup.exe; 12.0 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.6.05''', based on wxWidgets 2.8.6. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.6.05.exe?download Click here to download wxPack v2.8.6.05] (wxPack_v2.8.6.05.exe, 224.4 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.6):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-10-19T14:00:38Z

TDragon: Updated for wxPack 2.8.6.01

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.6'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.6-Setup.exe Click here to download the wxWidgets 2.8.6 sources for Windows] (wxMSW-2.8.6-Setup.exe; 12.0 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.6.01''', based on wxWidgets 2.8.6. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.6.01.exe?download Click here to download wxPack v2.8.6.01] (wxPack_v2.8.6.01.exe, 237.5 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.6):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-10-03T12:39:00Z

TDragon: Updated for wxPack v2.8.5.01

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.6'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.6-Setup.exe Click here to download the wxWidgets 2.8.6 sources for Windows] (wxMSW-2.8.6-Setup.exe; 12.0 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.5.01''', based on wxWidgets 2.8.5. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.5.01.exe?download Click here to download wxPack v2.8.5.01] (wxPack_v2.8.5.01.exe, 233.6 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.6):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-10-03T12:37:26Z

TDragon: Updated for wx 2.8.6

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.6'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.6-Setup.exe Click here to download the wxWidgets 2.8.6 sources for Windows] (wxMSW-2.8.6-Setup.exe; 12.0 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.4.02''', based on wxWidgets 2.8.4. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.4.02.exe?download Click here to download wxPack v2.8.4.02] (wxPack_v2.8.4.02.exe, 222.7 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.6):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-09-22T16:41:18Z

TDragon: /* Download wxWidgets */ Added link to wxPack download page

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.5'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.5-Setup.exe Click here to download the wxWidgets 2.8.5 sources for Windows] (wxMSW-2.8.5-Setup.exe; 11.9 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.4.02''', based on wxWidgets 2.8.4. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.4.02.exe?download Click here to download wxPack v2.8.4.02] (wxPack_v2.8.4.02.exe, 222.7 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.5):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-09-22T16:39:17Z

TDragon: wxWidgets build options explanation moved and expanded

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.5'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.5-Setup.exe Click here to download the wxWidgets 2.8.5 sources for Windows] (wxMSW-2.8.5-Setup.exe; 11.9 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.4.02''', based on wxWidgets 2.8.4. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.4.02.exe?download Click here to download wxPack v2.8.4.02] (wxPack_v2.8.4.02.exe, 222.7 MB). '''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.5):
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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

WxWindowsQuickRef

2007-09-16T14:54:41Z

TDragon: Changed to use the wx installer download

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

by JohnE / TDragon (TDM)

'''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]). If using MinGW/GCC, 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:\MinGW\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
* '''Nightly build of Code::Blocks''' - You need to have successfully installed and run [/index.php/board,20.0.html a recent nightly build of Code::Blocks].

== 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.5'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.5-Setup.exe Click here to download the wxWidgets 2.8.5 sources for Windows] (wxMSW-2.8.5-Setup.exe; 11.9 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.4.02''', based on wxWidgets 2.8.4. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.4.02.exe?download Click here to download wxPack v2.8.4.02] (wxPack_v2.8.4.02.exe, 222.7 MB). '''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.5):
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".

=== wxWidgets build options explained ===
''What do the BUILD, SHARED, MONOLITHIC, and UNICODE options mean?''
* BUILD=release indicates that we want the faster and smaller release build of wxWidgets, as opposed to the heavyweight debug build (BUILD=debug). You can still debug your own programs that use the wxWidgets release build.
* SHARED=1 indicates that we want to use wxWidgets from a separate DLL instead of statically linking the wxWidgets code into every program. This saves time compiling, and saves space.
* MONOLITHIC=1 indicates that we want all of the wxWidgets code in a single library, rather than split up into separate component libraries. This merely makes the wxWidgets library easier to work with while developing.
* UNICODE=1 indicates that we want Unicode-compatible strings and language support in our programs. This should always be preferred except on pre-Win2k systems, where you must either install a separate Unicode library or build with UNICODE=0.
''Why are these options critically important?''

These options 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. If, for some reason, you want to use a debug wxWidgets build, select "Configure Advanced options" and then select "Use __WXDEBUG__ and Debug wxWidgets lib" 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.

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

User documentation

2007-09-15T20:57:37Z

TDragon: Added my new WxWindowsQuickRef under third-party libraries

[[Category:Code::Blocks Documentation]]
[[Category:User Documentation]]
__TOC__
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

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

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

== Third-party libraries ==

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

== User interface development ==

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