Code::Blocks - User contributions [en]

Installing Code::Blocks from source on Windows

2007-11-04T12:16:02Z

AlexThis: /* wxWidgets */ a few new links

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]
== Prerequisites ==

'''Note for RC2 users'''

The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].

=== MinGW compiler ===

At the present time, Code::Blocks only compiles successfully with the MinGW compiler (or any other gcc for that matter). You will need a complete, working [[MinGW installation]].

Since November 2007 MinGW-GCC 4.2.1

=== wxWidgets ===

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

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

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

* since November 2007 wxWidgets 2.8.6 <br/>Download: [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.6.zip wxMSW-2.8.6.zip]

For latest infos check forum: [/index.php?topic=3299.0 Important changes to the nightly builds]

You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').
[http://www.beispiel.de Link-Text]

=== SVN client ===

In order to check out the Code::Blocks sources you will need a SVN client.
For convenience, it is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn command-line client] equally well.

It is generally a good idea to install the command-line client (and adding it to PATH) even if you use TortoiseSVN for convenience. The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn</tt> binary if it is available. This is preferrable to the manual parsing of the entries file that is used as fallback.

Please do note that working copies checked out with the 1.4 version of Subversion are no longer compatible with earlier versions (Subversion will transparently update existing repositories).

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

=== zip.exe ===

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

The zip program coming with cygwin will ''not'' work properly. You do ''not'' need WinZip.

Make sure the zip binary is in your PATH so the <tt>update.bat</tt> script will be able to find it (alternatively, you can edit the batch file, setting the ZIPCMD variable to something else).

The easiest way is to put zip.exe into <tt>bin</tt> inside your MinGW installation directory (that folder is normally in the path).

=== Code::Blocks sources ===

You will also (obviously) need the Code::Blocks sources.

Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".

In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.

Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:

mkdir codeblocks-head
cd codeblocks-head
svn checkout svn://svn.berlios.de/codeblocks/trunk

== Building ==

=== Unicode Build ===

==== Compile wxWidgets in Unicode mode ====

After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.

'''Optional:'''

To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.

==== Compile Code::Blocks ====

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

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

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

Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.
The stripped ("production") executable is found in <tt>output</tt> together with all libraries and data files. If you want a version with debug symbols instead (caution: huge size!), use the one found in the <tt>devel</tt> folder.<br>
Congratulations, you own a freshly built version of Code::Blocks!

For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/>
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>.

==== Install Code::Blocks ====

Copy the folder output to where you want Code::Blocks to reside.

==== Compile contributed (or your own) plugins ====

The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/>
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. This is the path that contains the sdk folder normally this is codeblocks\src. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.

Don't forget to run update.bat again after building the contrib plugins.

=== ANSI Build ===

<div style="background-color: #f7d9d9; border: 1px solid #000">
<div style="margin: 5px;">

==== DEPRECATION WARNING: ====
As of February 2006, the official default build for Code::Blocks is '''Unicode''' (see above). Although ANSI builds are technically possible, we discourage their use unless there is a good reason.<br/>
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''

There is hardly any good argument against using a Unicode build if your OS supports Unicode, even if you do not understand any other language than English, as a Unicode version guarantees that it will be able to work with whatever languages you may possibly encounter in the future -- at a very reasonable cost.

However, if you absolutely don't care about Unicode or if you are bound to use Windows 95, then you may want to build an ANSI version nevertheless.

</div>
</div>

==== Compile wxWidgets in ANSI mode ====

After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.

'''Optional:'''

To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.

==== Compile Code::Blocks ====

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

'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).

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

After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.

One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).

Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !

==== Install Code::Blocks ====

Copy the folder output to where you want Code::Blocks to reside.

==== Compile contributed (or your own) plugins ====

The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.

Installing Code::Blocks from source on Windows

2007-11-04T12:07:06Z

AlexThis: /* MinGW compiler */

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]
== Prerequisites ==

'''Note for RC2 users'''

The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].

=== MinGW compiler ===

At the present time, Code::Blocks only compiles successfully with the MinGW compiler (or any other gcc for that matter). You will need a complete, working [[MinGW installation]].

Since November 2007 MinGW-GCC 4.2.1

=== wxWidgets ===

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

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

You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').

=== SVN client ===

In order to check out the Code::Blocks sources you will need a SVN client.
For convenience, it is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn command-line client] equally well.

It is generally a good idea to install the command-line client (and adding it to PATH) even if you use TortoiseSVN for convenience. The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn</tt> binary if it is available. This is preferrable to the manual parsing of the entries file that is used as fallback.

Please do note that working copies checked out with the 1.4 version of Subversion are no longer compatible with earlier versions (Subversion will transparently update existing repositories).

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

=== zip.exe ===

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

The zip program coming with cygwin will ''not'' work properly. You do ''not'' need WinZip.

Make sure the zip binary is in your PATH so the <tt>update.bat</tt> script will be able to find it (alternatively, you can edit the batch file, setting the ZIPCMD variable to something else).

The easiest way is to put zip.exe into <tt>bin</tt> inside your MinGW installation directory (that folder is normally in the path).

=== Code::Blocks sources ===

You will also (obviously) need the Code::Blocks sources.

Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".

In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.

Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:

mkdir codeblocks-head
cd codeblocks-head
svn checkout svn://svn.berlios.de/codeblocks/trunk

== Building ==

=== Unicode Build ===

==== Compile wxWidgets in Unicode mode ====

After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.

'''Optional:'''

To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.

==== Compile Code::Blocks ====

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

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

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

Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.
The stripped ("production") executable is found in <tt>output</tt> together with all libraries and data files. If you want a version with debug symbols instead (caution: huge size!), use the one found in the <tt>devel</tt> folder.<br>
Congratulations, you own a freshly built version of Code::Blocks!

For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/>
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>.

==== Install Code::Blocks ====

Copy the folder output to where you want Code::Blocks to reside.

==== Compile contributed (or your own) plugins ====

The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/>
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. This is the path that contains the sdk folder normally this is codeblocks\src. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.

Don't forget to run update.bat again after building the contrib plugins.

=== ANSI Build ===

<div style="background-color: #f7d9d9; border: 1px solid #000">
<div style="margin: 5px;">

==== DEPRECATION WARNING: ====
As of February 2006, the official default build for Code::Blocks is '''Unicode''' (see above). Although ANSI builds are technically possible, we discourage their use unless there is a good reason.<br/>
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''

There is hardly any good argument against using a Unicode build if your OS supports Unicode, even if you do not understand any other language than English, as a Unicode version guarantees that it will be able to work with whatever languages you may possibly encounter in the future -- at a very reasonable cost.

However, if you absolutely don't care about Unicode or if you are bound to use Windows 95, then you may want to build an ANSI version nevertheless.

</div>
</div>

==== Compile wxWidgets in ANSI mode ====

After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.

'''Optional:'''

To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.

==== Compile Code::Blocks ====

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

'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).

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

After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.

One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).

Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !

==== Install Code::Blocks ====

Copy the folder output to where you want Code::Blocks to reside.

==== Compile contributed (or your own) plugins ====

The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.

Installing Code::Blocks from source on Windows

2007-08-18T23:41:55Z

AlexThis: /* wxWidgets */ new version of wxWidgets

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]
== Prerequisites ==

'''Note for RC2 users'''

The older Code::Blocks RC2 does not support global compiler variables which were added after RC2 was released and is unable to read project files generated with post-RC2 versions.
To build Code::Blocks, you need a post-RC2 build, such as any of the ''nightly builds'' obtainable by [/index.php?board=20.0 searching the forum].

=== MinGW compiler ===

At the present time, Code::Blocks only compiles successfully with the MinGW compiler (or any other gcc for that matter). You will need a complete, working [[MinGW installation]].

=== wxWidgets ===

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

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

You do ''not'' need MSYS (''in fact, if you have MSYS, make sure it is not in your PATH when building wxWidgets'').

=== SVN client ===

In order to check out the Code::Blocks sources you will need a SVN client.
For convenience, it is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine, as this is a lot more comfortable. However, if you get a bad feeling when some program is messing with your Explorer menu, then you can use the [http://subversion.tigris.org/project_packages.html svn command-line client] equally well.

It is generally a good idea to install the command-line client (and adding it to PATH) even if you use TortoiseSVN for convenience. The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn</tt> binary if it is available. This is preferrable to the manual parsing of the entries file that is used as fallback.

Please do note that working copies checked out with the 1.4 version of Subversion are no longer compatible with earlier versions (Subversion will transparently update existing repositories).

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

=== zip.exe ===

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

The zip program coming with cygwin will ''not'' work properly. You do ''not'' need WinZip.

Make sure the zip binary is in your PATH so the <tt>update.bat</tt> script will be able to find it (alternatively, you can edit the batch file, setting the ZIPCMD variable to something else).

The easiest way is to put zip.exe into <tt>bin</tt> inside your MinGW installation directory (that folder is normally in the path).

=== Code::Blocks sources ===

You will also (obviously) need the Code::Blocks sources.

Using ''TortoiseSVN'', make a folder where you want to store the sources, right-click on the folder, and select "SVN Checkout...".

In the top box, enter svn://svn.berlios.de/codeblocks/trunk and hit the OK button.

Using ''svn'', you have to open a command prompt ("DOS Window"). Make a folder, change directory, and run svn:

mkdir codeblocks-head
cd codeblocks-head
svn checkout svn://svn.berlios.de/codeblocks/trunk

== Building ==

=== Unicode Build ===

==== Compile wxWidgets in Unicode mode ====

After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets:

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.

'''Optional:'''

To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.

==== Compile Code::Blocks ====

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

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

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

Run <tt>src\update.bat</tt> (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.
The stripped ("production") executable is found in <tt>output</tt> together with all libraries and data files. If you want a version with debug symbols instead (caution: huge size!), use the one found in the <tt>devel</tt> folder.<br>
Congratulations, you own a freshly built version of Code::Blocks!

For future updates, go into the Code::Blocks root directory and run <tt>svn update</tt> (or use TurtoiseSVN to the same effect).<br/>
Then open and build the project as described before (and any contrib plugins that you wish to use), and re-run <tt>src\update.bat</tt>.

==== Install Code::Blocks ====

Copy the folder output to where you want Code::Blocks to reside.

==== Compile contributed (or your own) plugins ====

The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all).<br/>
When you open the contrib plugins workspace, you will be asked to define the <tt>$(#cb)</tt> global compiler variable. This is the path that contains the sdk folder normally this is codeblocks\src. The build process uses this information to place the plugins and data files into the correct place. Enter the location of the Code::Blocks sources in the same way as for the <tt>$(#wx)</tt> variable earlier.

Don't forget to run update.bat again after building the contrib plugins.

=== ANSI Build ===

<div style="background-color: #f7d9d9; border: 1px solid #000">
<div style="margin: 5px;">

==== DEPRECATION WARNING: ====
As of February 2006, the official default build for Code::Blocks is '''Unicode''' (see above). Although ANSI builds are technically possible, we discourage their use unless there is a good reason.<br/>
''Support for ANSI builds is likely to be dropped after Version 1.0 is out.''

There is hardly any good argument against using a Unicode build if your OS supports Unicode, even if you do not understand any other language than English, as a Unicode version guarantees that it will be able to work with whatever languages you may possibly encounter in the future -- at a very reasonable cost.

However, if you absolutely don't care about Unicode or if you are bound to use Windows 95, then you may want to build an ANSI version nevertheless.

</div>
</div>

==== Compile wxWidgets in ANSI mode ====

After unpacking the zip file to a directory of your choice, open a cmd prompt, and navigate to the folder build/msw inside the wxWidgets folder. Use the following commands to compile wxWidgets

set path=c:\mingw\bin;c:\mingw\mingw32\bin
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0

This assumes your MinGW installation is in C:\mingw. Use a different path if you installed MinGW somewhere else.

You will see a lot of warning messages during compilation. Don't worry, this is normal, you are compiling wxWidgets. The build process may take 10-30 minutes, depending on your computer's speed.

'''Optional:'''

To reduce the size of your wxWidgets library, you can disable features which are not used by Code::Blocks. However, you should not do this unless you know what you are doing. You have to delete the generated setup.h from lib/gcc_dll/msw/wx before building, because your changes to include/wx/msw will otherwise not be honoured.

==== Compile Code::Blocks ====

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

'''Important:''' The project file is set to compile an Unicode version of Code::Blocks by default. To make an ANSI build, you have to make the following two changes to build options before compiling:
1. In the "Compiler" tab, under "#defines", remove the entry wxUSE_UNICODE.
2. Under "Custom variables", set the variable WX_SUFFIX to empty (default value: u).

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

After the compilaton has finished, copy wxmsw26u_gcc_custom.dll from lib\gcc_dll inside the wxWidgets directory to the devel directory inside the Code::Blocks source folder (it will also work if you keep a copy of that library in your Windows folder or anywhere in your system path, but this is generally not recommended because you can get into [http://en.wikipedia.org/wiki/DLL_hell dll hell] ).
Run update.bat (located in the root source directory). This will pack the resource files and copy libraries and plugins to their correct locations.
The location of executable is src\output in C::B tree. From here you'll not need the nighty build anymore.

One little note for svn updates and rebuilds : just go into the codeblocks root directory and do '''svn update''' (or use Turtoise svn).

Then run the src/output/codeblocks.exe, reload project, build it, reload plugins workspace, build it, quit codeblocks and re-run update.bat. You'll have an up-to-date C::B in 3 minutes !

==== Install Code::Blocks ====

Copy the folder output to where you want Code::Blocks to reside.

==== Compile contributed (or your own) plugins ====

The workspace file ContribPlugins.workspace contains the project files for all contributed plugins. Open that workspace and compile the plugins which you would like to use (or select "Build Workspace" from the context menu if you want them all). Don't forget to run update.bat again after building the contrib plugins.

Installing Code::Blocks nightly build on Windows

2007-08-18T23:05:24Z

AlexThis: /* Install steps */ better explanation

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

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

=== Install steps ===

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

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

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

MinGW installation

2007-08-18T22:28:26Z

AlexThis: links to SourceForge optimised

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

MinGW installation

2007-08-18T22:18:27Z

AlexThis: /* Base system with C++ */ consistent links to sourceforge

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Installing Code::Blocks nightly build on Windows

2007-08-18T22:11:25Z

AlexThis: optimised for every version (on has to read forum) looking for newer wxWidgets versions, style, new example

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

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

=== Install steps ===

# [[MinGW_installation|Install ''MinGW'' and the ''GDB debugger'']].
# Download and install [http://www.7-zip.org/ 7-Zip]. You need it to extract the nightly build.
# Download the latest nightly build from the [/index.php?board=20.0 Nightly Builds forum].
# Download the according ''wxWidgets Unicode DLL'' for your nightly build (download link in forum).
# Download the ''mingw10.dll'' for ''Code::Blocks'' [http://download.berlios.de/codeblocks/mingwm10.7z mingwm10.7z] (also mentioned at the nightly build).
# Unzip ''Code::Blocks'' and the ''wxWidgets DLL'' to the same directory.
# Start ''Code::Blocks'' and configure ''GNU GCC compiler''.

*''NOTE'': Step 5 (''mingw10.dll'' download) can be skipped if the bin directory of ''MinGW'' is in your PATH variable '''or''' if you copy ''mingw10.dll'' from \MinGW\bin directory to your unzip-directory of ''Code::Blocks'' an ''wxWidgets DLL''.

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

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