Code::Blocks - User contributions [en]

Installing Code::Blocks from source on Windows

2017-08-22T23:20:00Z

Headkase: /* Build Code::Blocks */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

It is recommended, but not required, that you install a SVN client. An example would be [http://tortoisesvn.net/downloads TortoiseSVN] if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

If you don't wish to use a SVN utility, you can download a snapshot from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot."

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==

=== Self-Hosting ===

All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:17:08Z

Headkase: /* Code::Blocks Sources */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

It is recommended, but not required, that you install a SVN client. An example would be [http://tortoisesvn.net/downloads TortoiseSVN] if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

If you don't wish to use a SVN utility, you can download a snapshot from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot."

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:16:36Z

Headkase: /* Code::Blocks Sources */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

It is recommended, but not required, that you install a SVN client. An example would be [http://tortoisesvn.net/downloads TortoiseSVN] if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

If you don't wish to use a SVN utility, you can download a snapshot from: http://sourceforge.net/p/codeblocks/code/trunk ➡ "Download Snapshot."

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:14:09Z

Headkase: /* SVN */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

It is recommended, but not required, that you install a SVN client. An example would be [http://tortoisesvn.net/downloads TortoiseSVN] if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

If you don't wish to use a SVN utility, you can download a snapshot from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot."

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:12:15Z

Headkase: /* SVN */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

It is recommended, but not required, that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

If you don't wish to use a SVN utility, you can download a snapshot from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot."

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:11:37Z

Headkase: /* Code::Blocks Sources */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

If you don't wish to use a SVN utility, you can download a snapshot from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot."

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:11:12Z

Headkase: /* Code::Blocks Sources */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.
If you don't wish to use a SVN utility, you can download a snapshot from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot."

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:10:39Z

Headkase: /* Prerequisites */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client. If you don't wish to use a SVN utility, you can download a snapshot from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot."

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:04:33Z

Headkase: /* Compile wxWidgets Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:02:20Z

Headkase: /* Configure Build Options */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory there is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Compile wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:01:28Z

Headkase: /* Configure Build Options */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the wxWidgets zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Compile wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T23:00:40Z

Headkase: /* Build wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

=== Configure Build Options ===

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Compile wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T22:58:20Z

Headkase: /* Build wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Compile wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T22:57:23Z

Headkase: /* Build wxWidgets Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Compile wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T22:56:38Z

Headkase: /* wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T22:55:57Z

Headkase: /* Code::Blocks Sources */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

The last item is to acquire the Code::Blocks source code. Follow the appropriate instructions for whether you have a graphical or command line SVN client.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-22T22:50:54Z

Headkase: /* Prerequisites */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-18T07:22:47Z

Headkase: /* TortoiseSVN */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter <tt><nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki></tt> and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-18T07:19:09Z

Headkase: /* Compile contributed (or your own) plugins */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the "[http://www.boost.org/ Boost]" library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-18T07:17:48Z

Headkase: /* wxWidgets */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the "[https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface toolkit]" that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-18T07:16:58Z

Headkase: /* wxWidgets */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site ➡ [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-18T07:16:31Z

Headkase: /* wxWidgets */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site → [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-18T07:16:00Z

Headkase: /* wxWidgets */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-18T07:15:01Z

Headkase: /* SVN */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install: [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-18T07:13:20Z

Headkase: /* Tips */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-08-09T22:12:01Z

Headkase: /* Compile contributed (or your own) plugins */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* ''Advanced'': 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

[[Image:Build_Workspace.png]]

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-31T03:11:34Z

Headkase: /* Build wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* ''Advanced'': 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-30T04:50:24Z

Headkase: /* Build wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this directory is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* ''Advanced'': 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-30T04:50:05Z

Headkase: /* Build wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the directory <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* ''Advanced'': 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-30T04:48:49Z

Headkase: /* Tips */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* ''Advanced'': 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-30T04:48:01Z

Headkase: /* Tips */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-30T04:45:47Z

Headkase: /* Build wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

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

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-30T04:44:45Z

Headkase: /* wxWidgets */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-30T04:44:10Z

Headkase: /* wxWidgets */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

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

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-28T18:44:13Z

Headkase: /* Build wxWidgets Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download wxWidgets 2.8.12:

* wxWidgets 2.8.12 Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

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

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-28T08:04:41Z

Headkase: /* Build wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download wxWidgets 2.8.12:

* wxWidgets 2.8.12 Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

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

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug #269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your root toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-28T08:02:34Z

Headkase: /* Build wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download wxWidgets 2.8.12:

* wxWidgets 2.8.12 Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

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

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

Some versions of the MinGW Windows Runtime Library will cause an error during compilation. See: [https://sourceforge.net/p/tdm-gcc/bugs/269/ Bug# 269]. If this is the case with the toolchain you are using then try this workaround:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your root toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-28T01:58:42Z

Headkase: /* wxWidgets */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] toolkit that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download wxWidgets 2.8.12:

* wxWidgets 2.8.12 Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

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

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

If your compiler errors out, usually referencing monotree.dll or similar:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your root toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

MinGW installation

2017-07-27T08:51:49Z

Headkase: /* Overview */

[[Category:User Documentation]]

== Overview ==

A compiler toolchain is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler toolchain is a very complex undertaking it is not part of Code::Blocks itself but rather is a separate project that Code::Blocks then uses. The kind of compiler toolchains talked about on this page are "MinGW" toolchains. Which means "Minimalist GNU for Windows." And "GNU" expands to "GNU's Not Unix." More information about the GNU project can be found on the [https://www.gnu.org/home.en.html GNU Home Page].

For most MinGW-based compiler toolchains, having your toolchain in your PATH is important because it means that during development the toolchain libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as [https://cmake.org/ CMake] as they will be able to find your compiler toolchain. When you actually distribute your programs to other computers then you will copy the needed .dll files out of your toolchain directory and include them as part of your installer. On your machine they are in your PATH so you always have them, on your users computers they won't have the compiler toolchain so there you provide the .dll files with your program.

== TDM-GCC ==

[http://tdm-gcc.tdragon.net/ TDM-GCC] is the toolchain that will be used as the example for this guide. TDM-GCC statically links the required toolchain libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself. The Code::Blocks team recommends TDM-GCC.

=== Installation ===

Download the on-demand installer and run it.

Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.

[[Image:TDM_Create.png]] [[Image:TDM_Arch.png]]

[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]]

Once you are ready, click Install to proceed.

=== Code::Blocks Configuration ===

Go to your Compiler settings:

[[Image:Compiler_Settings.png]]

And then under the "Toolchain executables" tab (red arrow), click on the ellipsis ("...", blue arrow) and choose the root directory where you installed TDM-GCC 32-bit. Once you have that directory chosen, in the "Program Files" sub-tab (green arrow) area fill out the fields as shown. If you aren't using the TDM-GCC toolchain there might be minor variation in the executable names. If you choose the blue arrow ellipsis ''first'' then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC <tt>bin</tt> directory where the actual programs are.

[[Image:CB_TDM_Toolchain.png]]

Now, go to your Debugger settings:

[[Image:Settings_Debugger.png]]

Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).

[[Image:Debugger_Default.png]]

=== Summary ===

You now have a Code::Blocks environment that is configured to use TDM-GCC 32-bit properly. Using this guide as a template you can easily set up alternative compiler toolchains no matter the source - just follow the same basic procedure.

== Alternative MinGW Compiler Toolchains ==

[http://www.mingw.org/ MinGW] - The original project.

[https://sourceforge.net/projects/mingw-w64/files/ MinGW-Builds] ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.

[http://mingw-w64.org/doku.php Mingw-w64] - The parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.

[http://www.equation.com/servlet/equation.cmd?fa=fortran MinGW Equation] - A package that also provides OpenMP.

==Development Tools==

Normally you should not need many of these tools. ZIP is convenient, especially when: [[Installing_Code::Blocks_from_source_on_Windows | building Code::Blocks itself]], but other than that these tools only serve specialized purposes.

===UnxUtils===

* [https://sourceforge.net/projects/unxutils/ UnxUtils]

===GnuWin32===

*[https://sourceforge.net/projects/gnuwin32/ GnuWin32]

===ZIP===
*[ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn.zip zip-3.0.0 32-bit] or [ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn-x64.zip zip-3.0.0 64-bit]

Installing Code::Blocks from source on Windows

2017-07-27T08:49:04Z

Headkase: /* Build wxWidgets Support Library */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] system that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download wxWidgets 2.8.12:

* wxWidgets 2.8.12 Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

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

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

If your compiler errors out, usually referencing monotree.dll or similar:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. This would be useful for your own 64-bit programs but the Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your root toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-27T08:45:36Z

Headkase: /* MinGW Compiler */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] system that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download wxWidgets 2.8.12:

* wxWidgets 2.8.12 Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

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

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

If your compiler errors out, usually referencing monotree.dll or similar:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. However, there is no point to it. The Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your root toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

Installing Code::Blocks from source on Windows

2017-07-27T08:45:15Z

Headkase: /* MinGW Compiler */

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

=== Self-Hosting ===

The build process described on this page is a kind of "[https://en.wikipedia.org/wiki/Self-hosting Self-Hosting]." You use an existing version of Code::Blocks to compile the next version. When that version is proven to function correctly it is used to compile the next, and so on.

== Prerequisites ==

=== Bootstrap Code::Blocks ===

A properly working Code::Blocks is required to compile the next SVN version. A: [[Installing_Code::Blocks_nightly_build_on_Windows | Nightly Build]] is a good candidate to use. It will be paired with a MinGW compiler in the next item.

=== MinGW Compiler ===

At the present time, Code::Blocks only compiles successfully with a MinGW Compiler toolchain on Windows. You will need a complete, working: [[MinGW installation]].

=== Utilities ===

ZIP and SVN functions are not required to run Code::Blocks but ZIP is required to build it and a SVN client is strongly recommended but not absolutely necessary.

==== ZIP ====

You will need a command-line <tt>zip.exe</tt> program. The recommended one can be found on the: [[MinGW installation#Development Tools|Development Tools]] page. You do ''not'' need WinZip.

Make sure <tt>zip.exe</tt> is in your PATH as it is used both during the compilation in your current version of Code::Blocks and also by the <tt>update.bat</tt> script.

==== SVN ====

You can either download the Code::Blocks source from: http://sourceforge.net/p/codeblocks/code ➡ "Download Snapshot" or use an SVN Client to checkout the code.

It is recommended that you install [http://tortoisesvn.net/downloads TortoiseSVN] on your machine if you would like an all-in-one SVN solution. ''TortoiseSVN'' includes optional command-line client tools, which you should install as they provide a command-line SVN client. Choosing to install the command-line client tools will automatically add them to your PATH. However, if you do not wish to have the ''TortoiseSVN'' Explorer extensions in your right-click context menu or just don't feel a need for a graphical client in particular then you can use another: [http://subversion.apache.org/packages.html SVN command-line client] equally well. Just make sure that whichever client you install has its executable in your PATH.

The <tt>autorevision</tt> tool which is used during the build of Code::Blocks makes use of the <tt>svn.exe</tt> binary if it is available (in your PATH) and also uses the SVN meta-data generated by a SVN checkout. If you have both a SVN command-line client in your PATH, and the meta-data, the resulting build of Code::Blocks will show the revision on the loading splash window, the Start here page, and in the About dialog (shown here in the About dialog, indicated by the red arrow):

[[Image:About_SVN10627.png]]

=== wxWidgets ===

wxWidgets is the [https://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] system that Code::Blocks is built on top of.

For information about wxWidgets, see their official site: [http://www.wxwidgets.org/ wxWidgets.org]

Download wxWidgets 2.8.12:

* wxWidgets 2.8.12 Download: [https://github.com/wxWidgets/wxWidgets/releases/download/v2.8.12/wxMSW-2.8.12.zip wxMSW-2.8.12.zip]

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

=== Code::Blocks Sources ===

Finally, you will need the Code::Blocks sources.

==== TortoiseSVN ====

If you prefer a graphical SVN client you can use ''TortoiseSVN'' - make a directory where you want to store the sources, right-click on the directory, and select "'''SVN Checkout'''," and as shown you will get a checkout dialog:

[[Image:Tor_SVN.png]]

In the URL of the repository box, enter svn://svn.code.sf.net/p/codeblocks/code/trunk and verify the checkout directory is where you would like it to be. The example given here is "''C:\cb_svn''" - once satisfied with the arguments click the OK button to process the checkout.

==== Command-Line SVN ====

If you do not wish to use a graphical SVN client then a command-line equivalent to the above is to use the <tt>svn</tt> command - open a command prompt, make a directory, change into that directory, and then checkout a copy of the repository:

mkdir codeblocks-head
cd codeblocks-head
svn checkout <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

== Build wxWidgets Support Library ==

Unpack the zip file to a directory of your choice, open a command-line prompt, and navigate to the folder <tt>build/msw</tt> inside the wxWidgets directory. In this folder is a text file named <tt>config.gcc</tt> which you can edit with notepad to control the build options. There are two lines to note, <tt>CFLAGS ?=</tt> and <tt>CXXFLAGS ?=</tt>. The options given here will go in either or both of those lines.

If your linker runs out of memory while building use:

-fno-keep-inline-dllexport

If your compiler errors out, usually referencing monotree.dll or similar:

-D_WIN32_IE=0x0603

To silence warnings that can significantly slow down the compilation process:

-Wno-unused-local-typedefs

and

-Wno-deprecated-declarations

All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:

CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

wxWidgets 2.8.12 will not compile by default with a 64-bit compiler. To make it compile with one add <tt>CFG=64</tt> to the build line that is given next. However, there is no point to it. The Code::Blocks project files do not have a 64-bit project that targets wxWidgets 2.8.12. To attempt to modify them so they do is beyond the scope of this guide.

=== Build wxWidgets Library ===

At a command-line, inside the <tt>build/msw</tt> directory, use the following commands to build wxWidgets:

mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1

If your compiler toolchain is not in your PATH, it should be on a development machine, then put it in your path first:

set PATH=X:\path\to\toolchain\bin;%PATH%

Where "'''''X'''''" is the drive letter, and "'''''\path\to\toolchain\bin'''''" is where your root toolchain is located.

If your compilation fails for any reason then make sure to run the ''clean'' line before trying again.

=== Tips ===

* If you want to use wxWidgets not only for building Code::Blocks, but also for writing wxWidgets programs, and if you want to use the debugger in those programs, you have to compile a debug build of wxWidgets as well. ''Use the same commands as for the release build, but replace "release" with "debug".''

* Advanced: 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 <tt>setup.h</tt> from <tt>lib/gcc_dll/msw/wx</tt> before building, because your changes to <tt>include/wx/msw</tt> will otherwise not be honored.

== Build Code::Blocks ==
All the preparation work is now complete and we can actually perform a self-hosting compile of the next Code::Blocks with our current one. If you do not make any changes to your non-Code::Blocks prepared items, like your MinGW compiler version, and the wxWidgets library, then when building subsequent SVN versions of Code::Blocks you can keep all the preparation from a previous build and start with this section. When restarting from this point you can refresh your current Code::Blocks local source with ''TortoiseSVN''. Right-click on your local source directory, go to "TortoiseSVN" in the context-menu, then choose "update to revision." The "head" is always the latest version. If you are using a command-line SVN, just run <tt>svn update</tt> in the root of your local source directory.

=== Open project ===
Open the project file '''CodeBlocks.cbp'''.
*You will be prompted to define the global variable $(#wx). In the base field, enter the root of the location where you unpacked wxWidgets.

*You will also be prompted to enter the global variable '''cb_release_type'''. Here you can add compiler optimization or debug-flags. Enter '''-g''' in the '''base''' field as a default or any other options you require for your specific needs.

[[Image:Global_Variables.png]]

[[Image:Global_wx.png]]

=== Prevent unnecessary warnings ===

Building Code::Blocks against the wxWidgets library will generate an excessive amount of warnings during the compilation. This can significantly impact the time it takes to compile both the main project and the contributors workspace as each warning has to be printed to the build log. To silence these warnings, go to Compiler Settings:

[[Image:Compiler_Settings.png]]

And under the "Compiler settings" tab (red arrow), "Other compiler options" sub-tab (green arrow), enter "<tt>-Wno-unused-local-typedefs</tt>" (blue arrow), and you may also add "<tt>-Wno-deprecated-declarations</tt>" on its own line here too.

[[Image:Unused_Local_Typedefs.png]]

=== Compile project ===
Make sure that "All" is selected as the target (blue arrow), and then click the Build icon (red arrow).

[[Image:Compile_All.png]]

If everything builds correctly your build messages should end with no errors.

[[Image:Build_Log.png]]

=== Copy wxWidgets support DLL ===
After the compilation has finished, copy <tt>lib\gcc_dll\wxmsw28u_gcc_custom.dll</tt> from the wxWidgets directory to the <tt>devel</tt> directory in the Code::Blocks <tt>src</tt> directory.

[[Image:Update_Devel_Output.png]]

The <tt>devel</tt> directory is created by compiling the Code::Blocks project in Code::Blocks.

=== Generate Production Output ===
Run <tt>update.bat</tt> (located in the <tt>src</tt> directory). This will pack the resource files and copy the executables, libraries, and plugins to the <tt>output</tt> directory. It will also create the <tt>output</tt> directory if it does not exist.

[[Image:Update_bat.png]]

The stripped ("production") executable is found in <tt>output</tt> directory 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> directory.

[[Image:Update_Output.png]]

=== 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 Build menu if you want them all).

The NassiShneiderman plugin has a dependency on the [http://www.boost.org/ Boost] library. If you do not wish to use that plugin and therefore not need the library, just right-click on that plugin and choose "close project."

[[Image:Build_Workspace.png]]

Don't forget to run <tt>update.bat</tt> again after building the contributed plugins.

== Install Code::Blocks ==

Copy or move the <tt>output</tt> directory to where you want Code::Blocks to reside. You probably want to rename the <tt>output</tt> directory to something else. You can also optionally right-click on <tt>codeblocks.exe</tt> and choose "create shortcut" and then rename that shortcut to your liking and move it to another location such as your desktop for easy access.

If you want to run Code::Blocks on a machine without your compiler toolchain being in the PATH then you will likely have to include, in the same directory as the <tt>codeblocks.exe</tt> is fine, support .dll files from your compiler toolchain. The easiest way to determine the required files is to not have your compiler toolchain in your PATH and repeatedly run Code::Blocks and copy over each .dll it says is missing until all have been found.

MinGW installation

2017-07-27T08:29:44Z

Headkase: /* TDM-GCC */

[[Category:User Documentation]]

== Overview ==

A compiler toolchain is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler toolchain is a very complex undertaking it is not part of Code::Blocks itself but rather is a separate project that Code::Blocks then uses. The kind of compiler toolchains talked about on this page are "MinGW" toolchains. That means "Minimalist GNU for Windows." And "GNU" expands to "GNU's Not Unix." More information about the GNU project can be found on the [https://www.gnu.org/home.en.html GNU Home Page].

For most MinGW-based compiler toolchains, having your toolchain in your PATH is important because it means that during development the toolchain libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as [https://cmake.org/ CMake] as they will be able to find your compiler toolchain. When you actually distribute your programs to other computers then you will copy the needed .dll files out of your toolchain directory and include them as part of your installer. On your machine they are in your PATH so you always have them, on your users computers they won't have the compiler toolchain so there you provide the .dll files with your program.

== TDM-GCC ==

[http://tdm-gcc.tdragon.net/ TDM-GCC] is the toolchain that will be used as the example for this guide. TDM-GCC statically links the required toolchain libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself. The Code::Blocks team recommends TDM-GCC.

=== Installation ===

Download the on-demand installer and run it.

Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.

[[Image:TDM_Create.png]] [[Image:TDM_Arch.png]]

[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]]

Once you are ready, click Install to proceed.

=== Code::Blocks Configuration ===

Go to your Compiler settings:

[[Image:Compiler_Settings.png]]

And then under the "Toolchain executables" tab (red arrow), click on the ellipsis ("...", blue arrow) and choose the root directory where you installed TDM-GCC 32-bit. Once you have that directory chosen, in the "Program Files" sub-tab (green arrow) area fill out the fields as shown. If you aren't using the TDM-GCC toolchain there might be minor variation in the executable names. If you choose the blue arrow ellipsis ''first'' then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC <tt>bin</tt> directory where the actual programs are.

[[Image:CB_TDM_Toolchain.png]]

Now, go to your Debugger settings:

[[Image:Settings_Debugger.png]]

Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).

[[Image:Debugger_Default.png]]

=== Summary ===

You now have a Code::Blocks environment that is configured to use TDM-GCC 32-bit properly. Using this guide as a template you can easily set up alternative compiler toolchains no matter the source - just follow the same basic procedure.

== Alternative MinGW Compiler Toolchains ==

[http://www.mingw.org/ MinGW] - The original project.

[https://sourceforge.net/projects/mingw-w64/files/ MinGW-Builds] ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.

[http://mingw-w64.org/doku.php Mingw-w64] - The parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.

[http://www.equation.com/servlet/equation.cmd?fa=fortran MinGW Equation] - A package that also provides OpenMP.

==Development Tools==

Normally you should not need many of these tools. ZIP is convenient, especially when: [[Installing_Code::Blocks_from_source_on_Windows | building Code::Blocks itself]], but other than that these tools only serve specialized purposes.

===UnxUtils===

* [https://sourceforge.net/projects/unxutils/ UnxUtils]

===GnuWin32===

*[https://sourceforge.net/projects/gnuwin32/ GnuWin32]

===ZIP===
*[ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn.zip zip-3.0.0 32-bit] or [ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn-x64.zip zip-3.0.0 64-bit]

MinGW installation

2017-07-27T08:29:22Z

Headkase: /* TDM-GCC */

[[Category:User Documentation]]

== Overview ==

A compiler toolchain is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler toolchain is a very complex undertaking it is not part of Code::Blocks itself but rather is a separate project that Code::Blocks then uses. The kind of compiler toolchains talked about on this page are "MinGW" toolchains. That means "Minimalist GNU for Windows." And "GNU" expands to "GNU's Not Unix." More information about the GNU project can be found on the [https://www.gnu.org/home.en.html GNU Home Page].

For most MinGW-based compiler toolchains, having your toolchain in your PATH is important because it means that during development the toolchain libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as [https://cmake.org/ CMake] as they will be able to find your compiler toolchain. When you actually distribute your programs to other computers then you will copy the needed .dll files out of your toolchain directory and include them as part of your installer. On your machine they are in your PATH so you always have them, on your users computers they won't have the compiler toolchain so there you provide the .dll files with your program.

== TDM-GCC ==

[http://tdm-gcc.tdragon.net/ TDM-GCC] is the toolchain that will be used as the example for this guide. TDM-GCC statically links the required toolchain libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself. The Code::Blocks team recommends TDM builds of MinGW.

=== Installation ===

Download the on-demand installer and run it.

Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.

[[Image:TDM_Create.png]] [[Image:TDM_Arch.png]]

[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]]

Once you are ready, click Install to proceed.

=== Code::Blocks Configuration ===

Go to your Compiler settings:

[[Image:Compiler_Settings.png]]

And then under the "Toolchain executables" tab (red arrow), click on the ellipsis ("...", blue arrow) and choose the root directory where you installed TDM-GCC 32-bit. Once you have that directory chosen, in the "Program Files" sub-tab (green arrow) area fill out the fields as shown. If you aren't using the TDM-GCC toolchain there might be minor variation in the executable names. If you choose the blue arrow ellipsis ''first'' then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC <tt>bin</tt> directory where the actual programs are.

[[Image:CB_TDM_Toolchain.png]]

Now, go to your Debugger settings:

[[Image:Settings_Debugger.png]]

Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).

[[Image:Debugger_Default.png]]

=== Summary ===

You now have a Code::Blocks environment that is configured to use TDM-GCC 32-bit properly. Using this guide as a template you can easily set up alternative compiler toolchains no matter the source - just follow the same basic procedure.

== Alternative MinGW Compiler Toolchains ==

[http://www.mingw.org/ MinGW] - The original project.

[https://sourceforge.net/projects/mingw-w64/files/ MinGW-Builds] ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.

[http://mingw-w64.org/doku.php Mingw-w64] - The parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.

[http://www.equation.com/servlet/equation.cmd?fa=fortran MinGW Equation] - A package that also provides OpenMP.

==Development Tools==

Normally you should not need many of these tools. ZIP is convenient, especially when: [[Installing_Code::Blocks_from_source_on_Windows | building Code::Blocks itself]], but other than that these tools only serve specialized purposes.

===UnxUtils===

* [https://sourceforge.net/projects/unxutils/ UnxUtils]

===GnuWin32===

*[https://sourceforge.net/projects/gnuwin32/ GnuWin32]

===ZIP===
*[ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn.zip zip-3.0.0 32-bit] or [ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn-x64.zip zip-3.0.0 64-bit]

MinGW installation

2017-07-27T08:27:06Z

Headkase: /* Overview */

[[Category:User Documentation]]

== Overview ==

A compiler toolchain is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler toolchain is a very complex undertaking it is not part of Code::Blocks itself but rather is a separate project that Code::Blocks then uses. The kind of compiler toolchains talked about on this page are "MinGW" toolchains. That means "Minimalist GNU for Windows." And "GNU" expands to "GNU's Not Unix." More information about the GNU project can be found on the [https://www.gnu.org/home.en.html GNU Home Page].

For most MinGW-based compiler toolchains, having your toolchain in your PATH is important because it means that during development the toolchain libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as [https://cmake.org/ CMake] as they will be able to find your compiler toolchain. When you actually distribute your programs to other computers then you will copy the needed .dll files out of your toolchain directory and include them as part of your installer. On your machine they are in your PATH so you always have them, on your users computers they won't have the compiler toolchain so there you provide the .dll files with your program.

== TDM-GCC ==

[http://tdm-gcc.tdragon.net/ TDM-GCC] is the toolchain that will be used as the example for this guide. The Code::Blocks team recommends TDM builds of MinGW. TDM-GCC statically links the required toolchain libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself.

=== Installation ===

Download the on-demand installer and run it.

Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.

[[Image:TDM_Create.png]] [[Image:TDM_Arch.png]]

[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]]

Once you are ready, click Install to proceed.

=== Code::Blocks Configuration ===

Go to your Compiler settings:

[[Image:Compiler_Settings.png]]

And then under the "Toolchain executables" tab (red arrow), click on the ellipsis ("...", blue arrow) and choose the root directory where you installed TDM-GCC 32-bit. Once you have that directory chosen, in the "Program Files" sub-tab (green arrow) area fill out the fields as shown. If you aren't using the TDM-GCC toolchain there might be minor variation in the executable names. If you choose the blue arrow ellipsis ''first'' then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC <tt>bin</tt> directory where the actual programs are.

[[Image:CB_TDM_Toolchain.png]]

Now, go to your Debugger settings:

[[Image:Settings_Debugger.png]]

Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).

[[Image:Debugger_Default.png]]

=== Summary ===

You now have a Code::Blocks environment that is configured to use TDM-GCC 32-bit properly. Using this guide as a template you can easily set up alternative compiler toolchains no matter the source - just follow the same basic procedure.

== Alternative MinGW Compiler Toolchains ==

[http://www.mingw.org/ MinGW] - The original project.

[https://sourceforge.net/projects/mingw-w64/files/ MinGW-Builds] ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.

[http://mingw-w64.org/doku.php Mingw-w64] - The parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.

[http://www.equation.com/servlet/equation.cmd?fa=fortran MinGW Equation] - A package that also provides OpenMP.

==Development Tools==

Normally you should not need many of these tools. ZIP is convenient, especially when: [[Installing_Code::Blocks_from_source_on_Windows | building Code::Blocks itself]], but other than that these tools only serve specialized purposes.

===UnxUtils===

* [https://sourceforge.net/projects/unxutils/ UnxUtils]

===GnuWin32===

*[https://sourceforge.net/projects/gnuwin32/ GnuWin32]

===ZIP===
*[ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn.zip zip-3.0.0 32-bit] or [ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn-x64.zip zip-3.0.0 64-bit]

MinGW installation

2017-07-27T08:25:58Z

Headkase: /* Overview */

[[Category:User Documentation]]

== Overview ==

A compiler toolchain is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler toolchain is a very complex undertaking it is not part of Code::Blocks itself but rather is a separate project that Code::Blocks then uses. The kind of compiler toolchains talked about on this page are "MinGW" toolchains. That means "Minimalist GNU for Windows." And "GNU" expands to "GNU's Not Unix." More information about the GNU project can be foundon the [https://www.gnu.org/home.en.html GNU Home Page].

For most MinGW-based compiler toolchains, having your toolchain in your PATH is important because it means that during development the toolchain libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as [https://cmake.org/ CMake] as they will be able to find your compiler toolchain. When you actually distribute your programs to other computers then you will copy the needed .dll files out of your toolchain directory and include them as part of your installer. On your machine they are in your PATH so you always have them, on your users computers they won't have the compiler toolchain so there you provide the .dll files with your program.

== TDM-GCC ==

[http://tdm-gcc.tdragon.net/ TDM-GCC] is the toolchain that will be used as the example for this guide. The Code::Blocks team recommends TDM builds of MinGW. TDM-GCC statically links the required toolchain libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself.

=== Installation ===

Download the on-demand installer and run it.

Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.

[[Image:TDM_Create.png]] [[Image:TDM_Arch.png]]

[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]]

Once you are ready, click Install to proceed.

=== Code::Blocks Configuration ===

Go to your Compiler settings:

[[Image:Compiler_Settings.png]]

And then under the "Toolchain executables" tab (red arrow), click on the ellipsis ("...", blue arrow) and choose the root directory where you installed TDM-GCC 32-bit. Once you have that directory chosen, in the "Program Files" sub-tab (green arrow) area fill out the fields as shown. If you aren't using the TDM-GCC toolchain there might be minor variation in the executable names. If you choose the blue arrow ellipsis ''first'' then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC <tt>bin</tt> directory where the actual programs are.

[[Image:CB_TDM_Toolchain.png]]

Now, go to your Debugger settings:

[[Image:Settings_Debugger.png]]

Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).

[[Image:Debugger_Default.png]]

=== Summary ===

You now have a Code::Blocks environment that is configured to use TDM-GCC 32-bit properly. Using this guide as a template you can easily set up alternative compiler toolchains no matter the source - just follow the same basic procedure.

== Alternative MinGW Compiler Toolchains ==

[http://www.mingw.org/ MinGW] - The original project.

[https://sourceforge.net/projects/mingw-w64/files/ MinGW-Builds] ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.

[http://mingw-w64.org/doku.php Mingw-w64] - The parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.

[http://www.equation.com/servlet/equation.cmd?fa=fortran MinGW Equation] - A package that also provides OpenMP.

==Development Tools==

Normally you should not need many of these tools. ZIP is convenient, especially when: [[Installing_Code::Blocks_from_source_on_Windows | building Code::Blocks itself]], but other than that these tools only serve specialized purposes.

===UnxUtils===

* [https://sourceforge.net/projects/unxutils/ UnxUtils]

===GnuWin32===

*[https://sourceforge.net/projects/gnuwin32/ GnuWin32]

===ZIP===
*[ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn.zip zip-3.0.0 32-bit] or [ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn-x64.zip zip-3.0.0 64-bit]

MinGW installation

2017-07-27T08:24:06Z

Headkase: /* Overview */

[[Category:User Documentation]]

== Overview ==

A compiler toolchain is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler toolchain is a very complex undertaking it is not part of Code::Blocks itself but rather is a separate project that Code::Blocks then uses. The kind of compiler toolchains talked about on this page are "MinGW" toolchains. That means "Minimalist GNU for Windows." And "GNU" expands to "GNU's Not Unix." More information about the GNU project can be found: [https://www.gnu.org/home.en.html here].

For most MinGW-based compiler toolchains, having your toolchain in your PATH is important because it means that during development the toolchain libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as [https://cmake.org/ CMake] as they will be able to find your compiler toolchain. When you actually distribute your programs to other computers then you will copy the needed .dll files out of your toolchain directory and include them as part of your installer. On your machine they are in your PATH so you always have them, on your users computers they won't have the compiler toolchain so there you provide the .dll files with your program.

== TDM-GCC ==

[http://tdm-gcc.tdragon.net/ TDM-GCC] is the toolchain that will be used as the example for this guide. The Code::Blocks team recommends TDM builds of MinGW. TDM-GCC statically links the required toolchain libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself.

=== Installation ===

Download the on-demand installer and run it.

Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.

[[Image:TDM_Create.png]] [[Image:TDM_Arch.png]]

[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]]

Once you are ready, click Install to proceed.

=== Code::Blocks Configuration ===

Go to your Compiler settings:

[[Image:Compiler_Settings.png]]

And then under the "Toolchain executables" tab (red arrow), click on the ellipsis ("...", blue arrow) and choose the root directory where you installed TDM-GCC 32-bit. Once you have that directory chosen, in the "Program Files" sub-tab (green arrow) area fill out the fields as shown. If you aren't using the TDM-GCC toolchain there might be minor variation in the executable names. If you choose the blue arrow ellipsis ''first'' then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC <tt>bin</tt> directory where the actual programs are.

[[Image:CB_TDM_Toolchain.png]]

Now, go to your Debugger settings:

[[Image:Settings_Debugger.png]]

Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).

[[Image:Debugger_Default.png]]

=== Summary ===

You now have a Code::Blocks environment that is configured to use TDM-GCC 32-bit properly. Using this guide as a template you can easily set up alternative compiler toolchains no matter the source - just follow the same basic procedure.

== Alternative MinGW Compiler Toolchains ==

[http://www.mingw.org/ MinGW] - The original project.

[https://sourceforge.net/projects/mingw-w64/files/ MinGW-Builds] ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.

[http://mingw-w64.org/doku.php Mingw-w64] - The parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.

[http://www.equation.com/servlet/equation.cmd?fa=fortran MinGW Equation] - A package that also provides OpenMP.

==Development Tools==

Normally you should not need many of these tools. ZIP is convenient, especially when: [[Installing_Code::Blocks_from_source_on_Windows | building Code::Blocks itself]], but other than that these tools only serve specialized purposes.

===UnxUtils===

* [https://sourceforge.net/projects/unxutils/ UnxUtils]

===GnuWin32===

*[https://sourceforge.net/projects/gnuwin32/ GnuWin32]

===ZIP===
*[ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn.zip zip-3.0.0 32-bit] or [ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn-x64.zip zip-3.0.0 64-bit]

MinGW installation

2017-07-27T08:22:54Z

Headkase: /* TDM-GCC */

[[Category:User Documentation]]

== Overview ==

A compiler toolchain is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler toolchain is a very complex undertaking it is not part of Code::Blocks itself but rather is a separate project that Code::Blocks then uses. The kind of compiler toolchains talked about in this page are "MinGW" toolchains. That means "Minimalist GNU for Windows." And "GNU" expands to "GNU's Not Unix." More information about the GNU project can be found: [https://www.gnu.org/home.en.html here].

For most MinGW-based compiler toolchains, having your toolchain in your PATH is important because it means that during development the toolchain libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as [https://cmake.org/ CMake] as they will be able to find your compiler toolchain. When you actually distribute your programs to other computers then you will copy the needed .dll files out of your toolchain directory and include them as part of your installer. On your machine they are in your PATH so you always have them, on your users computers they won't have the compiler toolchain so there you provide the .dll files with your program.

== TDM-GCC ==

[http://tdm-gcc.tdragon.net/ TDM-GCC] is the toolchain that will be used as the example for this guide. The Code::Blocks team recommends TDM builds of MinGW. TDM-GCC statically links the required toolchain libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself.

=== Installation ===

Download the on-demand installer and run it.

Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.

[[Image:TDM_Create.png]] [[Image:TDM_Arch.png]]

[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]]

Once you are ready, click Install to proceed.

=== Code::Blocks Configuration ===

Go to your Compiler settings:

[[Image:Compiler_Settings.png]]

And then under the "Toolchain executables" tab (red arrow), click on the ellipsis ("...", blue arrow) and choose the root directory where you installed TDM-GCC 32-bit. Once you have that directory chosen, in the "Program Files" sub-tab (green arrow) area fill out the fields as shown. If you aren't using the TDM-GCC toolchain there might be minor variation in the executable names. If you choose the blue arrow ellipsis ''first'' then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC <tt>bin</tt> directory where the actual programs are.

[[Image:CB_TDM_Toolchain.png]]

Now, go to your Debugger settings:

[[Image:Settings_Debugger.png]]

Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).

[[Image:Debugger_Default.png]]

=== Summary ===

You now have a Code::Blocks environment that is configured to use TDM-GCC 32-bit properly. Using this guide as a template you can easily set up alternative compiler toolchains no matter the source - just follow the same basic procedure.

== Alternative MinGW Compiler Toolchains ==

[http://www.mingw.org/ MinGW] - The original project.

[https://sourceforge.net/projects/mingw-w64/files/ MinGW-Builds] ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.

[http://mingw-w64.org/doku.php Mingw-w64] - The parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.

[http://www.equation.com/servlet/equation.cmd?fa=fortran MinGW Equation] - A package that also provides OpenMP.

==Development Tools==

Normally you should not need many of these tools. ZIP is convenient, especially when: [[Installing_Code::Blocks_from_source_on_Windows | building Code::Blocks itself]], but other than that these tools only serve specialized purposes.

===UnxUtils===

* [https://sourceforge.net/projects/unxutils/ UnxUtils]

===GnuWin32===

*[https://sourceforge.net/projects/gnuwin32/ GnuWin32]

===ZIP===
*[ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn.zip zip-3.0.0 32-bit] or [ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn-x64.zip zip-3.0.0 64-bit]

MinGW installation

2017-07-27T08:21:50Z

Headkase: /* Overview */

[[Category:User Documentation]]

== Overview ==

A compiler toolchain is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler toolchain is a very complex undertaking it is not part of Code::Blocks itself but rather is a separate project that Code::Blocks then uses. The kind of compiler toolchains talked about in this page are "MinGW" toolchains. That means "Minimalist GNU for Windows." And "GNU" expands to "GNU's Not Unix." More information about the GNU project can be found: [https://www.gnu.org/home.en.html here].

For most MinGW-based compiler toolchains, having your toolchain in your PATH is important because it means that during development the toolchain libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as [https://cmake.org/ CMake] as they will be able to find your compiler toolchain. When you actually distribute your programs to other computers then you will copy the needed .dll files out of your toolchain directory and include them as part of your installer. On your machine they are in your PATH so you always have them, on your users computers they won't have the compiler toolchain so there you provide the .dll files with your program.

== TDM-GCC ==

[http://tdm-gcc.tdragon.net/ TDM-GCC] is the toolchain that will be used as the example for this guide. The Code::Blocks team recommends TDM builds of MinGW.

=== Installation ===

Download the on-demand installer and run it.

Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.

[[Image:TDM_Create.png]] [[Image:TDM_Arch.png]]

[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]]

Once you are ready, click Install to proceed.

=== Code::Blocks Configuration ===

Go to your Compiler settings:

[[Image:Compiler_Settings.png]]

And then under the "Toolchain executables" tab (red arrow), click on the ellipsis ("...", blue arrow) and choose the root directory where you installed TDM-GCC 32-bit. Once you have that directory chosen, in the "Program Files" sub-tab (green arrow) area fill out the fields as shown. If you aren't using the TDM-GCC toolchain there might be minor variation in the executable names. If you choose the blue arrow ellipsis ''first'' then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC <tt>bin</tt> directory where the actual programs are.

[[Image:CB_TDM_Toolchain.png]]

Now, go to your Debugger settings:

[[Image:Settings_Debugger.png]]

Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).

[[Image:Debugger_Default.png]]

=== Summary ===

You now have a Code::Blocks environment that is configured to use TDM-GCC 32-bit properly. Using this guide as a template you can easily set up alternative compiler toolchains no matter the source - just follow the same basic procedure.

== Alternative MinGW Compiler Toolchains ==

[http://www.mingw.org/ MinGW] - The original project.

[https://sourceforge.net/projects/mingw-w64/files/ MinGW-Builds] ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.

[http://mingw-w64.org/doku.php Mingw-w64] - The parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.

[http://www.equation.com/servlet/equation.cmd?fa=fortran MinGW Equation] - A package that also provides OpenMP.

==Development Tools==

Normally you should not need many of these tools. ZIP is convenient, especially when: [[Installing_Code::Blocks_from_source_on_Windows | building Code::Blocks itself]], but other than that these tools only serve specialized purposes.

===UnxUtils===

* [https://sourceforge.net/projects/unxutils/ UnxUtils]

===GnuWin32===

*[https://sourceforge.net/projects/gnuwin32/ GnuWin32]

===ZIP===
*[ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn.zip zip-3.0.0 32-bit] or [ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn-x64.zip zip-3.0.0 64-bit]

MinGW installation

2017-07-27T08:19:44Z

Headkase: /* Overview */

[[Category:User Documentation]]

== Overview ==

A compiler toolchain is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler toolchain is a very complex undertaking it is not part of Code::Blocks itself but rather is a separate project that Code::Blocks then uses. The kind of compiler toolchains talked about in this page are "MinGW" toolchains. That means "Minimalist GNU for Windows." And "GNU" expands to "GNU's Not Unix." More information about the GNU project can be found: [https://www.gnu.org/home.en.html here].

For most MinGW-based compiler toolchains, having your toolchain in your PATH is important because it means that during development the toolchain libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as [https://cmake.org/ CMake] as they will be able to find your compiler toolchain. When you actually distribute your programs to other computers then you will copy the needed .dll files out of your toolchain directory and include them as part of your installer. On your machine they are in your PATH so you always have them, on your users computers they won't have the compiler toolchain so there you provide the .dll files with your program.

TDM-GCC does not strictly follow the preceding however, it tends to statically link the required libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself.

== TDM-GCC ==

[http://tdm-gcc.tdragon.net/ TDM-GCC] is the toolchain that will be used as the example for this guide. The Code::Blocks team recommends TDM builds of MinGW.

=== Installation ===

Download the on-demand installer and run it.

Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.

[[Image:TDM_Create.png]] [[Image:TDM_Arch.png]]

[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]]

Once you are ready, click Install to proceed.

=== Code::Blocks Configuration ===

Go to your Compiler settings:

[[Image:Compiler_Settings.png]]

And then under the "Toolchain executables" tab (red arrow), click on the ellipsis ("...", blue arrow) and choose the root directory where you installed TDM-GCC 32-bit. Once you have that directory chosen, in the "Program Files" sub-tab (green arrow) area fill out the fields as shown. If you aren't using the TDM-GCC toolchain there might be minor variation in the executable names. If you choose the blue arrow ellipsis ''first'' then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC <tt>bin</tt> directory where the actual programs are.

[[Image:CB_TDM_Toolchain.png]]

Now, go to your Debugger settings:

[[Image:Settings_Debugger.png]]

Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).

[[Image:Debugger_Default.png]]

=== Summary ===

You now have a Code::Blocks environment that is configured to use TDM-GCC 32-bit properly. Using this guide as a template you can easily set up alternative compiler toolchains no matter the source - just follow the same basic procedure.

== Alternative MinGW Compiler Toolchains ==

[http://www.mingw.org/ MinGW] - The original project.

[https://sourceforge.net/projects/mingw-w64/files/ MinGW-Builds] ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.

[http://mingw-w64.org/doku.php Mingw-w64] - The parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.

[http://www.equation.com/servlet/equation.cmd?fa=fortran MinGW Equation] - A package that also provides OpenMP.

==Development Tools==

Normally you should not need many of these tools. ZIP is convenient, especially when: [[Installing_Code::Blocks_from_source_on_Windows | building Code::Blocks itself]], but other than that these tools only serve specialized purposes.

===UnxUtils===

* [https://sourceforge.net/projects/unxutils/ UnxUtils]

===GnuWin32===

*[https://sourceforge.net/projects/gnuwin32/ GnuWin32]

===ZIP===
*[ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn.zip zip-3.0.0 32-bit] or [ftp://ftp.info-zip.org/pub/infozip/win32/zip300xn-x64.zip zip-3.0.0 64-bit]