<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.codeblocks.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rickg22</id>
	<title>Code::Blocks - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.codeblocks.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rickg22"/>
	<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php/Special:Contributions/Rickg22"/>
	<updated>2026-05-02T11:05:27Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.0</generator>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=2197</id>
		<title>FAQ</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=2197"/>
		<updated>2006-01-19T21:49:27Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* My project should be compiled with a custom makefile. Is it possible with Code::Blocks? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General =&lt;br /&gt;
&lt;br /&gt;
== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==&lt;br /&gt;
&lt;br /&gt;
Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)&lt;br /&gt;
&lt;br /&gt;
== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==&lt;br /&gt;
&lt;br /&gt;
Since version 1.0-beta5, no it is not. Code::Blocks works with GNU &amp;quot;make&amp;quot; [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to &amp;quot;Project/Build options&amp;quot;, switch to the &amp;quot;Other&amp;quot; tab and select the build method you prefer.&lt;br /&gt;
&lt;br /&gt;
== What licence is Code::Blocks released under? ==&lt;br /&gt;
&lt;br /&gt;
GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])&lt;br /&gt;
&lt;br /&gt;
= Compiling =&lt;br /&gt;
&lt;br /&gt;
== What compiler can I use with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.&lt;br /&gt;
&lt;br /&gt;
As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5, DigitalMars Free Compiler., OpenWatcom and Small Device C Compiler (SDCC).&lt;br /&gt;
&lt;br /&gt;
== I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
A little documentation problem ^^;. The &amp;quot;default compiler&amp;quot; is usually GCC, so when you imported it with &amp;quot;the default compiler&amp;quot;, you told it to use GCC. To fix this situation, go to &amp;quot;Project&amp;quot;, &amp;quot;Build Options&amp;quot; and select VC++ Toolkit as your compiler.&lt;br /&gt;
&lt;br /&gt;
== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==&lt;br /&gt;
&lt;br /&gt;
''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''&lt;br /&gt;
&lt;br /&gt;
You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under &amp;quot;Settings/Configure plugins/Compiler&amp;quot; in the &amp;quot;Programs&amp;quot; tab...&lt;br /&gt;
Second, you have to add two additional compiler (include) dirs. Go to &amp;quot;Settings/Configure plugins/Compiler&amp;quot; and in the &amp;quot;Compiler dirs&amp;quot; tab add &amp;quot;dev-cpp\include\c++&amp;quot; and &amp;quot;dev-cpp\include\c++\mingw32&amp;quot; (substituting &amp;quot;dev-cpp&amp;quot; with the actual dev-cpp installation folder).&lt;br /&gt;
&lt;br /&gt;
== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==&lt;br /&gt;
&lt;br /&gt;
BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.&lt;br /&gt;
&lt;br /&gt;
== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Yes, you can. You need to change two different settings:&lt;br /&gt;
&lt;br /&gt;
a) In &amp;quot;Compiler Settings&amp;quot;, under the tab &amp;quot;Other&amp;quot;, there's a setting called &amp;quot;Build Method&amp;quot;. Choose &amp;quot;Work with makefiles&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
b) In your project's Properties, you can choose to use a makefile. Check &amp;quot;This is a custom makefile&amp;quot; (WARNING! if you forget to check, the makefile will be OVERWRITTEN!)&lt;br /&gt;
&lt;br /&gt;
And that's it! :)&lt;br /&gt;
&lt;br /&gt;
== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==&lt;br /&gt;
&lt;br /&gt;
Click on &amp;quot;Project/Build options&amp;quot; and select the compiler you want for your project/target.&lt;br /&gt;
&lt;br /&gt;
== When compiling a wxWidgets project, I get several &amp;quot;variable 'vtable for xxxx' can't be auto-imported&amp;quot;. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
You need to add WXUSINGDLL in &amp;quot;Project-&amp;gt;Build options-&amp;gt;Compiler #defines&amp;quot; and rebuild your project (or create a new project and use the &amp;quot;Using wxWidgets DLL&amp;quot; project option which adds &amp;quot;-DWXUSINGDLL&amp;quot; to Project-&amp;gt;Build options-&amp;gt;Other options).&lt;br /&gt;
Other errors with the same resolution are:&lt;br /&gt;
'unresolved external symbol &amp;quot;char const * const wxEmptyString&amp;quot; (?wxEmptyString@@3PBDB)' or similar.&lt;br /&gt;
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.&lt;br /&gt;
&lt;br /&gt;
== I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ==&lt;br /&gt;
&lt;br /&gt;
sorry, no fix for your problem...&lt;br /&gt;
&lt;br /&gt;
Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which are coming with Visual C++ (VC) which isn't free, unfortunately.&lt;br /&gt;
&lt;br /&gt;
Try buying a full-fledged VC++, or even better, download MinGW :)&lt;br /&gt;
&lt;br /&gt;
The libraries that can be obtained free of charge are:&lt;br /&gt;
&lt;br /&gt;
Paths:&lt;br /&gt;
 (VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib&lt;br /&gt;
 (PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib&lt;br /&gt;
 (NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib&lt;br /&gt;
&lt;br /&gt;
C runtime libs:&lt;br /&gt;
 LIBC.LIB 	Single-threaded, static link                                          (VCT3, NSDK)&lt;br /&gt;
 LIBCMT.LIB 	Multithreaded, static link                                            (VCT3, NSDK)&lt;br /&gt;
 MSVCRT.LIB 	Multithreaded, dynamic link (import library for MSVCR71.DLL)          (NSDK)&lt;br /&gt;
 LIBCD.LIB 	Single-threaded, static link (debug)                                  (VCT3, NSDK)&lt;br /&gt;
 LIBCMTD.LIB 	Multithreaded, static link (debug)                                    (NSDK)&lt;br /&gt;
 MSVCRTD.LIB 	Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)&lt;br /&gt;
&lt;br /&gt;
C++ libs:&lt;br /&gt;
 LIBCP.LIB 	Single-threaded, static link                                          (VCT3, PSDK)&lt;br /&gt;
 LIBCPMT.LIB 	Multithreaded, static link                                            (VCT3)&lt;br /&gt;
 MSVCPRT.LIB 	Multithreaded, dynamic link (import library for MSVCP71.dll)          (none)&lt;br /&gt;
 LIBCPD.LIB 	Single-threaded, static link (debug)                                  (VCT3)&lt;br /&gt;
 LIBCPMTD.LIB 	Multithreaded, static link (debug)                                    (none)&lt;br /&gt;
 MSVCPRTD.LIB 	Multithreaded, dynamic link (import library for MSVCP71D.DLL) (debug) (none)&lt;br /&gt;
&lt;br /&gt;
Try setting the library linker directories to:&lt;br /&gt;
 C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib&lt;br /&gt;
 C:\Program Files\Microsoft Platform SDK\Lib&lt;br /&gt;
 C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib&lt;br /&gt;
in that order.&lt;br /&gt;
&lt;br /&gt;
The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory.  Not sure if these would work on 32-bit windows, however, they may if they are&lt;br /&gt;
meant to work in 32-bit compatibility mode on the 64-bit processors.  Worth a try.  Otherwise, you&lt;br /&gt;
can link statically to the C++ library instead of using MSVCP71.dll.  If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed.  Search google for &amp;quot;exports.sed&amp;quot; for detailed steps.&lt;br /&gt;
&lt;br /&gt;
See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp&lt;br /&gt;
&lt;br /&gt;
See also: http://sapdb.2scale.net/moin.cgi/MS_20C_2b_2b_20Toolkit&lt;br /&gt;
&lt;br /&gt;
== Where are the libraries for the OpenGL / SDL / etc. projects? ==&lt;br /&gt;
&lt;br /&gt;
They're not bundled. The templates were provided for your convenience, but you need to download the libraries on your own.&lt;br /&gt;
In common terms, &amp;quot;batteries not included&amp;quot; :)&lt;br /&gt;
&lt;br /&gt;
== Is it possible to use Visual C++ 6.0 with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
As they say in ##C++ on FreeNode:&amp;lt;br&amp;gt;&lt;br /&gt;
cylon&amp;gt; msvc++6 is not a C++ compiler. It was made before the C++ standard, so it compiles some language that isn't C++. Upgrade.&lt;br /&gt;
&lt;br /&gt;
== I got this error when compiling: Symbol &amp;quot;isascii&amp;quot; was not found in &amp;quot;codeblocks.dll&amp;quot; ==&lt;br /&gt;
Make sure you didn't mix up the MSVC headers or libs with the MinGW ones.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Announcement_for_plugins/patches&amp;diff=424</id>
		<title>Announcement for plugins/patches</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Announcement_for_plugins/patches&amp;diff=424"/>
		<updated>2005-12-15T20:01:08Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Lexer/Template announcement */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== HowTo announce a new plugin/patch or similar ===&lt;br /&gt;
&lt;br /&gt;
''Please read carefully:''&lt;br /&gt;
&lt;br /&gt;
This WiKi section is to announce:&lt;br /&gt;
* a new plugin that is '''not''' within the contrib folder of the SVN repository&lt;br /&gt;
* a patch that is '''not''' a bugfix or similar and/or will '''not''' be applied to the SVN repository (e.g. because it's very specific)&lt;br /&gt;
* a new lexer/template that is '''not''' completed or approved and/or will '''not''' be added to the SVN&lt;br /&gt;
&lt;br /&gt;
If a plugin/patch/lexer/template is moved to the repository don't forget to remove it from here! This section is intended to '''collect''' the information about available plugins/patches/lexerers/templates in one place. So the announcement should be short and clear. It should (however) include at least the following content:&lt;br /&gt;
* Name of the plugin/patch/lexer/template and purpose&amp;lt;BR&amp;gt;&lt;br /&gt;
* Version (state) and date of last update (or release in the first place)&amp;lt;BR&amp;gt;&lt;br /&gt;
* Link to a thread (to be created) in the developers (plugin) forum for discussion of features, bugs, wishlist etc.&amp;lt;BR&amp;gt;&lt;br /&gt;
* A link where the '''most up-to-date''' version can be downloaded (e.g. in the forum).&amp;lt;BR&amp;gt;&lt;br /&gt;
The best way maybe to copy the section from the '''template''' plugin/patch/lexer/template and update it with your information. This will ensure consistency in the best way!&lt;br /&gt;
&lt;br /&gt;
=== Patch announcements ===&lt;br /&gt;
&lt;br /&gt;
So far there are no new patches.&lt;br /&gt;
&lt;br /&gt;
* [[Template for patch announcement]] (Read this before posting a new patch!)&lt;br /&gt;
&lt;br /&gt;
=== Plugin announcements ===&lt;br /&gt;
&lt;br /&gt;
These are the user-contributed plugins:&lt;br /&gt;
&lt;br /&gt;
* [[Replace in Files]] (MortenMacFly)&lt;br /&gt;
* [[Tab versus Space]] (MortenMacFly)&lt;br /&gt;
* [[Template for plugin announcement]] (Read this before posting a new plugin!)&lt;br /&gt;
&lt;br /&gt;
=== Lexer/Templates announcements ===&lt;br /&gt;
&lt;br /&gt;
These are the user-contributed Lexer / Templates:&lt;br /&gt;
&lt;br /&gt;
* [[Matlab Lexer]] (MortenMacFly)&lt;br /&gt;
* [[FLTK template]] (MortenMacFly)&lt;br /&gt;
* [[SmartWin template]] (MortenMacFly)&lt;br /&gt;
* [[Template for lexer/template announcement]] (Read this before posting a new lexer/template!)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Announcement_for_plugins/patches&amp;diff=414</id>
		<title>Announcement for plugins/patches</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Announcement_for_plugins/patches&amp;diff=414"/>
		<updated>2005-12-15T20:00:30Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Plugin announcements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== HowTo announce a new plugin/patch or similar ===&lt;br /&gt;
&lt;br /&gt;
''Please read carefully:''&lt;br /&gt;
&lt;br /&gt;
This WiKi section is to announce:&lt;br /&gt;
* a new plugin that is '''not''' within the contrib folder of the SVN repository&lt;br /&gt;
* a patch that is '''not''' a bugfix or similar and/or will '''not''' be applied to the SVN repository (e.g. because it's very specific)&lt;br /&gt;
* a new lexer/template that is '''not''' completed or approved and/or will '''not''' be added to the SVN&lt;br /&gt;
&lt;br /&gt;
If a plugin/patch/lexer/template is moved to the repository don't forget to remove it from here! This section is intended to '''collect''' the information about available plugins/patches/lexerers/templates in one place. So the announcement should be short and clear. It should (however) include at least the following content:&lt;br /&gt;
* Name of the plugin/patch/lexer/template and purpose&amp;lt;BR&amp;gt;&lt;br /&gt;
* Version (state) and date of last update (or release in the first place)&amp;lt;BR&amp;gt;&lt;br /&gt;
* Link to a thread (to be created) in the developers (plugin) forum for discussion of features, bugs, wishlist etc.&amp;lt;BR&amp;gt;&lt;br /&gt;
* A link where the '''most up-to-date''' version can be downloaded (e.g. in the forum).&amp;lt;BR&amp;gt;&lt;br /&gt;
The best way maybe to copy the section from the '''template''' plugin/patch/lexer/template and update it with your information. This will ensure consistency in the best way!&lt;br /&gt;
&lt;br /&gt;
=== Patch announcements ===&lt;br /&gt;
&lt;br /&gt;
So far there are no new patches.&lt;br /&gt;
&lt;br /&gt;
* [[Template for patch announcement]] (Read this before posting a new patch!)&lt;br /&gt;
&lt;br /&gt;
=== Plugin announcements ===&lt;br /&gt;
&lt;br /&gt;
These are the user-contributed plugins:&lt;br /&gt;
&lt;br /&gt;
* [[Replace in Files]] (MortenMacFly)&lt;br /&gt;
* [[Tab versus Space]] (MortenMacFly)&lt;br /&gt;
* [[Template for plugin announcement]] (Read this before posting a new plugin!)&lt;br /&gt;
&lt;br /&gt;
=== Lexer/Template announcement ===&lt;br /&gt;
&lt;br /&gt;
* [[Template for lexer/template announcement]] (Read this before posting a new lexer/template!)&lt;br /&gt;
* [[Matlab Lexer]] (MortenMacFly)&lt;br /&gt;
* [[FLTK template]] (MortenMacFly)&lt;br /&gt;
* [[SmartWin template]] (MortenMacFly)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Announcement_for_plugins/patches&amp;diff=413</id>
		<title>Announcement for plugins/patches</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Announcement_for_plugins/patches&amp;diff=413"/>
		<updated>2005-12-15T19:59:57Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Plugin announcement announcement */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== HowTo announce a new plugin/patch or similar ===&lt;br /&gt;
&lt;br /&gt;
''Please read carefully:''&lt;br /&gt;
&lt;br /&gt;
This WiKi section is to announce:&lt;br /&gt;
* a new plugin that is '''not''' within the contrib folder of the SVN repository&lt;br /&gt;
* a patch that is '''not''' a bugfix or similar and/or will '''not''' be applied to the SVN repository (e.g. because it's very specific)&lt;br /&gt;
* a new lexer/template that is '''not''' completed or approved and/or will '''not''' be added to the SVN&lt;br /&gt;
&lt;br /&gt;
If a plugin/patch/lexer/template is moved to the repository don't forget to remove it from here! This section is intended to '''collect''' the information about available plugins/patches/lexerers/templates in one place. So the announcement should be short and clear. It should (however) include at least the following content:&lt;br /&gt;
* Name of the plugin/patch/lexer/template and purpose&amp;lt;BR&amp;gt;&lt;br /&gt;
* Version (state) and date of last update (or release in the first place)&amp;lt;BR&amp;gt;&lt;br /&gt;
* Link to a thread (to be created) in the developers (plugin) forum for discussion of features, bugs, wishlist etc.&amp;lt;BR&amp;gt;&lt;br /&gt;
* A link where the '''most up-to-date''' version can be downloaded (e.g. in the forum).&amp;lt;BR&amp;gt;&lt;br /&gt;
The best way maybe to copy the section from the '''template''' plugin/patch/lexer/template and update it with your information. This will ensure consistency in the best way!&lt;br /&gt;
&lt;br /&gt;
=== Patch announcements ===&lt;br /&gt;
&lt;br /&gt;
So far there are no new patches.&lt;br /&gt;
&lt;br /&gt;
* [[Template for patch announcement]] (Read this before posting a new patch!)&lt;br /&gt;
&lt;br /&gt;
=== Plugin announcements ===&lt;br /&gt;
&lt;br /&gt;
These are the following user-contributed plugins:&lt;br /&gt;
&lt;br /&gt;
* [[Replace in Files]] (MortenMacFly)&lt;br /&gt;
* [[Tab versus Space]] (MortenMacFly)&lt;br /&gt;
* [[Template for plugin announcement]] (Read this before posting a new plugin!)&lt;br /&gt;
&lt;br /&gt;
=== Lexer/Template announcement ===&lt;br /&gt;
&lt;br /&gt;
* [[Template for lexer/template announcement]] (Read this before posting a new lexer/template!)&lt;br /&gt;
* [[Matlab Lexer]] (MortenMacFly)&lt;br /&gt;
* [[FLTK template]] (MortenMacFly)&lt;br /&gt;
* [[SmartWin template]] (MortenMacFly)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Announcement_for_plugins/patches&amp;diff=412</id>
		<title>Announcement for plugins/patches</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Announcement_for_plugins/patches&amp;diff=412"/>
		<updated>2005-12-15T19:59:21Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Patch announcement */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== HowTo announce a new plugin/patch or similar ===&lt;br /&gt;
&lt;br /&gt;
''Please read carefully:''&lt;br /&gt;
&lt;br /&gt;
This WiKi section is to announce:&lt;br /&gt;
* a new plugin that is '''not''' within the contrib folder of the SVN repository&lt;br /&gt;
* a patch that is '''not''' a bugfix or similar and/or will '''not''' be applied to the SVN repository (e.g. because it's very specific)&lt;br /&gt;
* a new lexer/template that is '''not''' completed or approved and/or will '''not''' be added to the SVN&lt;br /&gt;
&lt;br /&gt;
If a plugin/patch/lexer/template is moved to the repository don't forget to remove it from here! This section is intended to '''collect''' the information about available plugins/patches/lexerers/templates in one place. So the announcement should be short and clear. It should (however) include at least the following content:&lt;br /&gt;
* Name of the plugin/patch/lexer/template and purpose&amp;lt;BR&amp;gt;&lt;br /&gt;
* Version (state) and date of last update (or release in the first place)&amp;lt;BR&amp;gt;&lt;br /&gt;
* Link to a thread (to be created) in the developers (plugin) forum for discussion of features, bugs, wishlist etc.&amp;lt;BR&amp;gt;&lt;br /&gt;
* A link where the '''most up-to-date''' version can be downloaded (e.g. in the forum).&amp;lt;BR&amp;gt;&lt;br /&gt;
The best way maybe to copy the section from the '''template''' plugin/patch/lexer/template and update it with your information. This will ensure consistency in the best way!&lt;br /&gt;
&lt;br /&gt;
=== Patch announcements ===&lt;br /&gt;
&lt;br /&gt;
So far there are no new patches.&lt;br /&gt;
&lt;br /&gt;
* [[Template for patch announcement]] (Read this before posting a new patch!)&lt;br /&gt;
&lt;br /&gt;
=== Plugin announcement announcement ===&lt;br /&gt;
&lt;br /&gt;
* [[Template for plugin announcement]] (Read this before posting a new plugin!)&lt;br /&gt;
* [[Replace in Files]] (MortenMacFly)&lt;br /&gt;
* [[Tab versus Space]] (MortenMacFly)&lt;br /&gt;
&lt;br /&gt;
=== Lexer/Template announcement ===&lt;br /&gt;
&lt;br /&gt;
* [[Template for lexer/template announcement]] (Read this before posting a new lexer/template!)&lt;br /&gt;
* [[Matlab Lexer]] (MortenMacFly)&lt;br /&gt;
* [[FLTK template]] (MortenMacFly)&lt;br /&gt;
* [[SmartWin template]] (MortenMacFly)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux&amp;diff=343</id>
		<title>Installing Code::Blocks from source on Linux</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux&amp;diff=343"/>
		<updated>2005-11-22T17:45:08Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* wxGTK-2.4.2 installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
&lt;br /&gt;
In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.6.1 or later) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.&lt;br /&gt;
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!&lt;br /&gt;
Let me stress it here, while it's early: &amp;lt;u&amp;gt;GTK2 is required&amp;lt;/u&amp;gt;, not GTK1, for Code::Blocks to be operational.&lt;br /&gt;
&lt;br /&gt;
All the instructions below, assume an existing directory named &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt;. If you 'll be using a different one, adjust the path to match.&lt;br /&gt;
As a first step create this directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;mkdir ~/devel&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===wxGTK-2.4.2 installation===&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT NOTICE: Since 1.0RC2, you need wxGTK-2.6 to successfully compile CodeBlocks, so this part of the article no longer applies, and needs to be updated.'''&lt;br /&gt;
&lt;br /&gt;
====Getting wxGTK-2.4.2====&lt;br /&gt;
&lt;br /&gt;
Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the &amp;quot;Download&amp;quot; button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Uncompressing the wxGTK sources====&lt;br /&gt;
&lt;br /&gt;
After the download finishes, switch to &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now, untar the wxGTK sources:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;tar zxf wxGTK-2.4.2.tar.gz&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;tar jxf wxGTK-2.4.2.tar.bz2&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
depending on which file you downloaded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Patching wxGTK=====&lt;br /&gt;
&lt;br /&gt;
Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.&lt;br /&gt;
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.&lt;br /&gt;
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)&lt;br /&gt;
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp&lt;br /&gt;
--- wxGTK-2.4.2/src/gtk/menu.cpp	2003-09-21 13:31:57.000000000 +0200&lt;br /&gt;
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp	2004-03-29 14:53:34.000000000 +0200&lt;br /&gt;
@@ -30,13 +30,13 @@&lt;br /&gt;
 #ifdef __WXGTK20__&lt;br /&gt;
     #include &amp;lt;glib-object.h&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
-    #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))&lt;br /&gt;
-    #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))&lt;br /&gt;
+    #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))&lt;br /&gt;
+    #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))&lt;br /&gt;
     #define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)&lt;br /&gt;
 &lt;br /&gt;
-    #define ACCEL_OBJECT        GObject&lt;br /&gt;
+    #define ACCEL_OBJECT        GtkWindow&lt;br /&gt;
     #define ACCEL_OBJECTS(a)    (a)-&amp;gt;acceleratables&lt;br /&gt;
-    #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)&lt;br /&gt;
+    #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)&lt;br /&gt;
 #else // GTK+ 1.x&lt;br /&gt;
     #define ACCEL_OBJECT        GtkObject&lt;br /&gt;
     #define ACCEL_OBJECTS(a)    (a)-&amp;gt;attach_objects&lt;br /&gt;
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp&lt;br /&gt;
--- wxGTK-2.4.2/src/gtk/settings.cpp	2003-09-21 13:31:57.000000000 +0200&lt;br /&gt;
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp	2004-03-29 15:15:35.000000000 +0200&lt;br /&gt;
@@ -340,8 +340,8 @@&lt;br /&gt;
                 }  &lt;br /&gt;
                 else  &lt;br /&gt;
                 {  &lt;br /&gt;
-                    const gchar *font_name =&lt;br /&gt;
-                        _gtk_rc_context_get_default_font_name(gtk_settings_get_default());&lt;br /&gt;
+                    gchar *font_name;&lt;br /&gt;
+                    g_object_get(gtk_settings_get_default(), &amp;quot;gtk-font-name&amp;quot;, &amp;amp;font_name, NULL);&lt;br /&gt;
                     g_systemFont = new wxFont(wxString::FromAscii(font_name));&lt;br /&gt;
                 }  &lt;br /&gt;
                 gtk_widget_destroy( widget );&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save the file as &amp;lt;tt&amp;gt;~/devel/gtk-2.4-fix.patch&amp;lt;/tt&amp;gt; and apply it by issuing:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&lt;br /&gt;
patch -Np0 -i gtk-2.4-fix.patch&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now we can build wxGTK!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Building wxGTK-2.4.2====&lt;br /&gt;
&lt;br /&gt;
Issue the following commands to build wxGTK-2.4.2:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel/wxGTK-2.4.2&lt;br /&gt;
./configure --enable-gtk2&lt;br /&gt;
make&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.&lt;br /&gt;
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;su -c &amp;quot;make install&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The above command will ask you for the root's password (you &amp;lt;u&amp;gt;are&amp;lt;/u&amp;gt; working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.&lt;br /&gt;
&lt;br /&gt;
The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd contrib/src/stc&lt;br /&gt;
make&lt;br /&gt;
su -c &amp;quot;make install&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ../xrc&lt;br /&gt;
make&lt;br /&gt;
su -c &amp;quot;make install&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;NOTE:&amp;lt;/u&amp;gt; ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''&lt;br /&gt;
&lt;br /&gt;
That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.&lt;br /&gt;
You 're now ready to download and build Code::Blocks - i.e. the easy part :)&lt;br /&gt;
&lt;br /&gt;
====wxWidgets 2.6.1 build====&lt;br /&gt;
&lt;br /&gt;
In case you want to use wxGTK 2.6.1 instead.&lt;br /&gt;
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).&lt;br /&gt;
&lt;br /&gt;
The documentation says the default is for gtk2 to use unicode and wx &amp;gt; 2.5 to build as a monolithic library.  This doesn't appear to be the case, so these flags are passed to configure.&lt;br /&gt;
&lt;br /&gt;
 mkdir build_gtk2_shared_monolithic_unicode&lt;br /&gt;
 cd build_gtk2_shared_monolithic_unicode&lt;br /&gt;
 ../configure --prefix=/opt/wx/2.6 \&lt;br /&gt;
        --enable-xrc \&lt;br /&gt;
        --enable-monolithic \&lt;br /&gt;
        --enable-unicode&lt;br /&gt;
 make&lt;br /&gt;
 make -C contrib/src/stc&lt;br /&gt;
 su&lt;br /&gt;
 make install&lt;br /&gt;
 make -C contrib/src/stc install&lt;br /&gt;
 exit&lt;br /&gt;
&lt;br /&gt;
(Note: it's not necessary to make or install stc if you're compiling cvs HEAD or Code::Blocks newer than RC1)&lt;br /&gt;
&lt;br /&gt;
add /opt/wx/2.6/bin to the PATH (if you're shell is bash then edit /etc/profile or ~/.bash_profile).  an example PATH&lt;br /&gt;
 export PATH=/usr/bin:/opt/wx/2.6/bin:$PATH&lt;br /&gt;
(*Note// &lt;br /&gt;
on Ubuntu Hoary it was necessary to check &amp;quot;Run command as login shell&amp;quot; &lt;br /&gt;
in the gnome-terminal profile-settings, &lt;br /&gt;
otherwise the PATH changes are not available in a gnome-terminal window. &lt;br /&gt;
//tiwag 051008*)&lt;br /&gt;
&lt;br /&gt;
add /opt/wx/2.6/lib to /etc/ld.so.conf (nano /etc/ld.so.conf)&lt;br /&gt;
then run:&lt;br /&gt;
 ldconfig&lt;br /&gt;
 source /etc/profile&lt;br /&gt;
&lt;br /&gt;
That's it.  Now the linker will look in /opt/wx/2.6/lib for wx libraries and you will have a monolithic shared library unicode build.&lt;br /&gt;
&lt;br /&gt;
To check that things are working, type:&lt;br /&gt;
 wx-config --prefix&lt;br /&gt;
which should give you /opt/wx/2.6&lt;br /&gt;
 wx-config --libs&lt;br /&gt;
which should have at least&lt;br /&gt;
 -L/opt/wx/2.6/lib -lwx_gtk2-2.6&lt;br /&gt;
but can contain other flags as well.&lt;br /&gt;
 which wx-config&lt;br /&gt;
should return /opt/wx/2.6/bin/wx-config&lt;br /&gt;
&lt;br /&gt;
===Code::Blocks installation===&lt;br /&gt;
&lt;br /&gt;
====Downloading Code::Blocks====&lt;br /&gt;
&lt;br /&gt;
You can get Code::Blocks source code in one of two ways:&lt;br /&gt;
* Download the latest source package, or&lt;br /&gt;
* Get the latest sources from the CVS repository.&lt;br /&gt;
Both methods, are described below.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Downloading the latest source package=====&lt;br /&gt;
&lt;br /&gt;
Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the &amp;quot; Code::Blocks IDE version 1.0rc2 source code (tarball)&amp;quot; codeblocks-1.0rc2.tar.gz.&lt;br /&gt;
Save this file in &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt; and then untar it:&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&lt;br /&gt;
tar zxf codeblocks-1.0rc2.tar.gz&amp;lt;/pre&amp;gt;&lt;br /&gt;
This will create the directory &amp;lt;tt&amp;gt;~/devel/codeblocks-1.0rc2&amp;lt;/tt&amp;gt;.&lt;br /&gt;
Change to the source code directory, by issuing the following command:&lt;br /&gt;
&amp;lt;pre&amp;gt;cd codeblocks-1.0rc2&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====Getting the latest sources from CVS=====&lt;br /&gt;
&lt;br /&gt;
For the following to work, you need to have the &amp;lt;tt&amp;gt;cvs&amp;lt;/tt&amp;gt; command line client installed on your system.&lt;br /&gt;
First you need to login to the CVS server:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When asked for a password, press enter.&lt;br /&gt;
Now, just checkout (i.e. download) the sources from the repository:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&lt;br /&gt;
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will create the directory &amp;lt;tt&amp;gt;codeblocks&amp;lt;/tt&amp;gt;.&lt;br /&gt;
Change to the source code directory, by issuing the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd codeblocks&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Building Code::Blocks RC2 and CVS====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you're compiling the cvs HEAD verions of CodeBlocks (or future versions) then the unix build has switched to autotools.  So first build wxWidgets as described above and then build CodeBlocks as follows:&lt;br /&gt;
&lt;br /&gt;
 ./bootstrap&lt;br /&gt;
&lt;br /&gt;
This sets up the configure script and it's dependencies.  It only needs to be run once (after downloading the source from cvs).  '''If you get errors like:'''&lt;br /&gt;
 aclocal:configure.in:61: warning: macro `AM_OPTIONS_WXCONFIG' not found in library&lt;br /&gt;
Then aclocal is having trouble finding the wxWidgets .m4 files.  You can do one of two things:&lt;br /&gt;
To just get bootstrap to find the path this time do:&lt;br /&gt;
 export ACLOCAL_FLAGS=&amp;quot;--acdir=`wx-config --prefix`/share/aclocal&amp;quot;&lt;br /&gt;
To change the aclocal search path more permanently do:&lt;br /&gt;
 echo `wx-config --prefix`/share/aclocal &amp;gt;&amp;gt; /usr/share/aclocal/dirlist&lt;br /&gt;
Then aclocal will also search somewhere like /opt/wx/2.6/share/aclocal&lt;br /&gt;
&lt;br /&gt;
(*Note// '''If you run ./bootstrap and get errors like''':&lt;br /&gt;
 : bad interpreter: File not found&lt;br /&gt;
then there exists a problem with DOS line-endings. i had this error after i tried to build a  codeblocks from sources which were checked out with cvs on a windows machine. After i checked out a fresh copy of codeblocks from cvs under Ubuntu linux (see above topic: Downloading the latest source package fom CVS), all errors were gone. &lt;br /&gt;
//tiwag 051008*)&lt;br /&gt;
&lt;br /&gt;
Once you've run the bootstrap script, installing is as simple as:&lt;br /&gt;
 ./configure&lt;br /&gt;
 make&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
To uninstall you can later run:&lt;br /&gt;
 make uninstall&lt;br /&gt;
&lt;br /&gt;
If you want to recompile everything, first run:&lt;br /&gt;
 make clean&lt;br /&gt;
and then follow the above sequence for installing.&lt;br /&gt;
&lt;br /&gt;
By default, CodeBlocks will install to /usr/local.  If you want it in its own tree (so you can have multiple versions of CodeBlocks, each in its own subdirectory of /opt) replace the above ./configure command with:&lt;br /&gt;
 ./configure --prefix=/opt/codeblocks-cvs&lt;br /&gt;
or similar.  Then you can later install a different build like:&lt;br /&gt;
 ./configure --prefix=/opt/codeblocks2-cvs&lt;br /&gt;
followed by 'make &amp;amp;&amp;amp; make install' as usual.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Building Code::Blocks RC1 and former====&lt;br /&gt;
&lt;br /&gt;
To build Code::Blocks all you have to do now is type:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;make -f Makefile.unix&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will build everything: the application and the plugins. The final step is to update the working environment for your system:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;make -f Makefile.unix update&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following notes about converting the line endings does '''not''' apply to the CVS Version! The &amp;quot;update&amp;quot; script included there works just fine.&lt;br /&gt;
&lt;br /&gt;
'''Important note:''' Don't run that final make yet! The &amp;quot;update&amp;quot; script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:&lt;br /&gt;
&lt;br /&gt;
To install it in Gentoo, do:&lt;br /&gt;
&lt;br /&gt;
 # emerge -av dos2unix&lt;br /&gt;
&lt;br /&gt;
In Debian and Ubuntu, do (as root, or using sudo etc.):&lt;br /&gt;
&lt;br /&gt;
 # apt-get install sysutils&lt;br /&gt;
&lt;br /&gt;
This will install dos2unix. Now we are ready to convert the script.&lt;br /&gt;
 # dos2unix -n update update.unix&lt;br /&gt;
 # chmod +x update.unix&lt;br /&gt;
 # ./update.unix&lt;br /&gt;
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.&lt;br /&gt;
&lt;br /&gt;
OK. Now that the update script is converted to unix format, you can run the final make:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;make -f Makefile.unix update&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated &amp;lt;tt&amp;gt;run.sh&amp;lt;/tt&amp;gt; script in the &amp;lt;tt&amp;gt;output&amp;lt;/tt&amp;gt; subdir:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;output/run.sh&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)&lt;br /&gt;
&lt;br /&gt;
Enjoy!&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux&amp;diff=337</id>
		<title>Installing Code::Blocks from source on Linux</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux&amp;diff=337"/>
		<updated>2005-11-22T17:41:47Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
&lt;br /&gt;
In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.6.1 or later) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.&lt;br /&gt;
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!&lt;br /&gt;
Let me stress it here, while it's early: &amp;lt;u&amp;gt;GTK2 is required&amp;lt;/u&amp;gt;, not GTK1, for Code::Blocks to be operational.&lt;br /&gt;
&lt;br /&gt;
All the instructions below, assume an existing directory named &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt;. If you 'll be using a different one, adjust the path to match.&lt;br /&gt;
As a first step create this directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;mkdir ~/devel&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===wxGTK-2.4.2 installation===&lt;br /&gt;
====Getting wxGTK-2.4.2====&lt;br /&gt;
&lt;br /&gt;
Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the &amp;quot;Download&amp;quot; button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Uncompressing the wxGTK sources====&lt;br /&gt;
&lt;br /&gt;
After the download finishes, switch to &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now, untar the wxGTK sources:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;tar zxf wxGTK-2.4.2.tar.gz&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;tar jxf wxGTK-2.4.2.tar.bz2&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
depending on which file you downloaded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Patching wxGTK=====&lt;br /&gt;
&lt;br /&gt;
Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.&lt;br /&gt;
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.&lt;br /&gt;
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)&lt;br /&gt;
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp&lt;br /&gt;
--- wxGTK-2.4.2/src/gtk/menu.cpp	2003-09-21 13:31:57.000000000 +0200&lt;br /&gt;
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp	2004-03-29 14:53:34.000000000 +0200&lt;br /&gt;
@@ -30,13 +30,13 @@&lt;br /&gt;
 #ifdef __WXGTK20__&lt;br /&gt;
     #include &amp;lt;glib-object.h&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
-    #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))&lt;br /&gt;
-    #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))&lt;br /&gt;
+    #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))&lt;br /&gt;
+    #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))&lt;br /&gt;
     #define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)&lt;br /&gt;
 &lt;br /&gt;
-    #define ACCEL_OBJECT        GObject&lt;br /&gt;
+    #define ACCEL_OBJECT        GtkWindow&lt;br /&gt;
     #define ACCEL_OBJECTS(a)    (a)-&amp;gt;acceleratables&lt;br /&gt;
-    #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)&lt;br /&gt;
+    #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)&lt;br /&gt;
 #else // GTK+ 1.x&lt;br /&gt;
     #define ACCEL_OBJECT        GtkObject&lt;br /&gt;
     #define ACCEL_OBJECTS(a)    (a)-&amp;gt;attach_objects&lt;br /&gt;
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp&lt;br /&gt;
--- wxGTK-2.4.2/src/gtk/settings.cpp	2003-09-21 13:31:57.000000000 +0200&lt;br /&gt;
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp	2004-03-29 15:15:35.000000000 +0200&lt;br /&gt;
@@ -340,8 +340,8 @@&lt;br /&gt;
                 }  &lt;br /&gt;
                 else  &lt;br /&gt;
                 {  &lt;br /&gt;
-                    const gchar *font_name =&lt;br /&gt;
-                        _gtk_rc_context_get_default_font_name(gtk_settings_get_default());&lt;br /&gt;
+                    gchar *font_name;&lt;br /&gt;
+                    g_object_get(gtk_settings_get_default(), &amp;quot;gtk-font-name&amp;quot;, &amp;amp;font_name, NULL);&lt;br /&gt;
                     g_systemFont = new wxFont(wxString::FromAscii(font_name));&lt;br /&gt;
                 }  &lt;br /&gt;
                 gtk_widget_destroy( widget );&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save the file as &amp;lt;tt&amp;gt;~/devel/gtk-2.4-fix.patch&amp;lt;/tt&amp;gt; and apply it by issuing:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&lt;br /&gt;
patch -Np0 -i gtk-2.4-fix.patch&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now we can build wxGTK!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Building wxGTK-2.4.2====&lt;br /&gt;
&lt;br /&gt;
Issue the following commands to build wxGTK-2.4.2:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel/wxGTK-2.4.2&lt;br /&gt;
./configure --enable-gtk2&lt;br /&gt;
make&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.&lt;br /&gt;
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;su -c &amp;quot;make install&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The above command will ask you for the root's password (you &amp;lt;u&amp;gt;are&amp;lt;/u&amp;gt; working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.&lt;br /&gt;
&lt;br /&gt;
The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd contrib/src/stc&lt;br /&gt;
make&lt;br /&gt;
su -c &amp;quot;make install&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ../xrc&lt;br /&gt;
make&lt;br /&gt;
su -c &amp;quot;make install&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;NOTE:&amp;lt;/u&amp;gt; ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''&lt;br /&gt;
&lt;br /&gt;
That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.&lt;br /&gt;
You 're now ready to download and build Code::Blocks - i.e. the easy part :)&lt;br /&gt;
&lt;br /&gt;
====wxWidgets 2.6.1 build====&lt;br /&gt;
&lt;br /&gt;
In case you want to use wxGTK 2.6.1 instead.&lt;br /&gt;
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).&lt;br /&gt;
&lt;br /&gt;
The documentation says the default is for gtk2 to use unicode and wx &amp;gt; 2.5 to build as a monolithic library.  This doesn't appear to be the case, so these flags are passed to configure.&lt;br /&gt;
&lt;br /&gt;
 mkdir build_gtk2_shared_monolithic_unicode&lt;br /&gt;
 cd build_gtk2_shared_monolithic_unicode&lt;br /&gt;
 ../configure --prefix=/opt/wx/2.6 \&lt;br /&gt;
        --enable-xrc \&lt;br /&gt;
        --enable-monolithic \&lt;br /&gt;
        --enable-unicode&lt;br /&gt;
 make&lt;br /&gt;
 make -C contrib/src/stc&lt;br /&gt;
 su&lt;br /&gt;
 make install&lt;br /&gt;
 make -C contrib/src/stc install&lt;br /&gt;
 exit&lt;br /&gt;
&lt;br /&gt;
(Note: it's not necessary to make or install stc if you're compiling cvs HEAD or Code::Blocks newer than RC1)&lt;br /&gt;
&lt;br /&gt;
add /opt/wx/2.6/bin to the PATH (if you're shell is bash then edit /etc/profile or ~/.bash_profile).  an example PATH&lt;br /&gt;
 export PATH=/usr/bin:/opt/wx/2.6/bin:$PATH&lt;br /&gt;
(*Note// &lt;br /&gt;
on Ubuntu Hoary it was necessary to check &amp;quot;Run command as login shell&amp;quot; &lt;br /&gt;
in the gnome-terminal profile-settings, &lt;br /&gt;
otherwise the PATH changes are not available in a gnome-terminal window. &lt;br /&gt;
//tiwag 051008*)&lt;br /&gt;
&lt;br /&gt;
add /opt/wx/2.6/lib to /etc/ld.so.conf (nano /etc/ld.so.conf)&lt;br /&gt;
then run:&lt;br /&gt;
 ldconfig&lt;br /&gt;
 source /etc/profile&lt;br /&gt;
&lt;br /&gt;
That's it.  Now the linker will look in /opt/wx/2.6/lib for wx libraries and you will have a monolithic shared library unicode build.&lt;br /&gt;
&lt;br /&gt;
To check that things are working, type:&lt;br /&gt;
 wx-config --prefix&lt;br /&gt;
which should give you /opt/wx/2.6&lt;br /&gt;
 wx-config --libs&lt;br /&gt;
which should have at least&lt;br /&gt;
 -L/opt/wx/2.6/lib -lwx_gtk2-2.6&lt;br /&gt;
but can contain other flags as well.&lt;br /&gt;
 which wx-config&lt;br /&gt;
should return /opt/wx/2.6/bin/wx-config&lt;br /&gt;
&lt;br /&gt;
===Code::Blocks installation===&lt;br /&gt;
&lt;br /&gt;
====Downloading Code::Blocks====&lt;br /&gt;
&lt;br /&gt;
You can get Code::Blocks source code in one of two ways:&lt;br /&gt;
* Download the latest source package, or&lt;br /&gt;
* Get the latest sources from the CVS repository.&lt;br /&gt;
Both methods, are described below.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Downloading the latest source package=====&lt;br /&gt;
&lt;br /&gt;
Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the &amp;quot; Code::Blocks IDE version 1.0rc2 source code (tarball)&amp;quot; codeblocks-1.0rc2.tar.gz.&lt;br /&gt;
Save this file in &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt; and then untar it:&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&lt;br /&gt;
tar zxf codeblocks-1.0rc2.tar.gz&amp;lt;/pre&amp;gt;&lt;br /&gt;
This will create the directory &amp;lt;tt&amp;gt;~/devel/codeblocks-1.0rc2&amp;lt;/tt&amp;gt;.&lt;br /&gt;
Change to the source code directory, by issuing the following command:&lt;br /&gt;
&amp;lt;pre&amp;gt;cd codeblocks-1.0rc2&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====Getting the latest sources from CVS=====&lt;br /&gt;
&lt;br /&gt;
For the following to work, you need to have the &amp;lt;tt&amp;gt;cvs&amp;lt;/tt&amp;gt; command line client installed on your system.&lt;br /&gt;
First you need to login to the CVS server:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When asked for a password, press enter.&lt;br /&gt;
Now, just checkout (i.e. download) the sources from the repository:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&lt;br /&gt;
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will create the directory &amp;lt;tt&amp;gt;codeblocks&amp;lt;/tt&amp;gt;.&lt;br /&gt;
Change to the source code directory, by issuing the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd codeblocks&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Building Code::Blocks RC2 and CVS====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you're compiling the cvs HEAD verions of CodeBlocks (or future versions) then the unix build has switched to autotools.  So first build wxWidgets as described above and then build CodeBlocks as follows:&lt;br /&gt;
&lt;br /&gt;
 ./bootstrap&lt;br /&gt;
&lt;br /&gt;
This sets up the configure script and it's dependencies.  It only needs to be run once (after downloading the source from cvs).  '''If you get errors like:'''&lt;br /&gt;
 aclocal:configure.in:61: warning: macro `AM_OPTIONS_WXCONFIG' not found in library&lt;br /&gt;
Then aclocal is having trouble finding the wxWidgets .m4 files.  You can do one of two things:&lt;br /&gt;
To just get bootstrap to find the path this time do:&lt;br /&gt;
 export ACLOCAL_FLAGS=&amp;quot;--acdir=`wx-config --prefix`/share/aclocal&amp;quot;&lt;br /&gt;
To change the aclocal search path more permanently do:&lt;br /&gt;
 echo `wx-config --prefix`/share/aclocal &amp;gt;&amp;gt; /usr/share/aclocal/dirlist&lt;br /&gt;
Then aclocal will also search somewhere like /opt/wx/2.6/share/aclocal&lt;br /&gt;
&lt;br /&gt;
(*Note// '''If you run ./bootstrap and get errors like''':&lt;br /&gt;
 : bad interpreter: File not found&lt;br /&gt;
then there exists a problem with DOS line-endings. i had this error after i tried to build a  codeblocks from sources which were checked out with cvs on a windows machine. After i checked out a fresh copy of codeblocks from cvs under Ubuntu linux (see above topic: Downloading the latest source package fom CVS), all errors were gone. &lt;br /&gt;
//tiwag 051008*)&lt;br /&gt;
&lt;br /&gt;
Once you've run the bootstrap script, installing is as simple as:&lt;br /&gt;
 ./configure&lt;br /&gt;
 make&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
To uninstall you can later run:&lt;br /&gt;
 make uninstall&lt;br /&gt;
&lt;br /&gt;
If you want to recompile everything, first run:&lt;br /&gt;
 make clean&lt;br /&gt;
and then follow the above sequence for installing.&lt;br /&gt;
&lt;br /&gt;
By default, CodeBlocks will install to /usr/local.  If you want it in its own tree (so you can have multiple versions of CodeBlocks, each in its own subdirectory of /opt) replace the above ./configure command with:&lt;br /&gt;
 ./configure --prefix=/opt/codeblocks-cvs&lt;br /&gt;
or similar.  Then you can later install a different build like:&lt;br /&gt;
 ./configure --prefix=/opt/codeblocks2-cvs&lt;br /&gt;
followed by 'make &amp;amp;&amp;amp; make install' as usual.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Building Code::Blocks RC1 and former====&lt;br /&gt;
&lt;br /&gt;
To build Code::Blocks all you have to do now is type:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;make -f Makefile.unix&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will build everything: the application and the plugins. The final step is to update the working environment for your system:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;make -f Makefile.unix update&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following notes about converting the line endings does '''not''' apply to the CVS Version! The &amp;quot;update&amp;quot; script included there works just fine.&lt;br /&gt;
&lt;br /&gt;
'''Important note:''' Don't run that final make yet! The &amp;quot;update&amp;quot; script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:&lt;br /&gt;
&lt;br /&gt;
To install it in Gentoo, do:&lt;br /&gt;
&lt;br /&gt;
 # emerge -av dos2unix&lt;br /&gt;
&lt;br /&gt;
In Debian and Ubuntu, do (as root, or using sudo etc.):&lt;br /&gt;
&lt;br /&gt;
 # apt-get install sysutils&lt;br /&gt;
&lt;br /&gt;
This will install dos2unix. Now we are ready to convert the script.&lt;br /&gt;
 # dos2unix -n update update.unix&lt;br /&gt;
 # chmod +x update.unix&lt;br /&gt;
 # ./update.unix&lt;br /&gt;
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.&lt;br /&gt;
&lt;br /&gt;
OK. Now that the update script is converted to unix format, you can run the final make:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;make -f Makefile.unix update&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated &amp;lt;tt&amp;gt;run.sh&amp;lt;/tt&amp;gt; script in the &amp;lt;tt&amp;gt;output&amp;lt;/tt&amp;gt; subdir:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;output/run.sh&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)&lt;br /&gt;
&lt;br /&gt;
Enjoy!&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Main_Page&amp;diff=262</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Main_Page&amp;diff=262"/>
		<updated>2005-10-21T23:04:47Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Welcome to the official wiki site for Code::Blocks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- wiki user guide at [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] --&amp;gt;&lt;br /&gt;
= Welcome to the official wiki site for Code::Blocks =&lt;br /&gt;
[https://www.codeblocks.org Code::Blocks] is an open-source, cross-platform IDE (Integrated Development Environment). 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++. At the time of this writing, the following compilers are supported:&lt;br /&gt;
* [http://gcc.gnu.org/ GNU GCC] (Linux)&lt;br /&gt;
* [http://www.mingw.org MinGW GCC] (Win32)&lt;br /&gt;
* [http://msdn.microsoft.com/visualc/vctoolkit2003 Microsoft's Visual C++ Free Toolkit 2003] (Win32)&lt;br /&gt;
* [http://www.borland.com/products/downloads/download_cbuilder.html# Borland's C++ Compiler 5.5] (Win32)&lt;br /&gt;
* [http://www.digitalmars.com/ DigitalMars] (Win32)&lt;br /&gt;
* [http://store.scitechsoft.com/product_info.php?products_id=37/ OpenWatcom] (Win32)&lt;br /&gt;
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]&lt;br /&gt;
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/219754.htm Intel C++ compiler] ('''WARNING: [[Installing_a_supported_compiler#Configuring_CodeBlocks_to_use_the_Intel_C.2B.2B_Compiler|requires manual configuration]]''')&lt;br /&gt;
&lt;br /&gt;
This site does not hold much information yet but, with the help of the [https://www.codeblocks.org Code::Blocks] users, we hope it will soon be filled with articles, tutorials, FAQs, etc.&lt;br /&gt;
&lt;br /&gt;
== Table of contents ==&lt;br /&gt;
* [[Articles]]&lt;br /&gt;
* [[Tutorials]]&lt;br /&gt;
* [[Code::Blocks Interface]]&lt;br /&gt;
* [[FAQ]]&lt;br /&gt;
* [[Tips'n'Tricks]]&lt;br /&gt;
&lt;br /&gt;
The [https://www.codeblocks.org/about.shtml Code::Blocks Team].&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Installing_a_supported_compiler&amp;diff=254</id>
		<title>Installing a supported compiler</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Installing_a_supported_compiler&amp;diff=254"/>
		<updated>2005-10-21T22:56:56Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Currently supported compilers, at the time of this writing are:&lt;br /&gt;
* [http://gcc.gnu.org/ GNU GCC] (Linux)&lt;br /&gt;
* [http://www.mingw.org MinGW GCC] (Win32)&lt;br /&gt;
* [http://msdn.microsoft.com/visualc/vctoolkit2003 Microsoft's Visual C++ Free Toolkit 2003] (Win32)&lt;br /&gt;
* [http://www.borland.com/products/downloads/download_cbuilder.html# Borland's C++ Compiler 5.5] (Win32)&lt;br /&gt;
* [http://www.digitalmars.com/ DigitalMars] (Win32)&lt;br /&gt;
* [http://store.scitechsoft.com/product_info.php?products_id=37/ OpenWatcom] (Win32)&lt;br /&gt;
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When you launch Code::Blocks for the first time, it will scan the system for any supported compilers (it takes virtually no time). After this scan completes, Code::Blocks will have been configured for the found compiler(s). Code::Blocks will also be configured even for compilers that were not found (default installation settings will be used for each of those compilers).&lt;br /&gt;
&lt;br /&gt;
For more info on how to download and install each of the above compilers, please read on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Downloading the GNU GCC compiler &amp;amp; GDB debugger ===&lt;br /&gt;
&lt;br /&gt;
If you are working under linux:&lt;br /&gt;
Under Linux you'll, most probably, already have everything that is needed in order to compile. All major Linux distributions (RedHat, Debian, SuSE, Mandrake, Gentoo, ArchLinux, etc) come with GCC &amp;amp; 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.&lt;br /&gt;
&lt;br /&gt;
If you are working under Windows:&lt;br /&gt;
Go to MinGW's [http://www.mingw.org/download.shtml downloads] page and download the file named &amp;lt;code&amp;gt;MinGW-x.y.z.exe&amp;lt;/code&amp;gt;, where x, y and z are version numbers. At the time of this writing, this file is &amp;lt;code&amp;gt;MinGW-3.1.0-1.exe&amp;lt;/code&amp;gt;. If you consider yourself lucky, you might also try &amp;lt;code&amp;gt;MinGW-3.2.0-rc-3.exe&amp;lt;/code&amp;gt;. It's not a stable release yet, but it works and lacks some bugs the older version has.&lt;br /&gt;
These setup files contain everything needed to compile and debug windows programs.&lt;br /&gt;
&lt;br /&gt;
=== Downloading the Microsoft Visual C++ Free Toolkit 2003 ===&lt;br /&gt;
&lt;br /&gt;
Go to this [http://msdn.microsoft.com/visualc/vctoolkit2003 MSDN site] and click on the link labeled &amp;quot;Download the Visual C++ Toolkit 2003&amp;quot;. This will download the setup file.&lt;br /&gt;
&lt;br /&gt;
NOTE: ''This download is &amp;lt;u&amp;gt;not sufficient&amp;lt;/u&amp;gt; for building windows programs. You will also have to download and install the [http://www.microsoft.com/msdownload/platformsdk/instmsi.htm Microsoft Platform SDK]''...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Downloading the Borland C++ Compiler 5.5 ===&lt;br /&gt;
&lt;br /&gt;
NOTE: ''At some point, you will be asked to register with Borland and fill out a survey. Registration is free.''&lt;br /&gt;
&lt;br /&gt;
Go to [http://www.borland.com/products/downloads/download_cbuilder.html# Borland's downloads] and click on the link labeled &amp;quot;Compiler&amp;quot;. After you accept the license agreement, you will be provided with download links to the setup file.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Downloading the Digital Mars Free Compiler ===&lt;br /&gt;
&lt;br /&gt;
NOTE: ''Code::Blocks support for DigitalMars was added in 1.0-beta6.''&lt;br /&gt;
&lt;br /&gt;
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. Download the compiler (current version is 8.41). You might also want to download the resource compiler (in basic utilities), as well as the STLport.&lt;br /&gt;
&lt;br /&gt;
=== Configuring CodeBlocks to use the Intel C++ Compiler ===&lt;br /&gt;
&lt;br /&gt;
After various user requests, we decided to post here the info to support the Intel Compiler on CodeBlocks. This should be easy, since the Intel Compiler can emulate te MSVC++ compiler.&lt;br /&gt;
&lt;br /&gt;
* change MS Toolkit linker from cl.exe to icl.exe&lt;br /&gt;
* add (instalation path to the Intel C++)\Ia32\Bin to the &amp;quot;Programs -&amp;gt; Extra paths&amp;quot;&lt;br /&gt;
* add &amp;quot;-D_USE_INTEL_COMPILER&amp;quot; to &amp;quot;Compiler options&amp;quot;&lt;br /&gt;
* add (instalation path to the Intel C++)\Ia32\Include and \lib to the &amp;quot;Global compiler options -&amp;gt; Directories&amp;quot;&lt;br /&gt;
* add some options like &amp;quot;/QaxK&amp;quot; to the &amp;quot;Compiler options&amp;quot; (icl -help)&lt;br /&gt;
voila.&lt;br /&gt;
&lt;br /&gt;
=== Compiler-neutral setup steps ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Next&amp;quot; all the way and you 're done.&lt;br /&gt;
&lt;br /&gt;
If you installed the compiler on its default installation directory, there is nothing more to configure. Launch Code::Blocks and you 're all set :)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
If your compiler was not auto-detected, go to &amp;quot;Settings/Configure plugins/Compiler&amp;quot;, select the compiler you installed, switch to the &amp;quot;Programs&amp;quot; page and press &amp;quot;Auto-detect&amp;quot;.&lt;br /&gt;
If you get a message saying that the compiler was auto-detected, congratulations!&lt;br /&gt;
If not, then press the button with the three dots next to the &amp;quot;Auto-detect&amp;quot; button and select the installation directory of your compiler manually.&lt;br /&gt;
&lt;br /&gt;
NOTE: ''The compiler's installation directory is exactly this: the installation directory. Not the &amp;quot;bin&amp;quot; subdirectory nor any other.''&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=1235</id>
		<title>FAQ</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=1235"/>
		<updated>2005-10-06T18:21:06Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Compiling */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General =&lt;br /&gt;
&lt;br /&gt;
== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==&lt;br /&gt;
&lt;br /&gt;
Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)&lt;br /&gt;
&lt;br /&gt;
== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==&lt;br /&gt;
&lt;br /&gt;
Since version 1.0-beta5, no it is not. Code::Blocks works with GNU &amp;quot;make&amp;quot; [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to &amp;quot;Project/Build options&amp;quot;, switch to the &amp;quot;Other&amp;quot; tab and select the build method you prefer.&lt;br /&gt;
&lt;br /&gt;
== What licence is Code::Blocks released under? ==&lt;br /&gt;
&lt;br /&gt;
GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])&lt;br /&gt;
&lt;br /&gt;
= Compiling =&lt;br /&gt;
&lt;br /&gt;
== What compiler can I use with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.&lt;br /&gt;
&lt;br /&gt;
As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5, DigitalMars Free Compiler., OpenWatcom and Small Device C Compiler (SDCC).&lt;br /&gt;
&lt;br /&gt;
== I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
A little documentation problem ^^;. The &amp;quot;default compiler&amp;quot; is usually GCC, so when you imported it with &amp;quot;the default compiler&amp;quot;, you told it to use GCC. To fix this situation, go to &amp;quot;Project&amp;quot;, &amp;quot;Build Options&amp;quot; and select VC++ Toolkit as your compiler.&lt;br /&gt;
&lt;br /&gt;
== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==&lt;br /&gt;
&lt;br /&gt;
''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''&lt;br /&gt;
&lt;br /&gt;
You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under &amp;quot;Settings/Configure plugins/Compiler&amp;quot; in the &amp;quot;Programs&amp;quot; tab...&lt;br /&gt;
Second, you have to add two additional compiler (include) dirs. Go to &amp;quot;Settings/Configure plugins/Compiler&amp;quot; and in the &amp;quot;Compiler dirs&amp;quot; tab add &amp;quot;dev-cpp\include\c++&amp;quot; and &amp;quot;dev-cpp\include\c++\mingw32&amp;quot; (substituting &amp;quot;dev-cpp&amp;quot; with the actual dev-cpp installation folder).&lt;br /&gt;
&lt;br /&gt;
== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==&lt;br /&gt;
&lt;br /&gt;
BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.&lt;br /&gt;
&lt;br /&gt;
== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a &amp;quot;Custom Makefile&amp;quot; checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.&lt;br /&gt;
Also make sure that &amp;quot;GNU make&amp;quot; is the selected build method for the specific compiler.&lt;br /&gt;
&lt;br /&gt;
== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==&lt;br /&gt;
&lt;br /&gt;
Click on &amp;quot;Project/Build options&amp;quot; and select the compiler you want for your project/target.&lt;br /&gt;
&lt;br /&gt;
== When compiling a wxWidgets project, I get several &amp;quot;variable 'vtable for xxxx' can't be auto-imported&amp;quot;. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
You need to add WXUSINGDLL in &amp;quot;Project-&amp;gt;Build options-&amp;gt;Compiler #defines&amp;quot; and rebuild your project (or create a new project and use the &amp;quot;Using wxWidgets DLL&amp;quot; project option which adds &amp;quot;-DWXUSINGDLL&amp;quot; to Project-&amp;gt;Build options-&amp;gt;Other options).&lt;br /&gt;
Other errors with the same resolution are:&lt;br /&gt;
'unresolved external symbol &amp;quot;char const * const wxEmptyString&amp;quot; (?wxEmptyString@@3PBDB)' or similar.&lt;br /&gt;
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.&lt;br /&gt;
&lt;br /&gt;
== I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ==&lt;br /&gt;
&lt;br /&gt;
sorry, no fix for your problem...&lt;br /&gt;
&lt;br /&gt;
Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which are coming with Visual C++ (VC) which isn't free, unfortunately.&lt;br /&gt;
&lt;br /&gt;
Try buying a full-fledged VC++, or even better, download MinGW :)&lt;br /&gt;
&lt;br /&gt;
The libraries that can be obtained free of charge are:&lt;br /&gt;
&lt;br /&gt;
Paths:&lt;br /&gt;
 (VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib&lt;br /&gt;
 (PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib&lt;br /&gt;
 (NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib&lt;br /&gt;
&lt;br /&gt;
C runtime libs:&lt;br /&gt;
 LIBC.LIB 	Single-threaded, static link                                          (VCT3, NSDK)&lt;br /&gt;
 LIBCMT.LIB 	Multithreaded, static link                                            (VCT3, NSDK)&lt;br /&gt;
 MSVCRT.LIB 	Multithreaded, dynamic link (import library for MSVCR71.DLL)          (NSDK)&lt;br /&gt;
 LIBCD.LIB 	Single-threaded, static link (debug)                                  (VCT3, NSDK)&lt;br /&gt;
 LIBCMTD.LIB 	Multithreaded, static link (debug)                                    (NSDK)&lt;br /&gt;
 MSVCRTD.LIB 	Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)&lt;br /&gt;
&lt;br /&gt;
C++ libs:&lt;br /&gt;
 LIBCP.LIB 	Single-threaded, static link                                          (VCT3, PSDK)&lt;br /&gt;
 LIBCPMT.LIB 	Multithreaded, static link                                            (VCT3)&lt;br /&gt;
 MSVCPRT.LIB 	Multithreaded, dynamic link (import library for MSVCP71.dll)          (none)&lt;br /&gt;
 LIBCPD.LIB 	Single-threaded, static link (debug)                                  (VCT3)&lt;br /&gt;
 LIBCPMTD.LIB 	Multithreaded, static link (debug)                                    (none)&lt;br /&gt;
 MSVCPRTD.LIB 	Multithreaded, dynamic link (import library for MSVCP71D.DLL) (debug) (none)&lt;br /&gt;
&lt;br /&gt;
Try setting the library linker directories to:&lt;br /&gt;
 C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib&lt;br /&gt;
 C:\Program Files\Microsoft Platform SDK\Lib&lt;br /&gt;
 C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib&lt;br /&gt;
in that order.&lt;br /&gt;
&lt;br /&gt;
The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory.  Not sure if these would work on 32-bit windows, however, they may if they are&lt;br /&gt;
meant to work in 32-bit compatibility mode on the 64-bit processors.  Worth a try.  Otherwise, you&lt;br /&gt;
can link statically to the C++ library instead of using MSVCP71.dll.  If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed.  Search google for &amp;quot;exports.sed&amp;quot; for detailed steps.&lt;br /&gt;
&lt;br /&gt;
See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp&lt;br /&gt;
&lt;br /&gt;
See also: http://sapdb.2scale.net/moin.cgi/MS_20C_2b_2b_20Toolkit&lt;br /&gt;
&lt;br /&gt;
== Where are the libraries for the OpenGL / SDL / etc. projects? ==&lt;br /&gt;
&lt;br /&gt;
They're not bundled. The templates were provided for your convenience, but you need to download the libraries on your own.&lt;br /&gt;
In common terms, &amp;quot;batteries not included&amp;quot; :)&lt;br /&gt;
&lt;br /&gt;
== Is it possible to use Visual C++ 6.0 with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
As they say in ##C++ on FreeNode:&amp;lt;br&amp;gt;&lt;br /&gt;
cylon&amp;gt; msvc++6 is not a C++ compiler. It was made before the C++ standard, so it compiles some language that isn't C++. Upgrade.&lt;br /&gt;
&lt;br /&gt;
== I got this error when compiling: Symbol &amp;quot;isascii&amp;quot; was not found in &amp;quot;codeblocks.dll&amp;quot; ==&lt;br /&gt;
Make sure you didn't mix up the MSVC headers or libs with the MinGW ones.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Using_SDL_with_Code::Blocks&amp;diff=177</id>
		<title>Using SDL with Code::Blocks</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Using_SDL_with_Code::Blocks&amp;diff=177"/>
		<updated>2005-08-24T18:41:19Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Written by Thomas.&lt;br /&gt;
Original idea by [http://www.ubergeekultd.com Ubergeek, ultd].&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Good, the Bad, and the Ugly&amp;quot; - Setting up SDL==&lt;br /&gt;
&lt;br /&gt;
This article deals with [[SDL]] using [[CodeBlocks:About|Code::Blocks]] with the [http://www.mingw.org MinGW compiler], however the same steps will likely work with a different compiler (such as MSVC2003 toolkit) or under Linux, too (Linux users will of course not worry about DirectX).&lt;br /&gt;
&lt;br /&gt;
There are many ways to get the necessary libraries and include files to set up SDL to be used with Code::Blocks, each of them having its own advantages and disadvantages. In  memory of Sergio Leone's best movie, I will call these &amp;quot;the Good&amp;quot;, &amp;quot;the Bad&amp;quot;, and &amp;quot;the Ugly&amp;quot;.&amp;lt;br /&amp;gt;&lt;br /&gt;
The uglier variants have the advantage of better configurability, but are more error-prone and may take significantly more time to set up.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Good&amp;quot;==&lt;br /&gt;
The easiest of all possibilities is to just '''download the SDL binary distribution''' directly from libsdl.org.&amp;lt;br /&amp;gt;&lt;br /&gt;
If you are only interested in writing a SDL application and care little about esoteric compiler switches, then the pre-built libraries are probably good enough for all your needs, so there is little reason to waste your time compiling your own.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' need to download one file, setup time ~20 seconds&lt;br /&gt;
*'''pro:''' it works&lt;br /&gt;
*'''con:''' not configurable&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#Internet Connection&amp;lt;br /&amp;gt;&lt;br /&gt;
#Some archiving program (tar, 7z, WinZip, PowerArchiver, ...)&amp;lt;br /&amp;gt;&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-devel-1.2.8-mingw32.tar.gz SDL-devel-1.2.8-mingw32.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]. There are binary packages for several Linux distributions, too (&amp;lt;tt&amp;gt;rpm&amp;lt;/tt&amp;gt; may have problems downloading directly from libsdl.org, use &amp;lt;tt&amp;gt;wget&amp;lt;/tt&amp;gt; to get the packages in that case).&lt;br /&gt;
#Decompress the archive&lt;br /&gt;
#Copy &amp;lt;tt&amp;gt;SDL.dll&amp;lt;/tt&amp;gt; from inside the &amp;lt;tt&amp;gt;bin&amp;lt;/tt&amp;gt; folder to where you keep your dll files (could be &amp;lt;tt&amp;gt;C:\MinGW\dll&amp;lt;/tt&amp;gt; or &amp;lt;tt&amp;gt;C:\MinGW\lib&amp;lt;/tt&amp;gt;, whatever).&lt;br /&gt;
#Copy the contents of &amp;lt;tt&amp;gt;lib&amp;lt;/tt&amp;gt; to your compiler's lib folder. If MinGW is installed under &amp;lt;tt&amp;gt;C:\MinGW&amp;lt;/tt&amp;gt;, then this will be &amp;lt;tt&amp;gt;C:\MinGW\lib&amp;lt;/tt&amp;gt;.&lt;br /&gt;
#Copy the complete folder &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; from inside the folder &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; to your compiler's include directory (for example &amp;lt;tt&amp;gt;C:\MinGW\include&amp;lt;/tt&amp;gt;). Be sure to copy the ''folder'', not the individual files.&lt;br /&gt;
#Optionally, copy &amp;lt;tt&amp;gt;SDL.dll&amp;lt;/tt&amp;gt; to &amp;lt;tt&amp;gt;C:\Windows&amp;lt;/tt&amp;gt;, too. This will save you from copying the dll to each and every project directory while developing. Be cautious, however, not to find yourself in [http://en.wikipedia.org/wiki/DLL_hell DLL hell] afterwards.&lt;br /&gt;
#Screw the rest&lt;br /&gt;
It is of course possible to keep the library and include files in different locations than the ones stated above. In that case, you will have to add those locations to the compiler options. However, be sure ''not'' to add the &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; folder to include paths, but its ''parent folder'', as all SDL programs expect the headers to be inside a separate &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; folder.&lt;br /&gt;
===Alternative===&lt;br /&gt;
Code::Blocks comes with support for reading '''.DevPak''' files of late. This allows for an even more comfortable setup. Recent DevPaks (1.2.8) for SDL, SDL-mixer, and SDL-ttf can be found at [http://www.devpaks.org/category.php?category=SDL http://www.devpaks.org/category.php?category=SDL].&amp;lt;br /&amp;gt;&lt;br /&gt;
'''Important:''' Please do note that the packages at devpaks.org are not original packages created by the SDL team. Be aware that devpaks.org theoretically allows anyone to upload anything under the name SDL. Although I know of no case of malware being distributed over this channel, this is a potential risk you have to be aware of.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Bad&amp;quot;==&lt;br /&gt;
With a little more effort, you can '''build SDL from sources using Code::Blocks'''. While this may not be the desirable solution for Joe Everybody writing Hello World for his computer science class in week one, it has certainly its advantages.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' still relatively easy, build time ~5-6 minutes, setup time ~30 seconds&lt;br /&gt;
*'''pro:''' it's cool&lt;br /&gt;
*'''pro:''' it works&lt;br /&gt;
*'''pro:''' can tune optimization/target settings, release and debug libraries&lt;br /&gt;
*'''con:''' does not compile out-of-the box (yet)&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#An installation of the [https://www.codeblocks.org/downloads.shtml Code::Blocks IDE]&lt;br /&gt;
#A working [[MinGW installation]]&lt;br /&gt;
#Some archiving program (tar, 7z, WinZip, PowerArchiver, ...)&lt;br /&gt;
#DirectX development headers and libraries (version 5 or later)&lt;br /&gt;
#*in particular, the files &amp;lt;tt&amp;gt;d3dtypes.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;ddraw.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;dinput.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;directx.h&amp;lt;/tt&amp;gt;, and  &amp;lt;tt&amp;gt;dsound.h&amp;lt;/tt&amp;gt; are needed. The libraries come with a standard MinGW install, but the headers were strangely found to be missing on my system.&lt;br /&gt;
#*these files are contained in [http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz directx-devel.tar.gz] which is significantly less painful to download than the Microsoft DirectX SDK (300 MB!)&lt;br /&gt;
#*it is unlikely that your MinGW installation lacks the headers for OpenGL, but in any case, there is an [http://www.libsdl.org/extras/win32/common/opengl-devel.tar.gz OpenGL package] too.&lt;br /&gt;
&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]&lt;br /&gt;
#Decompress the archive somewhere (I will assume &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt; from now on)&lt;br /&gt;
#Inside &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt;, locate the file &amp;lt;tt&amp;gt;VisualC.zip&amp;lt;/tt&amp;gt;, decompress it, and open the workspace &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDL.dsw&amp;lt;/tt&amp;gt;&lt;br /&gt;
#As of RC1-1, Code::Blocks does not parse Visual-C projects 100% correctly, so you have to check that link libraries and include path are specified correctly.&amp;lt;br /&amp;gt;&lt;br /&gt;
#*SDL needs &amp;lt;tt&amp;gt;winmm&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;gdi32&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;dxguid&amp;lt;/tt&amp;gt;.&lt;br /&gt;
#*Also, you have to add the &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; directory inside the SDL source directory to compiler paths.&lt;br /&gt;
#Rebuild all (~3 minutes)&lt;br /&gt;
#Inside &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDL&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDLmain&amp;lt;/tt&amp;gt;, you will find the DLLs inside the &amp;lt;tt&amp;gt;Debug&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;Release&amp;lt;/tt&amp;gt; folders. Copy the DLLs to where you want to keep them and the static libraries to your compiler's &amp;lt;tt&amp;gt;lib&amp;lt;/tt&amp;gt; folder.&lt;br /&gt;
#Make a folder &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; inside your compiler's include directory. Copy all files from &amp;lt;tt&amp;gt;C:\SDL-1.2.8\include&amp;lt;/tt&amp;gt; into that directory&lt;br /&gt;
&lt;br /&gt;
[[Image:Compile sdl include libraries.png|Include directory and link libraries for building SDL in Code::Blocks]]&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Ugly&amp;quot;==&lt;br /&gt;
SDL can be '''built from sources using MSYS'''. This is certainly the most lenghty and painful way, but it also allows the most flexible configuration options.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' best tuning capabilities, can easily include or exclude individual parts of SDL&lt;br /&gt;
*'''con:''' painful, build time ~10-15 minutes, setup time ~30 seconds&lt;br /&gt;
*'''con:''' unreliable, build sometimes fails with strange errors&lt;br /&gt;
*'''con:''' have to take care of several possible pitfalls&lt;br /&gt;
===Caveats===&lt;br /&gt;
*SDL explicitely needs MSYS 1.0.8 - earlier versions will not work.&lt;br /&gt;
*Path names may not contain spaces, or you will utterly fail compiling.&lt;br /&gt;
*Some of the files in the archive may be read-only for some obscure reason. &amp;lt;tt&amp;gt;make&amp;lt;/tt&amp;gt; will choke when trying to overwrite these.&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]&lt;br /&gt;
#Decompress the archive somewhere (I will assume &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt; from now on). The path may not contain any spaces.&lt;br /&gt;
#Run &amp;lt;tt&amp;gt;./configure&amp;lt;/tt&amp;gt; along with all options that you wish. (~5-6 minutes)&lt;br /&gt;
#*&amp;lt;tt&amp;gt;./configure --help&amp;lt;/tt&amp;gt; shows all possible packages to include as well as all available options&lt;br /&gt;
#*you can trim down your SDL library by excluding unwanted features using --without-PACKAGE.&lt;br /&gt;
#Run &amp;lt;tt&amp;gt;make&amp;lt;/tt&amp;gt; (~5-8 minutes)&lt;br /&gt;
#Pray that the build succeeds&lt;br /&gt;
#Copy the libraries and header files to your preferred places as described above.&lt;br /&gt;
==&amp;quot;Arch Stanton&amp;quot; - Using SDL==&lt;br /&gt;
Now that we have the libraries built and headers installed, we want to build a SDL application.&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#[https://www.codeblocks.org/downloads.shtml The Code::Blocks IDE]&lt;br /&gt;
#A working [[MinGW installation]]&lt;br /&gt;
#The Good, the Bad, '''or''' the Ugly&lt;br /&gt;
===The Process===&lt;br /&gt;
#Code::Blocks comes with a template to create SDL projects. Use that template from &amp;quot;New Project...&amp;quot;.&lt;br /&gt;
#Open Build options and make sure the necessary libraries are included.&lt;br /&gt;
#*You have to link with &amp;lt;tt&amp;gt;mingw32&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;SDLmain&amp;lt;/tt&amp;gt; to use SDL. The template should already include these, but you may want to check.&lt;br /&gt;
#*Also, you may want to add &amp;lt;tt&amp;gt;-mwindows&amp;lt;/tt&amp;gt; to &amp;quot;Other linker options&amp;quot; to prevent a DOS window from showing (actually this is controlled by the build target type: &amp;quot;console&amp;quot; or &amp;quot;GUI&amp;quot;).&lt;br /&gt;
#Compile and run&lt;br /&gt;
&lt;br /&gt;
You should now (hopefully) see a small window showing the Code::Blocks logo:&lt;br /&gt;
&lt;br /&gt;
[[Image:Sdl-app.png|center|This is what you should get.]]&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Using_SDL_with_Code::Blocks&amp;diff=174</id>
		<title>Using SDL with Code::Blocks</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Using_SDL_with_Code::Blocks&amp;diff=174"/>
		<updated>2005-08-24T16:10:39Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;(Original contribution by [http://www.ubergeekultd.com Ubergeek, ultd]. Adapted, corrected and improved by Thomas)&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Good, the Bad, and the Ugly&amp;quot; - Setting up SDL==&lt;br /&gt;
&lt;br /&gt;
This article deals with [[SDL]] using [[CodeBlocks:About|Code::Blocks]] with the [http://www.mingw.org MinGW compiler], however the same steps will likely work with a different compiler (such as MSVC2003 toolkit) or under Linux, too (Linux users will of course not worry about DirectX).&lt;br /&gt;
&lt;br /&gt;
There are many ways to get the necessary libraries and include files to set up SDL to be used with Code::Blocks, each of them having its own advantages and disadvantages. In  memory of Sergio Leone's best movie, I will call these &amp;quot;the Good&amp;quot;, &amp;quot;the Bad&amp;quot;, and &amp;quot;the Ugly&amp;quot;.&amp;lt;br /&amp;gt;&lt;br /&gt;
The uglier variants have the advantage of better configurability, but are more error-prone and may take significantly more time to set up.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Good&amp;quot;==&lt;br /&gt;
The easiest of all possibilities is to just '''download the SDL binary distribution''' directly from libsdl.org.&amp;lt;br /&amp;gt;&lt;br /&gt;
If you are only interested in writing a SDL application and care little about esoteric compiler switches, then the pre-built libraries are probably good enough for all your needs, so there is little reason to waste your time compiling your own.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' need to download one file, setup time ~20 seconds&lt;br /&gt;
*'''pro:''' it works&lt;br /&gt;
*'''con:''' not configurable&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#Internet Connection&amp;lt;br /&amp;gt;&lt;br /&gt;
#Some archiving program (tar, 7z, WinZip, PowerArchiver, ...)&amp;lt;br /&amp;gt;&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-devel-1.2.8-mingw32.tar.gz SDL-devel-1.2.8-mingw32.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]. There are binary packages for several Linux distributions, too (&amp;lt;tt&amp;gt;rpm&amp;lt;/tt&amp;gt; may have problems downloading directly from libsdl.org, use &amp;lt;tt&amp;gt;wget&amp;lt;/tt&amp;gt; to get the packages in that case).&lt;br /&gt;
#Decompress the archive&lt;br /&gt;
#Copy &amp;lt;tt&amp;gt;SDL.dll&amp;lt;/tt&amp;gt; from inside the &amp;lt;tt&amp;gt;bin&amp;lt;/tt&amp;gt; folder to where you keep your dll files (could be &amp;lt;tt&amp;gt;C:\MinGW\dll&amp;lt;/tt&amp;gt; or &amp;lt;tt&amp;gt;C:\MinGW\lib&amp;lt;/tt&amp;gt;, whatever).&lt;br /&gt;
#Copy the contents of &amp;lt;tt&amp;gt;lib&amp;lt;/tt&amp;gt; to your compiler's lib folder. If MinGW is installed under &amp;lt;tt&amp;gt;C:\MinGW&amp;lt;/tt&amp;gt;, then this will be &amp;lt;tt&amp;gt;C:\MinGW\lib&amp;lt;/tt&amp;gt;.&lt;br /&gt;
#Copy the complete folder &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; from inside the folder &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; to your compiler's include directory (for example &amp;lt;tt&amp;gt;C:\MinGW\include&amp;lt;/tt&amp;gt;). Be sure to copy the ''folder'', not the individual files.&lt;br /&gt;
#Optionally, copy &amp;lt;tt&amp;gt;SDL.dll&amp;lt;/tt&amp;gt; to &amp;lt;tt&amp;gt;C:\Windows&amp;lt;/tt&amp;gt;, too. This will save you from copying the dll to each and every project directory while developing. Be cautious, however, not to find yourself in [http://en.wikipedia.org/wiki/DLL_hell DLL hell] afterwards.&lt;br /&gt;
#Screw the rest&lt;br /&gt;
It is of course possible to keep the library and include files in different locations than the ones stated above. In that case, you will have to add those locations to the compiler options. However, be sure ''not'' to add the &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; folder to include paths, but its ''parent folder'', as all SDL programs expect the headers to be inside a separate &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; folder.&lt;br /&gt;
===Alternative===&lt;br /&gt;
Code::Blocks comes with support for reading '''.DevPak''' files of late. This allows for an even more comfortable setup. Recent DevPaks (1.2.8) for SDL, SDL-mixer, and SDL-ttf can be found at [http://www.devpaks.org/category.php?category=SDL http://www.devpaks.org/category.php?category=SDL].&amp;lt;br /&amp;gt;&lt;br /&gt;
'''Important:''' Please do note that the packages at devpaks.org are not original packages created by the SDL team. Be aware that devpaks.org theoretically allows anyone to upload anything under the name SDL. Although I know of no case of malware being distributed over this channel, this is a potential risk you have to be aware of.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Bad&amp;quot;==&lt;br /&gt;
With a little more effort, you can '''build SDL from sources using Code::Blocks'''. While this may not be the desirable solution for Joe Everybody writing Hello World for his computer science class in week one, it has certainly its advantages.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' still relatively easy, build time ~5-6 minutes, setup time ~30 seconds&lt;br /&gt;
*'''pro:''' it's cool&lt;br /&gt;
*'''pro:''' it works&lt;br /&gt;
*'''pro:''' can tune optimization/target settings, release and debug libraries&lt;br /&gt;
*'''con:''' does not compile out-of-the box (yet)&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#An installation of the [https://www.codeblocks.org/downloads.shtml Code::Blocks IDE]&lt;br /&gt;
#A working [[MinGW installation]]&lt;br /&gt;
#Some archiving program (tar, 7z, WinZip, PowerArchiver, ...)&lt;br /&gt;
#DirectX development headers and libraries (version 5 or later)&lt;br /&gt;
#*in particular, the files &amp;lt;tt&amp;gt;d3dtypes.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;ddraw.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;dinput.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;directx.h&amp;lt;/tt&amp;gt;, and  &amp;lt;tt&amp;gt;dsound.h&amp;lt;/tt&amp;gt; are needed. The libraries come with a standard MinGW install, but the headers were strangely found to be missing on my system.&lt;br /&gt;
#*these files are contained in [http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz directx-devel.tar.gz] which is significantly less painful to download than the Microsoft DirectX SDK (300 MB!)&lt;br /&gt;
#*it is unlikely that your MinGW installation lacks the headers for OpenGL, but in any case, there is an [http://www.libsdl.org/extras/win32/common/opengl-devel.tar.gz OpenGL package] too.&lt;br /&gt;
&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]&lt;br /&gt;
#Decompress the archive somewhere (I will assume &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt; from now on)&lt;br /&gt;
#Inside &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt;, locate the file &amp;lt;tt&amp;gt;VisualC.zip&amp;lt;/tt&amp;gt;, decompress it, and open the workspace &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDL.dsw&amp;lt;/tt&amp;gt;&lt;br /&gt;
#As of RC1-1, Code::Blocks does not parse Visual-C projects 100% correctly, so you have to check that link libraries and include path are specified correctly.&amp;lt;br /&amp;gt;&lt;br /&gt;
#*SDL needs &amp;lt;tt&amp;gt;winmm&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;gdi32&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;dxguid&amp;lt;/tt&amp;gt; ([http://img243.imageshack.us/my.php?image=libs2be.png Screenshot])&lt;br /&gt;
#*Also, you have to add the &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; directory inside the SDL source directory to compiler paths ([http://img385.imageshack.us/img385/2069/inc0ke.png Screenshot]).&lt;br /&gt;
#Rebuild all (~3 minutes)&lt;br /&gt;
#Inside &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDL&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDLmain&amp;lt;/tt&amp;gt;, you will find the DLLs inside the &amp;lt;tt&amp;gt;Debug&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;Release&amp;lt;/tt&amp;gt; folders. Copy the DLLs to where you want to keep them and the static libraries to your compiler's &amp;lt;tt&amp;gt;lib&amp;lt;/tt&amp;gt; folder.&lt;br /&gt;
#Make a folder &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; inside your compiler's include directory. Copy all files from &amp;lt;tt&amp;gt;C:\SDL-1.2.8\include&amp;lt;/tt&amp;gt; into that directory&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Ugly&amp;quot;==&lt;br /&gt;
SDL can be '''built from sources using MSYS'''. This is certainly the most lenghty and painful way, but it also allows the most flexible configuration options.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' best tuning capabilities, can easily include or exclude individual parts of SDL&lt;br /&gt;
*'''con:''' painful, build time ~10-15 minutes, setup time ~30 seconds&lt;br /&gt;
*'''con:''' unreliable, build sometimes fails with strange errors&lt;br /&gt;
*'''con:''' have to take care of several possible pitfalls&lt;br /&gt;
===Caveats===&lt;br /&gt;
*SDL explicitely needs MSYS 1.0.8 - earlier versions will not work.&lt;br /&gt;
*Path names may not contain spaces, or you will utterly fail compiling.&lt;br /&gt;
*Some of the files in the archive may be read-only for some obscure reason. &amp;lt;tt&amp;gt;make&amp;lt;/tt&amp;gt; will choke when trying to overwrite these.&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]&lt;br /&gt;
#Decompress the archive somewhere (I will assume &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt; from now on). The path may not contain any spaces.&lt;br /&gt;
#Run &amp;lt;tt&amp;gt;./configure&amp;lt;/tt&amp;gt; along with all options that you wish. (~5-6 minutes)&lt;br /&gt;
#*&amp;lt;tt&amp;gt;./configure --help&amp;lt;/tt&amp;gt; shows all possible packages to include as well as all available options&lt;br /&gt;
#*you can trim down your SDL library by excluding unwanted features using --without-PACKAGE.&lt;br /&gt;
#Run &amp;lt;tt&amp;gt;make&amp;lt;/tt&amp;gt; (~5-8 minutes)&lt;br /&gt;
#Pray that the build succeeds&lt;br /&gt;
#Copy the libraries and header files to your preferred places as described above.&lt;br /&gt;
==&amp;quot;Arch Stanton&amp;quot; - Using SDL==&lt;br /&gt;
Now that we have the libraries built and headers installed, we want to build a SDL application.&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#[https://www.codeblocks.org/downloads.shtml The Code::Blocks IDE]&lt;br /&gt;
#A working [[MinGW installation]]&lt;br /&gt;
#The Good, the Bad, '''or''' the Ugly&lt;br /&gt;
===The Process===&lt;br /&gt;
#Code::Blocks comes with a template to create SDL projects. Use that template from &amp;quot;New Project...&amp;quot;.&lt;br /&gt;
#Open Build options and make sure the necessary libraries are included.&lt;br /&gt;
#*You have to link with &amp;lt;tt&amp;gt;mingw32&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;SDLmain&amp;lt;/tt&amp;gt; to use SDL.&lt;br /&gt;
#*Also, you may want to add &amp;lt;tt&amp;gt;-mwindows&amp;lt;/tt&amp;gt; to &amp;quot;Other linker options&amp;quot; to prevent a DOS window from showing (actually this is controlled by the build target type: &amp;quot;console&amp;quot; or &amp;quot;GUI&amp;quot;).&lt;br /&gt;
#Compile and run, you should now see a small window showing the Code::Blocks logo.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Using_SDL_with_Code::Blocks&amp;diff=173</id>
		<title>Using SDL with Code::Blocks</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Using_SDL_with_Code::Blocks&amp;diff=173"/>
		<updated>2005-08-24T16:01:34Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;(Original contribution by [http://www.ubergeekultd.com Ubergeek, ultd]. Adapted and improved by Thomas)&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Good, the Bad, and the Ugly&amp;quot; - Setting up SDL==&lt;br /&gt;
&lt;br /&gt;
This article deals with [[SDL]] using [[CodeBlocks:About|Code::Blocks]] with the [http://www.mingw.org MinGW compiler], however the same steps will likely work with a different compiler (such as MSVC2003 toolkit) or under Linux, too (Linux users will of course not worry about DirectX).&lt;br /&gt;
&lt;br /&gt;
There are many ways to get the necessary libraries and include files to set up SDL to be used with Code::Blocks, each of them having its own advantages and disadvantages. In  memory of Sergio Leone's best movie, I will call these &amp;quot;the Good&amp;quot;, &amp;quot;the Bad&amp;quot;, and &amp;quot;the Ugly&amp;quot;.&amp;lt;br /&amp;gt;&lt;br /&gt;
The uglier variants have the advantage of better configurability, but are more error-prone and may take significantly more time to set up.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Good&amp;quot;==&lt;br /&gt;
The easiest of all possibilities is to just '''download the SDL binary distribution''' directly from libsdl.org.&amp;lt;br /&amp;gt;&lt;br /&gt;
If you are only interested in writing a SDL application and care little about esoteric compiler switches, then the pre-built libraries are probably good enough for all your needs, so there is little reason to waste your time compiling your own.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' need to download one file, setup time ~20 seconds&lt;br /&gt;
*'''pro:''' it works&lt;br /&gt;
*'''con:''' not configurable&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#Internet Connection&amp;lt;br /&amp;gt;&lt;br /&gt;
#Some archiving program (tar, 7z, WinZip, PowerArchiver, ...)&amp;lt;br /&amp;gt;&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-devel-1.2.8-mingw32.tar.gz SDL-devel-1.2.8-mingw32.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]. There are binary packages for several Linux distributions, too (&amp;lt;tt&amp;gt;rpm&amp;lt;/tt&amp;gt; may have problems downloading directly from libsdl.org, use &amp;lt;tt&amp;gt;wget&amp;lt;/tt&amp;gt; to get the packages in that case).&lt;br /&gt;
#Decompress the archive&lt;br /&gt;
#Copy &amp;lt;tt&amp;gt;SDL.dll&amp;lt;/tt&amp;gt; from inside the &amp;lt;tt&amp;gt;bin&amp;lt;/tt&amp;gt; folder to where you keep your dll files (could be &amp;lt;tt&amp;gt;C:\MinGW\dll&amp;lt;/tt&amp;gt; or &amp;lt;tt&amp;gt;C:\MinGW\lib&amp;lt;/tt&amp;gt;, whatever).&lt;br /&gt;
#Copy the contents of &amp;lt;tt&amp;gt;lib&amp;lt;/tt&amp;gt; to your compiler's lib folder. If MinGW is installed under &amp;lt;tt&amp;gt;C:\MinGW&amp;lt;/tt&amp;gt;, then this will be &amp;lt;tt&amp;gt;C:\MinGW\lib&amp;lt;/tt&amp;gt;.&lt;br /&gt;
#Copy the complete folder &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; from inside the folder &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; to your compiler's include directory (for example &amp;lt;tt&amp;gt;C:\MinGW\include&amp;lt;/tt&amp;gt;). Be sure to copy the ''folder'', not the individual files.&lt;br /&gt;
#Optionally, copy &amp;lt;tt&amp;gt;SDL.dll&amp;lt;/tt&amp;gt; to &amp;lt;tt&amp;gt;C:\Windows&amp;lt;/tt&amp;gt;, too. This will save you from copying the dll to each and every project directory while developing. Be cautious, however, not to find yourself in [http://en.wikipedia.org/wiki/DLL_hell DLL hell] afterwards.&lt;br /&gt;
#Screw the rest&lt;br /&gt;
It is of course possible to keep the library and include files in different locations than the ones stated above. In that case, you will have to add those locations to the compiler options. However, be sure ''not'' to add the &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; folder to include paths, but its ''parent folder'', as all SDL programs expect the headers to be inside a separate &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; folder.&lt;br /&gt;
===Alternative===&lt;br /&gt;
Code::Blocks comes with support for reading '''.DevPak''' files of late. This allows for an even more comfortable setup. Recent DevPaks (1.2.8) for SDL, SDL-mixer, and SDL-ttf can be found at [http://www.devpaks.org/category.php?category=SDL http://www.devpaks.org/category.php?category=SDL].&amp;lt;br /&amp;gt;&lt;br /&gt;
'''Important:''' Please do note that the packages at devpaks.org are not original packages created by the SDL team. Be aware that devpaks.org theoretically allows anyone to upload anything under the name SDL. Although I know of no case of malware being distributed over this channel, this is a potential risk you have to be aware of.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Bad&amp;quot;==&lt;br /&gt;
With a little more effort, you can '''build SDL from sources using Code::Blocks'''. While this may not be the desirable solution for Joe Everybody writing Hello World for his computer science class in week one, it has certainly its advantages.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' still relatively easy, build time ~5-6 minutes, setup time ~30 seconds&lt;br /&gt;
*'''pro:''' it's cool&lt;br /&gt;
*'''pro:''' it works&lt;br /&gt;
*'''pro:''' can tune optimization/target settings, release and debug libraries&lt;br /&gt;
*'''con:''' does not compile out-of-the box (yet)&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#An installation of the [https://www.codeblocks.org/downloads.shtml Code::Blocks IDE]&lt;br /&gt;
#A working [[MinGW installation]]&lt;br /&gt;
#Some archiving program (tar, 7z, WinZip, PowerArchiver, ...)&lt;br /&gt;
#DirectX development headers and libraries (version 5 or later)&lt;br /&gt;
#*in particular, the files &amp;lt;tt&amp;gt;d3dtypes.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;ddraw.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;dinput.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;directx.h&amp;lt;/tt&amp;gt;, and  &amp;lt;tt&amp;gt;dsound.h&amp;lt;/tt&amp;gt; are needed. The libraries come with a standard MinGW install, but the headers were strangely found to be missing on my system.&lt;br /&gt;
#*these files are contained in [http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz directx-devel.tar.gz] which is significantly less painful to download than the Microsoft DirectX SDK (300 MB!)&lt;br /&gt;
#*it is unlikely that your MinGW installation lacks the headers for OpenGL, but in any case, there is an [http://www.libsdl.org/extras/win32/common/opengl-devel.tar.gz OpenGL package] too.&lt;br /&gt;
&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]&lt;br /&gt;
#Decompress the archive somewhere (I will assume &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt; from now on)&lt;br /&gt;
#Inside &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt;, locate the file &amp;lt;tt&amp;gt;VisualC.zip&amp;lt;/tt&amp;gt;, decompress it, and open the workspace &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDL.dsw&amp;lt;/tt&amp;gt;&lt;br /&gt;
#As of RC1-1, Code::Blocks does not parse Visual-C projects 100% correctly, so you have to check that link libraries and include path are specified correctly.&amp;lt;br /&amp;gt;&lt;br /&gt;
#*SDL needs &amp;lt;tt&amp;gt;winmm&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;gdi32&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;dxguid&amp;lt;/tt&amp;gt; ([http://img243.imageshack.us/my.php?image=libs2be.png Screenshot])&lt;br /&gt;
#*Also, you have to add the &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; directory inside the SDL source directory to compiler paths ([http://img385.imageshack.us/img385/2069/inc0ke.png Screenshot]).&lt;br /&gt;
#Rebuild all (~3 minutes)&lt;br /&gt;
#Inside &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDL&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDLmain&amp;lt;/tt&amp;gt;, you will find the DLLs inside the &amp;lt;tt&amp;gt;Debug&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;Release&amp;lt;/tt&amp;gt; folders. Copy the DLLs to where you want to keep them and the static libraries to your compiler's &amp;lt;tt&amp;gt;lib&amp;lt;/tt&amp;gt; folder.&lt;br /&gt;
#Make a folder &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; inside your compiler's include directory. Copy all files from &amp;lt;tt&amp;gt;C:\SDL-1.2.8\include&amp;lt;/tt&amp;gt; into that directory&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Ugly&amp;quot;==&lt;br /&gt;
SDL can be '''built from sources using MSYS'''. This is certainly the most lenghty and painful way, but it also allows the most flexible configuration options.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' best tuning capabilities, can easily include or exclude individual parts of SDL&lt;br /&gt;
*'''con:''' painful, build time ~10-15 minutes, setup time ~30 seconds&lt;br /&gt;
*'''con:''' unreliable, build sometimes fails with strange errors&lt;br /&gt;
*'''con:''' have to take care of several possible pitfalls&lt;br /&gt;
===Caveats===&lt;br /&gt;
*SDL explicitely needs MSYS 1.0.8 - earlier versions will not work.&lt;br /&gt;
*Path names may not contain spaces, or you will utterly fail compiling.&lt;br /&gt;
*Some of the files in the archive may be read-only for some obscure reason. &amp;lt;tt&amp;gt;make&amp;lt;/tt&amp;gt; will choke when trying to overwrite these.&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]&lt;br /&gt;
#Decompress the archive somewhere (I will assume &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt; from now on). The path may not contain any spaces.&lt;br /&gt;
#Run &amp;lt;tt&amp;gt;./configure&amp;lt;/tt&amp;gt; along with all options that you wish. (~5-6 minutes)&lt;br /&gt;
#*&amp;lt;tt&amp;gt;./configure --help&amp;lt;/tt&amp;gt; shows all possible packages to include as well as all available options&lt;br /&gt;
#*you can trim down your SDL library by excluding unwanted features using --without-PACKAGE.&lt;br /&gt;
#Run &amp;lt;tt&amp;gt;make&amp;lt;/tt&amp;gt; (~5-8 minutes)&lt;br /&gt;
#Pray that the build succeeds&lt;br /&gt;
#Copy the libraries and header files to your preferred places as described above.&lt;br /&gt;
==&amp;quot;Arch Stanton&amp;quot; - Using SDL==&lt;br /&gt;
Now that we have the libraries built and headers installed, we want to build a SDL application.&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#[https://www.codeblocks.org/downloads.shtml The Code::Blocks IDE]&lt;br /&gt;
#A working [[MinGW installation]]&lt;br /&gt;
#The Good, the Bad, '''or''' the Ugly&lt;br /&gt;
===The Process===&lt;br /&gt;
#Code::Blocks comes with a template to create SDL projects. Use that template from &amp;quot;New Project...&amp;quot;.&lt;br /&gt;
#Open Build options and make sure the necessary libraries are included.&lt;br /&gt;
#*You have to link with &amp;lt;tt&amp;gt;mingw32&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;SDLmain&amp;lt;/tt&amp;gt; to use SDL.&lt;br /&gt;
#*Also, you may want to add &amp;lt;tt&amp;gt;-mwindows&amp;lt;/tt&amp;gt; to &amp;quot;Other linker options&amp;quot; to prevent a DOS window from showing (actually this is controlled by the build target type: &amp;quot;console&amp;quot; or &amp;quot;GUI&amp;quot;).&lt;br /&gt;
#Compile and run, you should now see a small window showing the Code::Blocks logo.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Using_SDL_with_Code::Blocks&amp;diff=171</id>
		<title>Using SDL with Code::Blocks</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Using_SDL_with_Code::Blocks&amp;diff=171"/>
		<updated>2005-08-22T20:43:14Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;(Contributed by [http://www.ubergeekultd.com Ubergeek, ultd]. Copied by Thomas)&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Good, the Bad, and the Ugly&amp;quot; - Setting up SDL==&lt;br /&gt;
&lt;br /&gt;
This article deals with [[SDL]] using [[CodeBlocks:About|Code::Blocks]] with the [http://www.mingw.org MinGW compiler], however the same steps will likely work with a different compiler (such as MSVC2003 toolkit) or under Linux, too (Linux users will of course not worry about DirectX).&lt;br /&gt;
&lt;br /&gt;
There are many ways to get the necessary libraries and include files to set up SDL to be used with Code::Blocks, each of them having its own advantages and disadvantages. In  memory of Sergio Leone's best movie, I will call these &amp;quot;the Good&amp;quot;, &amp;quot;the Bad&amp;quot;, and &amp;quot;the Ugly&amp;quot;.&amp;lt;br /&amp;gt;&lt;br /&gt;
The uglier variants have the advantage of better configurability, but are more error-prone and may take significantly more time to set up.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Good&amp;quot;==&lt;br /&gt;
The easiest of all possibilities is to just '''download the SDL binary distribution''' directly from libsdl.org.&amp;lt;br /&amp;gt;&lt;br /&gt;
If you are only interested in writing a SDL application and care little about esoteric compiler switches, then the pre-built libraries are probably good enough for all your needs, so there is little reason to waste your time compiling your own.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' need to download one file, setup time ~20 seconds&lt;br /&gt;
*'''pro:''' it works&lt;br /&gt;
*'''con:''' not configurable&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#Internet Connection&amp;lt;br /&amp;gt;&lt;br /&gt;
#Some archiving program (tar, 7z, WinZip, PowerArchiver, ...)&amp;lt;br /&amp;gt;&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-devel-1.2.8-mingw32.tar.gz SDL-devel-1.2.8-mingw32.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]. There are binary packages for several Linux distributions, too (&amp;lt;tt&amp;gt;rpm&amp;lt;/tt&amp;gt; may have problems downloading directly from libsdl.org, use &amp;lt;tt&amp;gt;wget&amp;lt;/tt&amp;gt; to get the packages in that case).&lt;br /&gt;
#Decompress the archive&lt;br /&gt;
#Copy &amp;lt;tt&amp;gt;SDL.dll&amp;lt;/tt&amp;gt; from inside the &amp;lt;tt&amp;gt;bin&amp;lt;/tt&amp;gt; folder to where you keep your dll files (could be &amp;lt;tt&amp;gt;C:\MinGW\dll&amp;lt;/tt&amp;gt; or &amp;lt;tt&amp;gt;C:\MinGW\lib&amp;lt;/tt&amp;gt;, whatever).&lt;br /&gt;
#Copy the contents of &amp;lt;tt&amp;gt;lib&amp;lt;/tt&amp;gt; to your compiler's lib folder. If MinGW is installed under &amp;lt;tt&amp;gt;C:\MinGW&amp;lt;/tt&amp;gt;, then this will be &amp;lt;tt&amp;gt;C:\MinGW\lib&amp;lt;/tt&amp;gt;.&lt;br /&gt;
#Copy the complete folder &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; from inside the folder &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; to your compiler's include directory (for example &amp;lt;tt&amp;gt;C:\MinGW\include&amp;lt;/tt&amp;gt;). Be sure to copy the ''folder'', not the individual files.&lt;br /&gt;
#Optionally, copy &amp;lt;tt&amp;gt;SDL.dll&amp;lt;/tt&amp;gt; to &amp;lt;tt&amp;gt;C:\Windows&amp;lt;/tt&amp;gt;, too. This will save you from copying the dll to each and every project directory while developing. Be cautious, however, not to find yourself in [http://en.wikipedia.org/wiki/DLL_hell DLL hell] afterwards.&lt;br /&gt;
#Screw the rest&lt;br /&gt;
It is of course possible to keep the library and include files in different locations than the ones stated above. In that case, you will have to add those locations to the compiler options. However, be sure ''not'' to add the &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; folder to include paths, but its ''parent folder'', as all SDL programs expect the headers to be inside a separate &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; folder.&lt;br /&gt;
===Alternative===&lt;br /&gt;
Code::Blocks comes with support for reading '''.DevPak''' files of late. This allows for an even more comfortable setup. Recent DevPaks (1.2.8) for SDL, SDL-mixer, and SDL-ttf can be found at [http://www.devpaks.org/category.php?category=SDL http://www.devpaks.org/category.php?category=SDL].&amp;lt;br /&amp;gt;&lt;br /&gt;
'''Important:''' Please do note that the packages at devpaks.org are not original packages created by the SDL team. Be aware that devpaks.org theoretically allows anyone to upload anything under the name SDL. Although I know of no case of malware being distributed over this channel, this is a potential risk you have to be aware of.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Bad&amp;quot;==&lt;br /&gt;
With a little more effort, you can '''build SDL from sources using Code::Blocks'''. While this may not be the desirable solution for Joe Everybody writing Hello World for his computer science class in week one, it has certainly its advantages.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' still relatively easy, build time ~5-6 minutes, setup time ~30 seconds&lt;br /&gt;
*'''pro:''' it's cool&lt;br /&gt;
*'''pro:''' it works&lt;br /&gt;
*'''pro:''' can tune optimization/target settings, release and debug libraries&lt;br /&gt;
*'''con:''' does not compile out-of-the box (yet)&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#An installation of the [https://www.codeblocks.org/downloads.shtml Code::Blocks IDE]&lt;br /&gt;
#A working [[MinGW installation]]&lt;br /&gt;
#Some archiving program (tar, 7z, WinZip, PowerArchiver, ...)&lt;br /&gt;
#DirectX development headers and libraries (version 5 or later)&lt;br /&gt;
#*in particular, the files &amp;lt;tt&amp;gt;d3dtypes.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;ddraw.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;dinput.h&amp;lt;/tt&amp;gt;,  &amp;lt;tt&amp;gt;directx.h&amp;lt;/tt&amp;gt;, and  &amp;lt;tt&amp;gt;dsound.h&amp;lt;/tt&amp;gt; are needed. The libraries come with a standard MinGW install, but the headers were strangely found to be missing on my system.&lt;br /&gt;
#*these files are contained in [http://www.libsdl.org/extras/win32/common/directx-devel.tar.gz directx-devel.tar.gz] which is significantly less painful to download than the Microsoft DirectX SDK (300 MB!)&lt;br /&gt;
#*it is unlikely that your MinGW installation lacks the headers for OpenGL, but in any case, there is an [http://www.libsdl.org/extras/win32/common/opengl-devel.tar.gz OpenGL package] too.&lt;br /&gt;
&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]&lt;br /&gt;
#Decompress the archive somewhere (I will assume &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt; from now on)&lt;br /&gt;
#Inside &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt;, locate the file &amp;lt;tt&amp;gt;VisualC.zip&amp;lt;/tt&amp;gt;, decompress it, and open the workspace &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDL.dsw&amp;lt;/tt&amp;gt;&lt;br /&gt;
#As of RC1-1, Code::Blocks does not parse Visual-C projects 100% correctly, so you have to check that link libraries and include path are specified correctly.&amp;lt;br /&amp;gt;&lt;br /&gt;
#*SDL needs &amp;lt;tt&amp;gt;winmm&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;gdi32&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;dxguid&amp;lt;/tt&amp;gt; ([http://img243.imageshack.us/my.php?image=libs2be.png Screenshot])&lt;br /&gt;
#*Also, you have to add the &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; directory inside the SDL source directory to compiler paths ([http://img385.imageshack.us/img385/2069/inc0ke.png Screenshot]).&lt;br /&gt;
#Rebuild all (~3 minutes)&lt;br /&gt;
#Inside &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDL&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;C:\SDL-1.2.8\VisualC\SDLmain&amp;lt;/tt&amp;gt;, copy &amp;lt;tt&amp;gt;SDL.dll&amp;lt;/tt&amp;gt; from either Debug or Release (or both) to where you keep your dlls. Also copy all of the static libraries to your compiler's &amp;lt;tt&amp;gt;lib&amp;lt;/tt&amp;gt; folder.&lt;br /&gt;
#Make a folder &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt; inside your compiler's include directory. Copy all files from &amp;lt;tt&amp;gt;C:\SDL-1.2.8\include&amp;lt;/tt&amp;gt; into that directory&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;The Ugly&amp;quot;==&lt;br /&gt;
SDL can be '''built from sources using MSYS'''. This is certainly the most lenghty and painful way, but it also allows the most flexible configuration options.&lt;br /&gt;
===Pro/Con===&lt;br /&gt;
*'''pro:''' best tuning capabilities, can easily include or exclude individual parts of SDL&lt;br /&gt;
*'''con:''' painful, build time ~10-15 minutes, setup time ~30 seconds&lt;br /&gt;
*'''con:''' unreliable, build sometimes fails with strange errors&lt;br /&gt;
*'''con:''' have to take care of several possible pitfalls&lt;br /&gt;
===Caveats===&lt;br /&gt;
*SDL explicitely needs MSYS 1.0.8 - earlier versions will not work.&lt;br /&gt;
*Path names may not contain spaces, or you will utterly fail compiling.&lt;br /&gt;
*Some of the files in the archive may be read-only for some obscure reason. &amp;lt;tt&amp;gt;make&amp;lt;/tt&amp;gt; will choke when trying to overwrite these.&lt;br /&gt;
===The Process===&lt;br /&gt;
#Download [http://www.libsdl.org/release/SDL-1.2.8.tar.gz SDL-1.2.8.tar.gz] from the [http://www.libsdl.org/download-1.2.php SDL version 1.2.8 download page]&lt;br /&gt;
#Decompress the archive somewhere (I will assume &amp;lt;tt&amp;gt;C:\SDL-1.2.8&amp;lt;/tt&amp;gt; from now on). The path may not contain any spaces.&lt;br /&gt;
#Run &amp;lt;tt&amp;gt;./configure&amp;lt;/tt&amp;gt; along with all options that you wish. (~5-6 minutes)&lt;br /&gt;
#*&amp;lt;tt&amp;gt;./configure --help&amp;lt;/tt&amp;gt; shows all possible packages to include as well as all available options&lt;br /&gt;
#*you can trim down your SDL library by excluding unwanted features using --without-PACKAGE.&lt;br /&gt;
#Run &amp;lt;tt&amp;gt;make&amp;lt;/tt&amp;gt; (~5-8 minutes)&lt;br /&gt;
#Pray that the build succeeds&lt;br /&gt;
#Copy the libraries and header files to your preferred places as described above.&lt;br /&gt;
==&amp;quot;Arch Stanton&amp;quot; - Using SDL==&lt;br /&gt;
Now that we have the libraries built and headers installed, we want to build a SDL application.&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
#[https://www.codeblocks.org/downloads.shtml The Code::Blocks IDE]&lt;br /&gt;
#A working [[MinGW installation]]&lt;br /&gt;
#The Good, the Bad, '''or''' the Ugly&lt;br /&gt;
===The Process===&lt;br /&gt;
#Code::Blocks comes with a template to create SDL projects. Use that template from &amp;quot;New Project...&amp;quot;.&lt;br /&gt;
#Open Build options and make sure the necessary libraries are included.&lt;br /&gt;
#*You have to link with &amp;lt;tt&amp;gt;mingw32&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;SDL&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;SDLmain&amp;lt;/tt&amp;gt; to use SDL.&lt;br /&gt;
#*Also, you may want to add &amp;lt;tt&amp;gt;-mwindows&amp;lt;/tt&amp;gt; to &amp;quot;Other linker options&amp;quot; to prevent a DOS window from showing (actually this is controlled by the build target type: &amp;quot;console&amp;quot; or &amp;quot;GUI&amp;quot;).&lt;br /&gt;
#Compile and run, you should now see a small window showing the Code::Blocks logo.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=123</id>
		<title>FAQ</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=123"/>
		<updated>2005-08-07T03:12:44Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Compiling */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General =&lt;br /&gt;
&lt;br /&gt;
== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==&lt;br /&gt;
&lt;br /&gt;
Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)&lt;br /&gt;
&lt;br /&gt;
== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==&lt;br /&gt;
&lt;br /&gt;
Since version 1.0-beta5, no it is not. Code::Blocks works with GNU &amp;quot;make&amp;quot; [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to &amp;quot;Project/Build options&amp;quot;, switch to the &amp;quot;Other&amp;quot; tab and select the build method you prefer.&lt;br /&gt;
&lt;br /&gt;
== What licence is Code::Blocks released under? ==&lt;br /&gt;
&lt;br /&gt;
GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])&lt;br /&gt;
&lt;br /&gt;
= Compiling =&lt;br /&gt;
&lt;br /&gt;
== What compiler can I use with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.&lt;br /&gt;
&lt;br /&gt;
As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5 and DigitalMars Free Compiler.&lt;br /&gt;
&lt;br /&gt;
== I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
A little documentation problem ^^;. The &amp;quot;default compiler&amp;quot; is usually GCC, so when you imported it with &amp;quot;the default compiler&amp;quot;, you told it to use GCC. To fix this situation, go to &amp;quot;Project&amp;quot;, &amp;quot;Build Options&amp;quot; and select VC++ Toolkit as your compiler.&lt;br /&gt;
&lt;br /&gt;
== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==&lt;br /&gt;
&lt;br /&gt;
''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''&lt;br /&gt;
&lt;br /&gt;
You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under &amp;quot;Settings/Configure plugins/Compiler&amp;quot; in the &amp;quot;Programs&amp;quot; tab...&lt;br /&gt;
Second, you have to add two additional compiler (include) dirs. Go to &amp;quot;Settings/Configure plugins/Compiler&amp;quot; and in the &amp;quot;Compiler dirs&amp;quot; tab add &amp;quot;dev-cpp\include\c++&amp;quot; and &amp;quot;dev-cpp\include\c++\mingw32&amp;quot; (substituting &amp;quot;dev-cpp&amp;quot; with the actual dev-cpp installation folder).&lt;br /&gt;
&lt;br /&gt;
== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==&lt;br /&gt;
&lt;br /&gt;
BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.&lt;br /&gt;
&lt;br /&gt;
== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a &amp;quot;Custom Makefile&amp;quot; checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.&lt;br /&gt;
Also make sure that &amp;quot;GNU make&amp;quot; is the selected build method for the specific compiler.&lt;br /&gt;
&lt;br /&gt;
== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==&lt;br /&gt;
&lt;br /&gt;
Click on &amp;quot;Project/Build options&amp;quot; and select the compiler you want for your project/target.&lt;br /&gt;
&lt;br /&gt;
== When compiling a wxWidgets project, I get several &amp;quot;variable 'vtable for xxxx' can't be auto-imported&amp;quot;. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
You need to add WXUSINGDLL in &amp;quot;Project-&amp;gt;Build options-&amp;gt;Compiler definitions&amp;quot; and rebuild your project.&lt;br /&gt;
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.&lt;br /&gt;
&lt;br /&gt;
== I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ==&lt;br /&gt;
&lt;br /&gt;
sorry, no fix for your problem...&lt;br /&gt;
&lt;br /&gt;
Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which are coming with Visual C++ (VC) which isn't free, unfortunately.&lt;br /&gt;
&lt;br /&gt;
Try buying a full-fledged VC++, or even better, download MinGW :)&lt;br /&gt;
&lt;br /&gt;
== Where are the libraries for the OpenGL / SDL / etc. projects? ==&lt;br /&gt;
&lt;br /&gt;
They're not bundled. The templates were provided for your convenience, but you need to download the libraries on your own.&lt;br /&gt;
In common terms, &amp;quot;batteries not included&amp;quot; :)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=116</id>
		<title>FAQ</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=116"/>
		<updated>2005-08-07T03:11:08Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Compiling */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General =&lt;br /&gt;
&lt;br /&gt;
== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==&lt;br /&gt;
&lt;br /&gt;
Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)&lt;br /&gt;
&lt;br /&gt;
== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==&lt;br /&gt;
&lt;br /&gt;
Since version 1.0-beta5, no it is not. Code::Blocks works with GNU &amp;quot;make&amp;quot; [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to &amp;quot;Project/Build options&amp;quot;, switch to the &amp;quot;Other&amp;quot; tab and select the build method you prefer.&lt;br /&gt;
&lt;br /&gt;
== What licence is Code::Blocks released under? ==&lt;br /&gt;
&lt;br /&gt;
GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])&lt;br /&gt;
&lt;br /&gt;
= Compiling =&lt;br /&gt;
&lt;br /&gt;
== What compiler can I use with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.&lt;br /&gt;
&lt;br /&gt;
As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5 and DigitalMars Free Compiler.&lt;br /&gt;
&lt;br /&gt;
== I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
A little documentation problem ^^;. The &amp;quot;default compiler&amp;quot; is usually GCC, so when you imported it with &amp;quot;the default compiler&amp;quot;, you told it to use GCC. To fix this situation, go to &amp;quot;Project&amp;quot;, &amp;quot;Build Options&amp;quot; and select VC++ Toolkit as your compiler.&lt;br /&gt;
&lt;br /&gt;
== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==&lt;br /&gt;
&lt;br /&gt;
''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''&lt;br /&gt;
&lt;br /&gt;
You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under &amp;quot;Settings/Configure plugins/Compiler&amp;quot; in the &amp;quot;Programs&amp;quot; tab...&lt;br /&gt;
Second, you have to add two additional compiler (include) dirs. Go to &amp;quot;Settings/Configure plugins/Compiler&amp;quot; and in the &amp;quot;Compiler dirs&amp;quot; tab add &amp;quot;dev-cpp\include\c++&amp;quot; and &amp;quot;dev-cpp\include\c++\mingw32&amp;quot; (substituting &amp;quot;dev-cpp&amp;quot; with the actual dev-cpp installation folder).&lt;br /&gt;
&lt;br /&gt;
== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==&lt;br /&gt;
&lt;br /&gt;
BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.&lt;br /&gt;
&lt;br /&gt;
== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a &amp;quot;Custom Makefile&amp;quot; checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.&lt;br /&gt;
Also make sure that &amp;quot;GNU make&amp;quot; is the selected build method for the specific compiler.&lt;br /&gt;
&lt;br /&gt;
== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==&lt;br /&gt;
&lt;br /&gt;
Click on &amp;quot;Project/Build options&amp;quot; and select the compiler you want for your project/target.&lt;br /&gt;
&lt;br /&gt;
== When compiling a wxWidgets project, I get several &amp;quot;variable 'vtable for xxxx' can't be auto-imported&amp;quot;. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
You need to add WXUSINGDLL in &amp;quot;Project-&amp;gt;Build options-&amp;gt;Compiler definitions&amp;quot; and rebuild your project.&lt;br /&gt;
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.&lt;br /&gt;
&lt;br /&gt;
== I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ==&lt;br /&gt;
&lt;br /&gt;
sorry, no fix for your problem...&lt;br /&gt;
&lt;br /&gt;
Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which are coming with Visual C++ (VC) which isn't free, unfortunately.&lt;br /&gt;
&lt;br /&gt;
Try buying a full-fledged VC++, or even better, download MinGW :)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=115</id>
		<title>FAQ</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=115"/>
		<updated>2005-08-07T03:08:51Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Compiling */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General =&lt;br /&gt;
&lt;br /&gt;
== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==&lt;br /&gt;
&lt;br /&gt;
Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)&lt;br /&gt;
&lt;br /&gt;
== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==&lt;br /&gt;
&lt;br /&gt;
Since version 1.0-beta5, no it is not. Code::Blocks works with GNU &amp;quot;make&amp;quot; [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to &amp;quot;Project/Build options&amp;quot;, switch to the &amp;quot;Other&amp;quot; tab and select the build method you prefer.&lt;br /&gt;
&lt;br /&gt;
== What licence is Code::Blocks released under? ==&lt;br /&gt;
&lt;br /&gt;
GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])&lt;br /&gt;
&lt;br /&gt;
= Compiling =&lt;br /&gt;
&lt;br /&gt;
== What compiler can I use with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.&lt;br /&gt;
&lt;br /&gt;
As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5 and DigitalMars Free Compiler.&lt;br /&gt;
&lt;br /&gt;
== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==&lt;br /&gt;
&lt;br /&gt;
''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''&lt;br /&gt;
&lt;br /&gt;
You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under &amp;quot;Settings/Configure plugins/Compiler&amp;quot; in the &amp;quot;Programs&amp;quot; tab...&lt;br /&gt;
Second, you have to add two additional compiler (include) dirs. Go to &amp;quot;Settings/Configure plugins/Compiler&amp;quot; and in the &amp;quot;Compiler dirs&amp;quot; tab add &amp;quot;dev-cpp\include\c++&amp;quot; and &amp;quot;dev-cpp\include\c++\mingw32&amp;quot; (substituting &amp;quot;dev-cpp&amp;quot; with the actual dev-cpp installation folder).&lt;br /&gt;
&lt;br /&gt;
== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==&lt;br /&gt;
&lt;br /&gt;
BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.&lt;br /&gt;
&lt;br /&gt;
== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a &amp;quot;Custom Makefile&amp;quot; checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.&lt;br /&gt;
Also make sure that &amp;quot;GNU make&amp;quot; is the selected build method for the specific compiler.&lt;br /&gt;
&lt;br /&gt;
== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==&lt;br /&gt;
&lt;br /&gt;
Click on &amp;quot;Project/Build options&amp;quot; and select the compiler you want for your project/target.&lt;br /&gt;
&lt;br /&gt;
== When compiling a wxWidgets project, I get several &amp;quot;variable 'vtable for xxxx' can't be auto-imported&amp;quot;. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
You need to add WXUSINGDLL in &amp;quot;Project-&amp;gt;Build options-&amp;gt;Compiler definitions&amp;quot; and rebuild your project.&lt;br /&gt;
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.&lt;br /&gt;
&lt;br /&gt;
== I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ==&lt;br /&gt;
&lt;br /&gt;
sorry, no fix for your problem...&lt;br /&gt;
&lt;br /&gt;
Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which are coming with Visual C++ (VC) which isn't free, unfortunately.&lt;br /&gt;
&lt;br /&gt;
Try buying a full-fledged VC++, or even better, download MinGW :)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=107</id>
		<title>FAQ</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=FAQ&amp;diff=107"/>
		<updated>2005-07-20T21:06:48Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Compiling */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;(Stolderized from [https://www.codeblocks.org/modules.php?op=modload&amp;amp;name=FAQ&amp;amp;file=index&amp;amp;myfaq=yes&amp;amp;id_cat=1 here])&lt;br /&gt;
&lt;br /&gt;
= General =&lt;br /&gt;
&lt;br /&gt;
== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==&lt;br /&gt;
&lt;br /&gt;
Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)&lt;br /&gt;
&lt;br /&gt;
== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==&lt;br /&gt;
&lt;br /&gt;
Since version 1.0-beta5, no it is not. Code::Blocks works with GNU &amp;quot;make&amp;quot; [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to &amp;quot;Project/Build options&amp;quot;, switch to the &amp;quot;Other&amp;quot; tab and select the build method you prefer.&lt;br /&gt;
&lt;br /&gt;
== What licence is Code::Blocks released under? ==&lt;br /&gt;
&lt;br /&gt;
GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])&lt;br /&gt;
&lt;br /&gt;
= Compiling =&lt;br /&gt;
&lt;br /&gt;
== What compiler can I use with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.&lt;br /&gt;
&lt;br /&gt;
As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5 and DigitalMars Free Compiler.&lt;br /&gt;
&lt;br /&gt;
== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==&lt;br /&gt;
&lt;br /&gt;
''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''&lt;br /&gt;
&lt;br /&gt;
You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under &amp;quot;Settings/Configure plugins/Compiler&amp;quot; in the &amp;quot;Programs&amp;quot; tab...&lt;br /&gt;
Second, you have to add two additional compiler (include) dirs. Go to &amp;quot;Settings/Configure plugins/Compiler&amp;quot; and in the &amp;quot;Compiler dirs&amp;quot; tab add &amp;quot;dev-cpp\include\c++&amp;quot; and &amp;quot;dev-cpp\include\c++\mingw32&amp;quot; (substituting &amp;quot;dev-cpp&amp;quot; with the actual dev-cpp installation folder).&lt;br /&gt;
&lt;br /&gt;
== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==&lt;br /&gt;
&lt;br /&gt;
BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.&lt;br /&gt;
&lt;br /&gt;
== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==&lt;br /&gt;
&lt;br /&gt;
Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a &amp;quot;Custom Makefile&amp;quot; checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.&lt;br /&gt;
Also make sure that &amp;quot;GNU make&amp;quot; is the selected build method for the specific compiler.&lt;br /&gt;
&lt;br /&gt;
== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==&lt;br /&gt;
&lt;br /&gt;
Click on &amp;quot;Project/Build options&amp;quot; and select the compiler you want for your project/target.&lt;br /&gt;
&lt;br /&gt;
== When compiling a wxWidgets project, I get several &amp;quot;variable 'vtable for xxxx' can't be auto-imported&amp;quot;. What's wrong? ==&lt;br /&gt;
&lt;br /&gt;
You need to add WXUSINGDLL in &amp;quot;Project-&amp;gt;Build options-&amp;gt;Compiler definitions&amp;quot; and rebuild your project.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=100</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=100"/>
		<updated>2005-06-10T18:10:44Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Install the unix-like commands ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets makefile requires some unix commands (like cp) to run correctly. To avoid this windows-linux compatibility problems, you have two options:&lt;br /&gt;
&lt;br /&gt;
a) Download the [ftp://biolpc22.york.ac.uk/pub/ports/mingw32/extra.zip extra.zip] package, or&lt;br /&gt;
&lt;br /&gt;
b) Setup [[#About MSYS|MSYS]].&lt;br /&gt;
&lt;br /&gt;
=== About the extra.zip package ===&lt;br /&gt;
&lt;br /&gt;
The extra.zip package contains some programs which mimic frequently-used commands in Linux.&lt;br /&gt;
&lt;br /&gt;
To install, just [ftp://biolpc22.york.ac.uk/pub/ports/mingw32/extra.zip download it] and unzip it in your MINGW directory.&lt;br /&gt;
&lt;br /&gt;
=== About MSYS ===&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
If you don't have the extra package, you must run the wxWidgets 2.4.2 compilation from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
This section provides you with two alternatives: The easy one, and the hard one.&lt;br /&gt;
The easy one consists of just copying the files to your MINGW directory. The hard one consists of setting up the paths in codeblocks.&lt;br /&gt;
&lt;br /&gt;
=== Option 1: Copying the wxWidgets files over your MINGW installation ===&lt;br /&gt;
&lt;br /&gt;
NOTE: The following instructions will overwrite part of your MINGW installation. If you're planning to build unicode applications, or use another version of wxWidgets, DO NOT, repeat, '''DO NOT''' follow these! Instead you'll have to set up the paths manually.&lt;br /&gt;
&lt;br /&gt;
So, here's how to copy the files. I (Rick) guarantee this option works, since it's the one I used.&lt;br /&gt;
&lt;br /&gt;
Close your MSYS window, and now open your windows explorer ('''NOT''' internet explorer, but Windows explorer. To open it, just press &amp;quot;(Windows key)+E&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It's recommended to open TWO explorer windows: One for your wxWidgets directory (which we'll change to copy different files), and another to &lt;br /&gt;
==== Copying the header files ====&lt;br /&gt;
In the location bar, select the following path:&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select all the files AND DIRECTORIES and copy. &lt;br /&gt;
Change to the directory &amp;quot;include&amp;quot; under your MINGW main directory, and paste.&lt;br /&gt;
&lt;br /&gt;
Now change again the directory to:&lt;br /&gt;
:&amp;lt;&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\contrib\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all files and directories, and paste them to your MINGW include directory.&lt;br /&gt;
&lt;br /&gt;
==== Copying the library files ====&lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to: &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And select all the files. Copy and Paste under your MINGW &amp;quot;lib&amp;quot; directory. &lt;br /&gt;
&lt;br /&gt;
==== Copying the setup.h file ====&lt;br /&gt;
&lt;br /&gt;
This one's very important! Normally people know to copy the headers and libs, but miss this step. If you miss it, you'll get LOTS of compilation errors. &lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a &amp;quot;mswdll&amp;quot; directory there. Under it, there's a &amp;quot;wx&amp;quot; subdirectory, too. Inside it there's a &amp;quot;setup.h&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Copy it, and paste under your MINGW include/wx directory.&lt;br /&gt;
&lt;br /&gt;
(END of option 1)&lt;br /&gt;
&lt;br /&gt;
=== Option 2: Setting up the paths manually ===&lt;br /&gt;
&lt;br /&gt;
These instructions are to be followed by those who plan to use the 2.6 version of wxWidgets, or want to build their own version (i.e. with unicode support). Since you can't use both 2.4.2 and 2.6 libraries at the same time, you have to keep them in separate directories.&lt;br /&gt;
&lt;br /&gt;
(Under construction - Somebody who has done this step, please edit)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
And that's it. Now you're ready to compile Code::Blocks!&lt;br /&gt;
&lt;br /&gt;
== Common compilation problems ==&lt;br /&gt;
&lt;br /&gt;
=== symbol `_D' is already defined ===&lt;br /&gt;
&lt;br /&gt;
Your MinGW installation is probably outdated (dev-cpp user perhaps?). Make sure you're using [[#Install_MinGW|GCC 3.4.2 or later]].&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux&amp;diff=90</id>
		<title>Installing Code::Blocks from source on Linux</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux&amp;diff=90"/>
		<updated>2005-05-28T06:40:46Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Building Code::Blocks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Prerequisites===&lt;br /&gt;
&lt;br /&gt;
In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.&lt;br /&gt;
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!&lt;br /&gt;
Let me stress it here, while it's early: &amp;lt;u&amp;gt;GTK2 is required&amp;lt;/u&amp;gt;, not GTK1, for Code::Blocks to be operational.&lt;br /&gt;
&lt;br /&gt;
All the instructions below, assume an existing directory named &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt;. If you 'll be using a different one, adjust the path to match.&lt;br /&gt;
As a first step create this directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;mkdir ~/devel&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===wxGTK-2.4.2 installation===&lt;br /&gt;
====Getting wxGTK-2.4.2====&lt;br /&gt;
&lt;br /&gt;
Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the &amp;quot;Download&amp;quot; button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Uncompressing the wxGTK sources====&lt;br /&gt;
&lt;br /&gt;
After the download finishes, switch to &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now, untar the wxGTK sources:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;tar zxf wxGTK-2.4.2.tar.gz&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;tar jxf wxGTK-2.4.2.tar.bz2&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
depending on which file you downloaded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Patching wxGTK=====&lt;br /&gt;
&lt;br /&gt;
Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.&lt;br /&gt;
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.&lt;br /&gt;
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)&lt;br /&gt;
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp&lt;br /&gt;
--- wxGTK-2.4.2/src/gtk/menu.cpp	2003-09-21 13:31:57.000000000 +0200&lt;br /&gt;
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp	2004-03-29 14:53:34.000000000 +0200&lt;br /&gt;
@@ -30,13 +30,13 @@&lt;br /&gt;
 #ifdef __WXGTK20__&lt;br /&gt;
     #include &amp;lt;glib-object.h&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
-    #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))&lt;br /&gt;
-    #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))&lt;br /&gt;
+    #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))&lt;br /&gt;
+    #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))&lt;br /&gt;
     #define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)&lt;br /&gt;
 &lt;br /&gt;
-    #define ACCEL_OBJECT        GObject&lt;br /&gt;
+    #define ACCEL_OBJECT        GtkWindow&lt;br /&gt;
     #define ACCEL_OBJECTS(a)    (a)-&amp;gt;acceleratables&lt;br /&gt;
-    #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)&lt;br /&gt;
+    #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)&lt;br /&gt;
 #else // GTK+ 1.x&lt;br /&gt;
     #define ACCEL_OBJECT        GtkObject&lt;br /&gt;
     #define ACCEL_OBJECTS(a)    (a)-&amp;gt;attach_objects&lt;br /&gt;
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp&lt;br /&gt;
--- wxGTK-2.4.2/src/gtk/settings.cpp	2003-09-21 13:31:57.000000000 +0200&lt;br /&gt;
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp	2004-03-29 15:15:35.000000000 +0200&lt;br /&gt;
@@ -340,8 +340,8 @@&lt;br /&gt;
                 }  &lt;br /&gt;
                 else  &lt;br /&gt;
                 {  &lt;br /&gt;
-                    const gchar *font_name =&lt;br /&gt;
-                        _gtk_rc_context_get_default_font_name(gtk_settings_get_default());&lt;br /&gt;
+                    gchar *font_name;&lt;br /&gt;
+                    g_object_get(gtk_settings_get_default(), &amp;quot;gtk-font-name&amp;quot;, &amp;amp;font_name, NULL);&lt;br /&gt;
                     g_systemFont = new wxFont(wxString::FromAscii(font_name));&lt;br /&gt;
                 }  &lt;br /&gt;
                 gtk_widget_destroy( widget );&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save the file as &amp;lt;tt&amp;gt;~/devel/gtk-2.4-fix.patch&amp;lt;/tt&amp;gt; and apply it by issuing:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&lt;br /&gt;
patch -Np0 -i gtk-2.4-fix.patch&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now we can build wxGTK!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Building wxGTK-2.4.2====&lt;br /&gt;
&lt;br /&gt;
Issue the following commands to build wxGTK-2.4.2:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel/wxGTK-2.4.2&lt;br /&gt;
./configure --enable-gtk2&lt;br /&gt;
make&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.&lt;br /&gt;
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;su -c &amp;quot;make install&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The above command will ask you for the root's password (you &amp;lt;u&amp;gt;are&amp;lt;/u&amp;gt; working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.&lt;br /&gt;
&lt;br /&gt;
The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd contrib/src/stc&lt;br /&gt;
make&lt;br /&gt;
su -c &amp;quot;make install&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ../xrc&lt;br /&gt;
make&lt;br /&gt;
su -c &amp;quot;make install&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;NOTE:&amp;lt;/u&amp;gt; ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''&lt;br /&gt;
&lt;br /&gt;
That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.&lt;br /&gt;
You 're now ready to download and build Code::Blocks - i.e. the easy part :) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Code::Blocks installation===&lt;br /&gt;
&lt;br /&gt;
====Downloading Code::Blocks====&lt;br /&gt;
&lt;br /&gt;
You can get Code::Blocks source code in one of two ways:&lt;br /&gt;
* Download the latest source package, or&lt;br /&gt;
* Get the latest sources from the CVS repository.&lt;br /&gt;
Both methods, are described below.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Downloading the latest source package=====&lt;br /&gt;
&lt;br /&gt;
Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the &amp;quot; Code::Blocks IDE version 1.0-beta6 source code (tarball)&amp;quot; codeblocks-1.0-beta6.tar.gz.&lt;br /&gt;
Save this file in &amp;lt;tt&amp;gt;~/devel&amp;lt;/tt&amp;gt; and then untar it:&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&lt;br /&gt;
tar zxf codeblocks-1.0-beta6.tar.gz&amp;lt;/pre&amp;gt;&lt;br /&gt;
This will create the directory &amp;lt;tt&amp;gt;~/devel/codeblocks-1.0-beta6&amp;lt;/tt&amp;gt;.&lt;br /&gt;
Change to the source code directory, by issuing the following command:&lt;br /&gt;
&amp;lt;pre&amp;gt;cd codeblocks-1.0-beta6/src&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====Getting the latest sources from CVS=====&lt;br /&gt;
&lt;br /&gt;
For the following to work, you need to have the &amp;lt;tt&amp;gt;cvs&amp;lt;/tt&amp;gt; command line client installed on your system.&lt;br /&gt;
First you need to login to the CVS server:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When asked for a password, enter &amp;lt;tt&amp;gt;anonymous&amp;lt;/tt&amp;gt;&lt;br /&gt;
Now, just checkout (i.e. download) the sources from the repository:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd ~/devel&lt;br /&gt;
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will create the directory &amp;lt;tt&amp;gt;codeblocks&amp;lt;/tt&amp;gt;.&lt;br /&gt;
Change to the source code directory, by issuing the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;cd codeblocks/src&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Building Code::Blocks====&lt;br /&gt;
&lt;br /&gt;
To build Code::Blocks all you have to do now is type:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;make -f Makefile.unix&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will build everything: the application and the plugins. The final step is to update the working environment for your system:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;make -f Makefile.unix update&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Important note:''' Don't run that final make yet! The &amp;quot;update&amp;quot; script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:&lt;br /&gt;
 # emerge -av dos2unix&lt;br /&gt;
This will install dos2unix. Now we are ready to convert the script.&lt;br /&gt;
 # dos2unix -n update update.unix&lt;br /&gt;
 # chmod +x update.unix&lt;br /&gt;
 # ./update.unix&lt;br /&gt;
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.&lt;br /&gt;
&lt;br /&gt;
OK. Now that the update script is converted to unix format, you can run the final make:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;make -f Makefile.unix update&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated &amp;lt;tt&amp;gt;run.sh&amp;lt;/tt&amp;gt; script in the &amp;lt;tt&amp;gt;output&amp;lt;/tt&amp;gt; subdir:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;output/run.sh&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)&lt;br /&gt;
&lt;br /&gt;
Enjoy!&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=94</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=94"/>
		<updated>2005-05-26T22:06:20Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* About the extra.zip package */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Install the unix-like commands ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets makefile requires some unix commands (like cp) to run correctly. To avoid this windows-linux compatibility problems, you have two options:&lt;br /&gt;
&lt;br /&gt;
a) Download the [ftp://biolpc22.york.ac.uk/pub/ports/mingw32/extra.zip extra.zip] package, or&lt;br /&gt;
&lt;br /&gt;
b) Setup [[#About MSYS|MSYS]].&lt;br /&gt;
&lt;br /&gt;
=== About the extra.zip package ===&lt;br /&gt;
&lt;br /&gt;
The extra.zip package contains some programs which mimic frequently-used commands in Linux.&lt;br /&gt;
&lt;br /&gt;
To install, just [ftp://biolpc22.york.ac.uk/pub/ports/mingw32/extra.zip download it] and unzip it in your MINGW directory.&lt;br /&gt;
&lt;br /&gt;
=== About MSYS ===&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
If you don't have the extra package, you must run the wxWidgets 2.4.2 compilation from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
This section provides you with two alternatives: The easy one, and the hard one.&lt;br /&gt;
The easy one consists of just copying the files to your MINGW directory. The hard one consists of setting up the paths in codeblocks.&lt;br /&gt;
&lt;br /&gt;
=== Option 1: Copying the wxWidgets files over your MINGW installation ===&lt;br /&gt;
&lt;br /&gt;
NOTE: The following instructions will overwrite part of your MINGW installation. If you're planning to build unicode applications, or use another version of wxWidgets, DO NOT, repeat, '''DO NOT''' follow these! Instead you'll have to set up the paths manually.&lt;br /&gt;
&lt;br /&gt;
So, here's how to copy the files. I (Rick) guarantee this option works, since it's the one I used.&lt;br /&gt;
&lt;br /&gt;
Close your MSYS window, and now open your windows explorer ('''NOT''' internet explorer, but Windows explorer. To open it, just press &amp;quot;(Windows key)+E&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It's recommended to open TWO explorer windows: One for your wxWidgets directory (which we'll change to copy different files), and another to &lt;br /&gt;
==== Copying the header files ====&lt;br /&gt;
In the location bar, select the following path:&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select all the files AND DIRECTORIES and copy. &lt;br /&gt;
Change to the directory &amp;quot;include&amp;quot; under your MINGW main directory, and paste.&lt;br /&gt;
&lt;br /&gt;
Now change again the directory to:&lt;br /&gt;
:&amp;lt;&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\contrib\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all files and directories, and paste them to your MINGW include directory.&lt;br /&gt;
&lt;br /&gt;
==== Copying the library files ====&lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to: &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And select all the files. Copy and Paste under your MINGW &amp;quot;lib&amp;quot; directory. &lt;br /&gt;
&lt;br /&gt;
==== Copying the setup.h file ====&lt;br /&gt;
&lt;br /&gt;
This one's very important! Normally people know to copy the headers and libs, but miss this step. If you miss it, you'll get LOTS of compilation errors. &lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a &amp;quot;mswdll&amp;quot; directory there. Under it, there's a &amp;quot;wx&amp;quot; subdirectory, too. Inside it there's a &amp;quot;setup.h&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Copy it, and paste under your MINGW include/wx directory.&lt;br /&gt;
&lt;br /&gt;
(END of option 1)&lt;br /&gt;
&lt;br /&gt;
=== Option 2: Setting up the paths manually ===&lt;br /&gt;
&lt;br /&gt;
These instructions are to be followed by those who plan to use the 2.6 version of wxWidgets, or want to build their own version (i.e. with unicode support). Since you can't use both 2.4.2 and 2.6 libraries at the same time, you have to keep them in separate directories.&lt;br /&gt;
&lt;br /&gt;
(Under construction - Somebody who has done this step, please edit)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
And that's it. Now you're ready to compile Code::Blocks!&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=88</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=88"/>
		<updated>2005-05-26T22:05:25Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Set up MSYS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Install the unix-like commands ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets makefile requires some unix commands (like cp) to run correctly. To avoid this windows-linux compatibility problems, you have two options:&lt;br /&gt;
&lt;br /&gt;
a) Download the [ftp://biolpc22.york.ac.uk/pub/ports/mingw32/extra.zip extra.zip] package, or&lt;br /&gt;
&lt;br /&gt;
b) Setup [[#About MSYS|MSYS]].&lt;br /&gt;
&lt;br /&gt;
=== About the extra.zip package ===&lt;br /&gt;
&lt;br /&gt;
the extra.zip package contains some programs which mimic frequently-used commands in Linux.&lt;br /&gt;
&lt;br /&gt;
To install, just [ftp://biolpc22.york.ac.uk/pub/ports/mingw32/extra.zip download it] and unzip it in your MINGW directory. &lt;br /&gt;
&lt;br /&gt;
=== About MSYS ===&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
If you don't have the extra package, you must run the wxWidgets 2.4.2 compilation from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
This section provides you with two alternatives: The easy one, and the hard one.&lt;br /&gt;
The easy one consists of just copying the files to your MINGW directory. The hard one consists of setting up the paths in codeblocks.&lt;br /&gt;
&lt;br /&gt;
=== Option 1: Copying the wxWidgets files over your MINGW installation ===&lt;br /&gt;
&lt;br /&gt;
NOTE: The following instructions will overwrite part of your MINGW installation. If you're planning to build unicode applications, or use another version of wxWidgets, DO NOT, repeat, '''DO NOT''' follow these! Instead you'll have to set up the paths manually.&lt;br /&gt;
&lt;br /&gt;
So, here's how to copy the files. I (Rick) guarantee this option works, since it's the one I used.&lt;br /&gt;
&lt;br /&gt;
Close your MSYS window, and now open your windows explorer ('''NOT''' internet explorer, but Windows explorer. To open it, just press &amp;quot;(Windows key)+E&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It's recommended to open TWO explorer windows: One for your wxWidgets directory (which we'll change to copy different files), and another to &lt;br /&gt;
==== Copying the header files ====&lt;br /&gt;
In the location bar, select the following path:&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select all the files AND DIRECTORIES and copy. &lt;br /&gt;
Change to the directory &amp;quot;include&amp;quot; under your MINGW main directory, and paste.&lt;br /&gt;
&lt;br /&gt;
Now change again the directory to:&lt;br /&gt;
:&amp;lt;&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\contrib\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all files and directories, and paste them to your MINGW include directory.&lt;br /&gt;
&lt;br /&gt;
==== Copying the library files ====&lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to: &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And select all the files. Copy and Paste under your MINGW &amp;quot;lib&amp;quot; directory. &lt;br /&gt;
&lt;br /&gt;
==== Copying the setup.h file ====&lt;br /&gt;
&lt;br /&gt;
This one's very important! Normally people know to copy the headers and libs, but miss this step. If you miss it, you'll get LOTS of compilation errors. &lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a &amp;quot;mswdll&amp;quot; directory there. Under it, there's a &amp;quot;wx&amp;quot; subdirectory, too. Inside it there's a &amp;quot;setup.h&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Copy it, and paste under your MINGW include/wx directory.&lt;br /&gt;
&lt;br /&gt;
(END of option 1)&lt;br /&gt;
&lt;br /&gt;
=== Option 2: Setting up the paths manually ===&lt;br /&gt;
&lt;br /&gt;
These instructions are to be followed by those who plan to use the 2.6 version of wxWidgets, or want to build their own version (i.e. with unicode support). Since you can't use both 2.4.2 and 2.6 libraries at the same time, you have to keep them in separate directories.&lt;br /&gt;
&lt;br /&gt;
(Under construction - Somebody who has done this step, please edit)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
And that's it. Now you're ready to compile Code::Blocks!&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=87</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=87"/>
		<updated>2005-05-26T22:00:09Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Set up MSYS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets makefile requires some unix commands (like cp) to run correctly. To avoid this windows-linux compatibility, you have two options:&lt;br /&gt;
&lt;br /&gt;
a) Download the [ftp://biolpc22.york.ac.uk/pub/ports/mingw32/extra.zip extra.zip] package, or&lt;br /&gt;
&lt;br /&gt;
b) Setup MSYS.&lt;br /&gt;
&lt;br /&gt;
=== Download the extra.zip package ===&lt;br /&gt;
&lt;br /&gt;
Download it and unzip it in your MINGW directory.&lt;br /&gt;
&lt;br /&gt;
=== Setup MSYS. ===&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
If you don't have the extra package, you must run the wxWidgets 2.4.2 compilation from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
This section provides you with two alternatives: The easy one, and the hard one.&lt;br /&gt;
The easy one consists of just copying the files to your MINGW directory. The hard one consists of setting up the paths in codeblocks.&lt;br /&gt;
&lt;br /&gt;
=== Option 1: Copying the wxWidgets files over your MINGW installation ===&lt;br /&gt;
&lt;br /&gt;
NOTE: The following instructions will overwrite part of your MINGW installation. If you're planning to build unicode applications, or use another version of wxWidgets, DO NOT, repeat, '''DO NOT''' follow these! Instead you'll have to set up the paths manually.&lt;br /&gt;
&lt;br /&gt;
So, here's how to copy the files. I (Rick) guarantee this option works, since it's the one I used.&lt;br /&gt;
&lt;br /&gt;
Close your MSYS window, and now open your windows explorer ('''NOT''' internet explorer, but Windows explorer. To open it, just press &amp;quot;(Windows key)+E&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It's recommended to open TWO explorer windows: One for your wxWidgets directory (which we'll change to copy different files), and another to &lt;br /&gt;
==== Copying the header files ====&lt;br /&gt;
In the location bar, select the following path:&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select all the files AND DIRECTORIES and copy. &lt;br /&gt;
Change to the directory &amp;quot;include&amp;quot; under your MINGW main directory, and paste.&lt;br /&gt;
&lt;br /&gt;
Now change again the directory to:&lt;br /&gt;
:&amp;lt;&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\contrib\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all files and directories, and paste them to your MINGW include directory.&lt;br /&gt;
&lt;br /&gt;
==== Copying the library files ====&lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to: &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And select all the files. Copy and Paste under your MINGW &amp;quot;lib&amp;quot; directory. &lt;br /&gt;
&lt;br /&gt;
==== Copying the setup.h file ====&lt;br /&gt;
&lt;br /&gt;
This one's very important! Normally people know to copy the headers and libs, but miss this step. If you miss it, you'll get LOTS of compilation errors. &lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a &amp;quot;mswdll&amp;quot; directory there. Under it, there's a &amp;quot;wx&amp;quot; subdirectory, too. Inside it there's a &amp;quot;setup.h&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Copy it, and paste under your MINGW include/wx directory.&lt;br /&gt;
&lt;br /&gt;
(END of option 1)&lt;br /&gt;
&lt;br /&gt;
=== Option 2: Setting up the paths manually ===&lt;br /&gt;
&lt;br /&gt;
These instructions are to be followed by those who plan to use the 2.6 version of wxWidgets, or want to build their own version (i.e. with unicode support). Since you can't use both 2.4.2 and 2.6 libraries at the same time, you have to keep them in separate directories.&lt;br /&gt;
&lt;br /&gt;
(Under construction - Somebody who has done this step, please edit)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
And that's it. Now you're ready to compile Code::Blocks!&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=82</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=82"/>
		<updated>2005-05-25T05:40:49Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
This section provides you with two alternatives: The easy one, and the hard one.&lt;br /&gt;
The easy one consists of just copying the files to your MINGW directory. The hard one consists of setting up the paths in codeblocks.&lt;br /&gt;
&lt;br /&gt;
=== Option 1: Copying the wxWidgets files over your MINGW installation ===&lt;br /&gt;
&lt;br /&gt;
NOTE: The following instructions will overwrite part of your MINGW installation. If you're planning to build unicode applications, or use another version of wxWidgets, DO NOT, repeat, '''DO NOT''' follow these! Instead you'll have to set up the paths manually.&lt;br /&gt;
&lt;br /&gt;
So, here's how to copy the files. I (Rick) guarantee this option works, since it's the one I used.&lt;br /&gt;
&lt;br /&gt;
Close your MSYS window, and now open your windows explorer ('''NOT''' internet explorer, but Windows explorer. To open it, just press &amp;quot;(Windows key)+E&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It's recommended to open TWO explorer windows: One for your wxWidgets directory (which we'll change to copy different files), and another to &lt;br /&gt;
==== Copying the header files ====&lt;br /&gt;
In the location bar, select the following path:&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select all the files AND DIRECTORIES and copy. &lt;br /&gt;
Change to the directory &amp;quot;include&amp;quot; under your MINGW main directory, and paste.&lt;br /&gt;
&lt;br /&gt;
Now change again the directory to:&lt;br /&gt;
:&amp;lt;&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\contrib\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all files and directories, and paste them to your MINGW include directory.&lt;br /&gt;
&lt;br /&gt;
==== Copying the library files ====&lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to: &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And select all the files. Copy and Paste under your MINGW &amp;quot;lib&amp;quot; directory. &lt;br /&gt;
&lt;br /&gt;
==== Copying the setup.h file ====&lt;br /&gt;
&lt;br /&gt;
This one's very important! Normally people know to copy the headers and libs, but miss this step. If you miss it, you'll get LOTS of compilation errors. &lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a &amp;quot;mswdll&amp;quot; directory there. Under it, there's a &amp;quot;wx&amp;quot; subdirectory, too. Inside it there's a &amp;quot;setup.h&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Copy it, and paste under your MINGW include/wx directory.&lt;br /&gt;
&lt;br /&gt;
(END of option 1)&lt;br /&gt;
&lt;br /&gt;
=== Option 2: Setting up the paths manually ===&lt;br /&gt;
&lt;br /&gt;
These instructions are to be followed by those who plan to use the 2.6 version of wxWidgets, or want to build their own version (i.e. with unicode support). Since you can't use both 2.4.2 and 2.6 libraries at the same time, you have to keep them in separate directories.&lt;br /&gt;
&lt;br /&gt;
(Under construction - Somebody who has done this step, please edit)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
And that's it. Now you're ready to compile Code::Blocks!&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=81</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=81"/>
		<updated>2005-05-25T05:39:00Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Option 2: Setting up the paths manually */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
This section provides you with two alternatives: The easy one, and the hard one.&lt;br /&gt;
The easy one consists of just copying the files to your MINGW directory. The hard one consists of setting up the paths in codeblocks.&lt;br /&gt;
&lt;br /&gt;
=== Option 1: Copying the wxWidgets files over your MINGW installation ===&lt;br /&gt;
&lt;br /&gt;
NOTE: The following instructions will overwrite part of your MINGW installation. If you're planning to build unicode applications, or use another version of wxWidgets, DO NOT, repeat, '''DO NOT''' follow these! Instead you'll have to set up the paths manually.&lt;br /&gt;
&lt;br /&gt;
So, here's how to copy the files. I (Rick) guarantee this option works, since it's the one I used.&lt;br /&gt;
&lt;br /&gt;
Close your MSYS window, and now open your windows explorer ('''NOT''' internet explorer, but Windows explorer. To open it, just press &amp;quot;(Windows key)+E&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It's recommended to open TWO explorer windows: One for your wxWidgets directory (which we'll change to copy different files), and another to &lt;br /&gt;
==== Copying the header files ====&lt;br /&gt;
In the location bar, select the following path:&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select all the files AND DIRECTORIES and copy. &lt;br /&gt;
Change to the directory &amp;quot;include&amp;quot; under your MINGW main directory, and paste.&lt;br /&gt;
&lt;br /&gt;
Now change again the directory to:&lt;br /&gt;
:&amp;lt;&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\contrib\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all files and directories, and paste them to your MINGW include directory.&lt;br /&gt;
&lt;br /&gt;
==== Copying the library files ====&lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to: &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And select all the files. Copy and Paste under your MINGW &amp;quot;lib&amp;quot; directory. &lt;br /&gt;
&lt;br /&gt;
==== Copying the setup.h file ====&lt;br /&gt;
&lt;br /&gt;
This one's very important! Normally people know to copy the headers and libs, but miss this step. If you miss it, you'll get LOTS of compilation errors. &lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a &amp;quot;mswdll&amp;quot; directory there. Under it, there's a &amp;quot;wx&amp;quot; subdirectory, too. Inside it there's a &amp;quot;setup.h&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Copy it, and paste under your MINGW include/wx directory.&lt;br /&gt;
&lt;br /&gt;
(END of option 1)&lt;br /&gt;
&lt;br /&gt;
=== Option 2: Setting up the paths manually ===&lt;br /&gt;
&lt;br /&gt;
These instructions are to be followed by those who plan to use the 2.6 version of wxWidgets, or want to build their own version (i.e. with unicode support). Since you can't use both 2.4.2 and 2.6 libraries at the same time, you have to keep them in separate directories.&lt;br /&gt;
&lt;br /&gt;
(Under construction - Somebody who has done this step, please edit)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=80</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=80"/>
		<updated>2005-05-25T05:37:02Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Option 1: Copying the wxWidgets files over your MINGW installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
This section provides you with two alternatives: The easy one, and the hard one.&lt;br /&gt;
The easy one consists of just copying the files to your MINGW directory. The hard one consists of setting up the paths in codeblocks.&lt;br /&gt;
&lt;br /&gt;
=== Option 1: Copying the wxWidgets files over your MINGW installation ===&lt;br /&gt;
&lt;br /&gt;
NOTE: The following instructions will overwrite part of your MINGW installation. If you're planning to build unicode applications, or use another version of wxWidgets, DO NOT, repeat, '''DO NOT''' follow these! Instead you'll have to set up the paths manually.&lt;br /&gt;
&lt;br /&gt;
So, here's how to copy the files. I (Rick) guarantee this option works, since it's the one I used.&lt;br /&gt;
&lt;br /&gt;
Close your MSYS window, and now open your windows explorer ('''NOT''' internet explorer, but Windows explorer. To open it, just press &amp;quot;(Windows key)+E&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It's recommended to open TWO explorer windows: One for your wxWidgets directory (which we'll change to copy different files), and another to &lt;br /&gt;
==== Copying the header files ====&lt;br /&gt;
In the location bar, select the following path:&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select all the files AND DIRECTORIES and copy. &lt;br /&gt;
Change to the directory &amp;quot;include&amp;quot; under your MINGW main directory, and paste.&lt;br /&gt;
&lt;br /&gt;
Now change again the directory to:&lt;br /&gt;
:&amp;lt;&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\contrib\include&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all files and directories, and paste them to your MINGW include directory.&lt;br /&gt;
&lt;br /&gt;
==== Copying the library files ====&lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to: &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And select all the files. Copy and Paste under your MINGW &amp;quot;lib&amp;quot; directory. &lt;br /&gt;
&lt;br /&gt;
==== Copying the setup.h file ====&lt;br /&gt;
&lt;br /&gt;
This one's very important! Normally people know to copy the headers and libs, but miss this step. If you miss it, you'll get LOTS of compilation errors. &lt;br /&gt;
&lt;br /&gt;
Change the explorer directory to:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;C:\wxWindows-2.4.2\lib&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a &amp;quot;mswdll&amp;quot; directory there. Under it, there's a &amp;quot;wx&amp;quot; subdirectory, too. Inside it there's a &amp;quot;setup.h&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Copy it, and paste under your MINGW include/wx directory.&lt;br /&gt;
&lt;br /&gt;
(END of option 1)&lt;br /&gt;
&lt;br /&gt;
=== Option 2: Setting up the paths manually ===&lt;br /&gt;
&lt;br /&gt;
These instructions are to be followed by those who plan to use the 2.6 version of wxWidgets, or want to build their own version (i.e. with unicode support). Since you can't use both 2.4.2 and 2.6 libraries at the same time, you have to keep them in separate directories.&lt;br /&gt;
&lt;br /&gt;
(Under construction)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=79</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=79"/>
		<updated>2005-05-25T05:18:22Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Copy the files to your mingw directory or set up the paths */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
This section provides you with two alternatives: The easy one, and the hard one.&lt;br /&gt;
The easy one consists of just copying the files to your MINGW directory. The hard one consists of setting up the paths in codeblocks.&lt;br /&gt;
&lt;br /&gt;
=== Option 1: Copying the wxWidgets files over your MINGW installation ===&lt;br /&gt;
&lt;br /&gt;
Close your MSYS window, and now open your windows explorer.&lt;br /&gt;
&lt;br /&gt;
NOTE: The following instructions will overwrite part of your MINGW installation. If you're planning to build unicode applications, or use another version of wxWidgets, DO NOT, repeat, '''DO NOT''' follow these! Instead you'll have to set up the paths manually.&lt;br /&gt;
&lt;br /&gt;
So, here's how to copy the files:&lt;br /&gt;
&lt;br /&gt;
(Under construction)&lt;br /&gt;
&lt;br /&gt;
=== Option 2: Setting up the paths manually ===&lt;br /&gt;
&lt;br /&gt;
These instructions are to be followed by those who plan to use the 2.6 version of wxWidgets, or want to build their own version (i.e. with unicode support). Since you can't use both 2.4.2 and 2.6 libraries at the same time, you have to keep them in separate directories.&lt;br /&gt;
&lt;br /&gt;
(Under construction)&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=78</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=78"/>
		<updated>2005-05-25T05:11:01Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Build the XRC library */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=77</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=77"/>
		<updated>2005-05-25T05:09:06Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Build the STC library */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../../contrib/src/stc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.&lt;br /&gt;
Now type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And then:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=76</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=76"/>
		<updated>2005-05-25T05:07:51Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Build the XRC library */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;&lt;br /&gt;
cd ../../contrib/src/stc&lt;br /&gt;
mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&lt;br /&gt;
&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;cd ../xrc&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And then:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=75</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=75"/>
		<updated>2005-05-25T05:06:53Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Build the STC library */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Still inside MSYS, type:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;tt&amp;gt;&lt;br /&gt;
cd ../../contrib/src/stc&lt;br /&gt;
mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1&lt;br /&gt;
&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=74</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=74"/>
		<updated>2005-05-25T04:58:16Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Build wxWidgets */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;cd /c/wxWindows-2.4.2/src/msw&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then proceed to the build. But first, an important warning that will save you many headaches.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:'''WARNING!'''&lt;br /&gt;
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:&lt;br /&gt;
&lt;br /&gt;
:: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 clean&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations). &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And now that everything's clean, proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Is it compiling OK? Good! You can now enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=73</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=73"/>
		<updated>2005-05-25T04:49:48Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Build wxWidgets */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .&lt;br /&gt;
Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)&lt;br /&gt;
&lt;br /&gt;
Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;'''cd /c/wxWindows-2.4.2/src/msw'''&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And proceed to the build:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;'''mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1'''&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If no &amp;quot;mingw32-make&amp;quot; is found, try this:&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;tt&amp;gt;'''make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1'''&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now it's time to enjoy your coffee :-)&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=72</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=72"/>
		<updated>2005-05-25T04:34:26Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Set up MSYS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=71</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=71"/>
		<updated>2005-05-25T04:33:41Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Install MinGW */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The MSYS package (NOT included in the Code::Blocks+MinGW bundle) allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=70</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=70"/>
		<updated>2005-05-25T04:32:49Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Set up MSYS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The MSYS package (NOT included in the Code::Blocks+MinGW bundle) allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=69</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=69"/>
		<updated>2005-05-25T04:30:58Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Install MinGW */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
'''If you DO have the Code::Blocks + MinGW bundle, you can skip this section.'''&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
After you install, make sure you have the following directories under your path:&lt;br /&gt;
* C:\MINGW\bin;&lt;br /&gt;
* C:\MINGW\mingw32\bin;&lt;br /&gt;
(I'm assumming you installed under C:\MINGW)&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The MSYS package allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=68</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=68"/>
		<updated>2005-05-25T04:08:35Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Download and Install the wxWidgets source code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The MSYS package allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).&lt;br /&gt;
&lt;br /&gt;
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.&lt;br /&gt;
On a second thought, you might like to use the setup version :P&lt;br /&gt;
&lt;br /&gt;
I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .&lt;br /&gt;
&lt;br /&gt;
And now that you have all the ingredients, it's time to compile :)&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=67</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=67"/>
		<updated>2005-05-25T03:54:38Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well&lt;br /&gt;
&lt;br /&gt;
NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&amp;amp;file=viewtopic&amp;amp;t=211&amp;amp;highlight=tutorial in the forums].&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The MSYS package allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=66</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=66"/>
		<updated>2005-05-25T03:49:40Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Install MinGW */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
(NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well)&lt;br /&gt;
&lt;br /&gt;
(NOTE: This article is under construction)&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I (Rick) have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The MSYS package allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=65</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=65"/>
		<updated>2005-05-25T03:48:28Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Set up MSYS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
(NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well)&lt;br /&gt;
&lt;br /&gt;
(NOTE: This article is under construction)&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
The MSYS package allows you to run unix scripts with Mingw. Think of it as a &amp;quot;mini-linux emulator&amp;quot;. When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.&lt;br /&gt;
&lt;br /&gt;
The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=64</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=64"/>
		<updated>2005-05-25T03:42:34Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: /* Install MinGW */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
(NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well)&lt;br /&gt;
&lt;br /&gt;
(NOTE: This article is under construction)&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the &lt;br /&gt;
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
NOTE: The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them.&lt;br /&gt;
&lt;br /&gt;
The files I have installed are:&lt;br /&gt;
&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]&lt;br /&gt;
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=63</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=63"/>
		<updated>2005-05-25T02:25:27Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
(NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well)&lt;br /&gt;
&lt;br /&gt;
(NOTE: This article is under construction)&lt;br /&gt;
&lt;br /&gt;
== Install MinGW ==&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the MINGW site and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Set up MSYS ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Download and Install the wxWidgets source code ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build wxWidgets ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the STC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Build the XRC library ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Copy the files to your mingw directory or set up the paths ==&lt;br /&gt;
&lt;br /&gt;
Under construction.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=62</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=62"/>
		<updated>2005-05-25T02:04:51Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
(NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well)&lt;br /&gt;
&lt;br /&gt;
(NOTE: This article is under construction)&lt;br /&gt;
&lt;br /&gt;
== Contents ==&lt;br /&gt;
&lt;br /&gt;
1. Install MinGW&lt;br /&gt;
&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the MINGW site and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
2. Set up MSYS&lt;br /&gt;
&lt;br /&gt;
3. Download and Install the wxWidgets source code.&lt;br /&gt;
&lt;br /&gt;
4. Build wxWidgets.&lt;br /&gt;
&lt;br /&gt;
5. Build the STC library.&lt;br /&gt;
&lt;br /&gt;
6. Build the XRC library.&lt;br /&gt;
&lt;br /&gt;
7. Copy the files to your mingw directory or set up the paths.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
	<entry>
		<id>https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=61</id>
		<title>Compiling wxWidgets 2.4.2 to develop Code::Blocks (MSW)</title>
		<link rel="alternate" type="text/html" href="https://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)&amp;diff=61"/>
		<updated>2005-05-25T02:02:29Z</updated>

		<summary type="html">&lt;p&gt;Rickg22: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.&lt;br /&gt;
&lt;br /&gt;
(NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well)&lt;br /&gt;
&lt;br /&gt;
(NOTE: This article is under construction)&lt;br /&gt;
&lt;br /&gt;
1. Install MinGW&lt;br /&gt;
If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the MINGW site and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.&lt;br /&gt;
&lt;br /&gt;
2. Set up MSYS&lt;br /&gt;
&lt;br /&gt;
3. Download and Install the wxWidgets source code.&lt;br /&gt;
&lt;br /&gt;
4. Build wxWidgets.&lt;br /&gt;
&lt;br /&gt;
5. Build the STC library.&lt;br /&gt;
&lt;br /&gt;
6. Build the XRC library.&lt;br /&gt;
&lt;br /&gt;
7. Copy the files to your mingw directory or set up the paths.&lt;/div&gt;</summary>
		<author><name>Rickg22</name></author>
	</entry>
</feed>