Code::Blocks - User contributions [en]

Main Page

2025-03-31T10:08:23Z

MichaelAgarkov: Set version to 25.03

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

Wiki Editors: In order to edit pages, you must create an account on the [https://forums.codeblocks.org/ forums] and authenticate there. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

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


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

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

|-

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

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


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

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


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

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

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


|}
</div>

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

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

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

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

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

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

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

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

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/binaries 25.03]
* Nightly builds: [https://forums.codeblocks.org/index.php/board,20.0.html Forum board]
* Source code: [https://www.codeblocks.org/downloads/source 25.03], [https://www.codeblocks.org/downloads/svn current trunk]
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [https://forums.codeblocks.org/ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3ABug_Report+or+_type%3AUndefined bugs] or browse [http://alpha0010.github.io/cb-history/bugs.html old bugs]
* '''Features''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3AFeature_Request+or+_type%3AUndefined features] or browse [http://alpha0010.github.io/cb-history/features.html old features]
* '''Patches''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3APatch+or+_type%3AUndefined patches] or browse [http://alpha0010.github.io/cb-history/patches.html old patches]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [https://www.mingw-w64.org/ MinGW-w64] (Win)
* [https://github.com/jmeubank/tdm-gcc/ TDM GCC] (Win)
* [https://www.msys2.org/ MSYS2] (Win)
* [https://www.cygwin.com/ Cygwin] (Win)
* [https://winlibs.com/ WinLibs GCC] (Win)
* [https://osdn.net/projects/mingw/ MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore and PowerPC GCC] (Win32, Linux)
* [https://developer.apple.com/xcode/ Apple XCode (GCC)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [https://visualstudio.microsoft.com/vs/community/ Microsoft Visual Community Edition] (Win)
* [http://altd.embarcadero.com/download/bcppbuilder/freecommandLinetools.exe Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [https://github.com/open-watcom/open-watcom-v2 OpenWatcom V2] (Win32)
* [https://software.intel.com/en-us/c-compilers Intel C++ compiler] (Win32)
* [https://bellard.org/tcc/ Tiny C compiler] (Win32, Linux)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://dlang.org/ Digital Mars D] (Win32, Linux, Mac OS X)
* [https://gdcproject.org/ GDC D Compiler] (Linux)
* [https://github.com/ldc-developers/ldc/ LLVM D Compiler] (Win32, Linux, Mac OS X)
}}
|}

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

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

Talk:DevPak Installer plugin

2025-03-20T15:56:13Z

MichaelAgarkov: /* DevPak installer works? */ new section

== DevPak installer works? ==

Does the DevPak installer still work to this day? It tries to connect to a now offline site and doesn't let the user change it.

Talk:DevPak Installer plugin

2025-03-20T15:54:28Z

MichaelAgarkov: Created blank page

User:MichaelAgarkov

2025-03-17T21:24:11Z

MichaelAgarkov: Change my contact email

Contact email: [mailto:michaelagarkov@michaelagarkov.ru michaelagarkov@michaelagarkov.ru]

Personal Git server: https://michaelagarkov.ru/MichaelAgarkov

Codeberg: https://codeberg.org/MichaelAgarkov

User:MichaelAgarkov

2025-03-17T16:24:44Z

MichaelAgarkov: Added my personal Git server link

Contact email: [mailto:michaelagarkov@internet.ru michaelagarkov@internet.ru]

Codeberg: https://codeberg.org/MichaelAgarkov

Personal Git server: https://michaelagarkov.ru/MichaelAgarkov

Developer documentation

2025-03-12T22:46:58Z

MichaelAgarkov:

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
{{Layout_box2|1=
'''Official Code repository Subversion''' 
* Web-interface by ViewVC: http://sourceforge.net/p/codeblocks/code/log/
* Subversion URL: <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki> or <nowiki>http://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

'''Mirror by Carsten Arnholm''' (Read-only; )
* Web-interface: https://github.com/arnholm/codeblocks_sfmirror
* Git URL: see the above page.

'''Mirror by biplab''' (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)
* Subversion URL: <nowiki>svn://cb.biplab.in/codeblocks/trunk</nowiki> 
* Web-interface: http://cb.biplab.in/websvn/
* Git URL: git://cb.biplab.in/codeblocks.git
* Web-interface:http://cb.biplab.in/cgit/

'''Mirror by Jens''' (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)
* Web-interface: http://cgit.jenslody.de/
* Git URL: git://jenslody.de/git/codeblocks
* the above Web-interface link contains many other mirrors such as wxWidgets trunk, git mirror, and git mirror of codeblocks.github

'''Mirror by Obf''' (Read-only; refreshed manually. As 2022-09-12, it looks dead.)
* Web-interface: https://github.com/obfuscated/codeblocks_sf
* Git URL: see the above page.
}}

'''Articles for Code::Blocks developers.'''

* '''Documentation'''
:[https://www.codeblocks.org/manual.shtml User's manual] in various formats and languages.
:Browse SDK documentation at http://alpha0010.github.io/cb-docs/ as html.

* Compile the complete Code::Blocks from sources on '''[[Installing Code::Blocks from source on Windows|Windows]]''' and '''[[Installing Code::Blocks from source on Linux|Linux]]'''

* '''[[Compile Code::Blocks plugins based on a nightly]]''' without the need to compile wxWidgets or the Code::Blocks core.

:Code::Blocks uses Launchpad to coordinate translation efforts.
* '''[http://launchpad.net/products/codeblocks/ Old Translation page]'''
* '''[http://launchpad.net/products/codeblocks-gd/ New Translation page]'''
:See also [https://forums.codeblocks.org/index.php/topic,1022.msg159075.html#msg159075 Code::Blocks' translation]

* '''[[Coding style]]'''
:The source code formatting style used in the Code::Blocks' source.

* '''[[Creating a custom lexer for Code::Blocks editor]]'''
:How to add support for new syntax lighting schemes.

* '''[[Creating a patch to submit (Patch Tracker)]]'''
:Creating a diff file and then submitting it to the patch tracker.

* '''[[Unicode Standards]]'''
:Information about unicode standards and how unicode is handled in Code::Blocks' source code.

* '''[[Various development tips]]'''
:List of various development tips for Code::Blocks.

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

* '''[[A short overview about Code::Blocks architecture]]'''
:Information about the architecture of Code::Blocks.

* '''[[Code::Blocks SDK events]]'''
:Information about the Code::Blocks SDK events and how to work with them.

* '''[[File formats description]]'''
:Description of the format of each file Code::Blocks produces.

* '''[[Version control]]'''
:Tips and trick for working with our version control system.

== Plug-In development ==

* [[Plugin structure of C::B]]
* [[Creating a simple "Hello World" plugin]]
* [[Creating a Plug-in which modifies CB's Menus]]
* [[Creating a plugin that actually does something]]
* [[Linking the plugin to a Nightly Build]]
* [[Managing Plug-in Resources]]

* [[Research on doing a Plug-in for embedded help in CB]]

* [[wxSmith extensions]]
* [[Code::Completion Rewrite]] and [[Code Completion plugin]] and [[Code Completion Design]]

== Scripting ==

Using scripting to extend Code::Blocks' functionality

* [[Wizard scripts|Creating a new project wizard]]

== Developing C::B with Git ==
For devs who want to use Git to develop C::B, here are some steps to follow, especially you need to correctly set the SVN and GIT properties so that you can make your local git commits back to the official SVN repo. See [https://forums.codeblocks.org/index.php/topic,16096.msg128152.html#msg128152 Re: Read-only Git, SVN Repo for Code::Blocks], also stahta01 has a nice instruction about how to use git, see [https://forums.codeblocks.org/index.php/topic,19533.msg133422.html#msg133422 Development How to use a Code::Blocks Git Repo].

If you want to create a SVN style patch from git, see: [https://forums.codeblocks.org/index.php/topic,19391.msg132530.html#msg132530 This forum post].

It's possible to build Code::Blocks through GitHub Actions, see [https://wiki.codeblocks.org/index.php/Building_Code::Blocks_through_GitHub_Actions Building Code::Blocks through GitHub Actions].

== Debugging C::B ==

* When C::B crashes, it will generate a call-stack file "codeblocks.RPT", at the crash point (see [[FAQ-Compiling_(general)#Q: How do I report a compilation problem on the forums?|this]] for more information). This is a text file that you can open; if your C::B contains the debug information, it will have file and line information about each call. If your C::B is a stripped version, but you have the debug version of C::B, you can try to run the [https://forums.codeblocks.org/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is an address2line UI interface that works under Windows.
* You can debug C::B under C::B (with the debugger plugin), also, you can link C::B to the debug version of wxWidgets library, so you can see whether a bug is located in C::B source code or wxWidgets' source code, see here: [https://forums.codeblocks.org/index.php/topic,17316.msg130972.html#msg130972 patch to build C::B against wx debug library]. You can use the project option plugin to change all the custom variable WX_SUFFIX from "u" to "ud" in the workspace, so that you can build C::B against wx debug library, see discussion here: [https://forums.codeblocks.org/index.php/topic,25959.0.html How to globally set the "custom variables" in the cbp files under a workspace].
* to accelerate the debugging process for many plugins(when GDB load a lot of plugins with debug information, it will be slow), there is a special profile named "debug-plugin", a profile file is just a configure file named "debug-plugin.conf", when you start with this profile, you can exclude other plugins, and only load the plugins you needed, see discussion here: [https://forums.codeblocks.org/index.php/topic,25161.0.html How to exclude the other plugins when debugging]
* if you application or the debugee C::B is built against release version of wxWidgets library, how to debug the wxWidgets symbols, the method is to use the gcc's option "-femit-class-debug-always", see forum discussion here: [https://forums.codeblocks.org/index.php/topic,25731.0.html How to add gcc option "-femit-class-debug-always" to a single cpp file in cbp]
* to catch more debug information on the crash, we can distribute separate debug files, see discussion here: [https://forums.codeblocks.org/index.php/topic,25712.0.html new idea: ship the debug symbols in a separate file when we distribute C::B]

Developer documentation

2025-03-05T20:11:49Z

MichaelAgarkov: Returned my mirror back online.

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
{{Layout_box2|1=
'''Official Code repository Subversion''' 
* Web-interface by ViewVC: http://sourceforge.net/p/codeblocks/code/log/
* Subversion URL: <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki> or <nowiki>http://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

'''Mirror by Carsten Arnholm''' (Read-only; )
* Web-interface: https://github.com/arnholm/codeblocks_sfmirror
* Git URL: see the above page.

'''Mirror by Michael Agarkov''' (Read-only)
* Web-interface: https://michaelagarkov.ru/MichaelAgarkov/codeblocks
* Git URL: see the above page.

'''Mirror by biplab''' (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)
* Subversion URL: <nowiki>svn://cb.biplab.in/codeblocks/trunk</nowiki> 
* Web-interface: http://cb.biplab.in/websvn/
* Git URL: git://cb.biplab.in/codeblocks.git
* Web-interface:http://cb.biplab.in/cgit/

'''Mirror by Jens''' (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)
* Web-interface: http://cgit.jenslody.de/
* Git URL: git://jenslody.de/git/codeblocks
* the above Web-interface link contains many other mirrors such as wxWidgets trunk, git mirror, and git mirror of codeblocks.github

'''Mirror by Obf''' (Read-only; refreshed manually. As 2022-09-12, it looks dead.)
* Web-interface: https://github.com/obfuscated/codeblocks_sf
* Git URL: see the above page.
}}

'''Articles for Code::Blocks developers.'''

* '''Documentation'''
:[https://www.codeblocks.org/manual.shtml User's manual] in various formats and languages.
:Browse SDK documentation at http://alpha0010.github.io/cb-docs/ as html.

* Compile the complete Code::Blocks from sources on '''[[Installing Code::Blocks from source on Windows|Windows]]''' and '''[[Installing Code::Blocks from source on Linux|Linux]]'''

* '''[[Compile Code::Blocks plugins based on a nightly]]''' without the need to compile wxWidgets or the Code::Blocks core.

:Code::Blocks uses Launchpad to coordinate translation efforts.
* '''[http://launchpad.net/products/codeblocks/ Old Translation page]'''
* '''[http://launchpad.net/products/codeblocks-gd/ New Translation page]'''
:See also [https://forums.codeblocks.org/index.php/topic,1022.msg159075.html#msg159075 Code::Blocks' translation]

* '''[[Coding style]]'''
:The source code formatting style used in the Code::Blocks' source.

* '''[[Creating a custom lexer for Code::Blocks editor]]'''
:How to add support for new syntax lighting schemes.

* '''[[Creating a patch to submit (Patch Tracker)]]'''
:Creating a diff file and then submitting it to the patch tracker.

* '''[[Unicode Standards]]'''
:Information about unicode standards and how unicode is handled in Code::Blocks' source code.

* '''[[Various development tips]]'''
:List of various development tips for Code::Blocks.

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

* '''[[A short overview about Code::Blocks architecture]]'''
:Information about the architecture of Code::Blocks.

* '''[[Code::Blocks SDK events]]'''
:Information about the Code::Blocks SDK events and how to work with them.

* '''[[File formats description]]'''
:Description of the format of each file Code::Blocks produces.

* '''[[Version control]]'''
:Tips and trick for working with our version control system.

== Plug-In development ==

* [[Plugin structure of C::B]]
* [[Creating a simple "Hello World" plugin]]
* [[Creating a Plug-in which modifies CB's Menus]]
* [[Creating a plugin that actually does something]]
* [[Linking the plugin to a Nightly Build]]
* [[Managing Plug-in Resources]]

* [[Research on doing a Plug-in for embedded help in CB]]

* [[wxSmith extensions]]
* [[Code::Completion Rewrite]] and [[Code Completion plugin]] and [[Code Completion Design]]

== Scripting ==

Using scripting to extend Code::Blocks' functionality

* [[Wizard scripts|Creating a new project wizard]]

== Developing C::B with Git ==
For devs who want to use Git to develop C::B, here are some steps to follow, especially you need to correctly set the SVN and GIT properties so that you can make your local git commits back to the official SVN repo. See [https://forums.codeblocks.org/index.php/topic,16096.msg128152.html#msg128152 Re: Read-only Git, SVN Repo for Code::Blocks], also stahta01 has a nice instruction about how to use git, see [https://forums.codeblocks.org/index.php/topic,19533.msg133422.html#msg133422 Development How to use a Code::Blocks Git Repo].

If you want to create a SVN style patch from git, see: [https://forums.codeblocks.org/index.php/topic,19391.msg132530.html#msg132530 This forum post].

It's possible to build Code::Blocks through GitHub Actions, see [https://wiki.codeblocks.org/index.php/Building_Code::Blocks_through_GitHub_Actions Building Code::Blocks through GitHub Actions].

== Debugging C::B ==

* When C::B crashes, it will generate a call-stack file "codeblocks.RPT", at the crash point (see [[FAQ-Compiling_(general)#Q: How do I report a compilation problem on the forums?|this]] for more information). This is a text file that you can open; if your C::B contains the debug information, it will have file and line information about each call. If your C::B is a stripped version, but you have the debug version of C::B, you can try to run the [https://forums.codeblocks.org/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is an address2line UI interface that works under Windows.
* You can debug C::B under C::B (with the debugger plugin), also, you can link C::B to the debug version of wxWidgets library, so you can see whether a bug is located in C::B source code or wxWidgets' source code, see here: [https://forums.codeblocks.org/index.php/topic,17316.msg130972.html#msg130972 patch to build C::B against wx debug library]. You can use the project option plugin to change all the custom variable WX_SUFFIX from "u" to "ud" in the workspace, so that you can build C::B against wx debug library, see discussion here: [https://forums.codeblocks.org/index.php/topic,25959.0.html How to globally set the "custom variables" in the cbp files under a workspace].
* to accelerate the debugging process for many plugins(when GDB load a lot of plugins with debug information, it will be slow), there is a special profile named "debug-plugin", a profile file is just a configure file named "debug-plugin.conf", when you start with this profile, you can exclude other plugins, and only load the plugins you needed, see discussion here: [https://forums.codeblocks.org/index.php/topic,25161.0.html How to exclude the other plugins when debugging]
* if you application or the debugee C::B is built against release version of wxWidgets library, how to debug the wxWidgets symbols, the method is to use the gcc's option "-femit-class-debug-always", see forum discussion here: [https://forums.codeblocks.org/index.php/topic,25731.0.html How to add gcc option "-femit-class-debug-always" to a single cpp file in cbp]
* to catch more debug information on the crash, we can distribute separate debug files, see discussion here: [https://forums.codeblocks.org/index.php/topic,25712.0.html new idea: ship the debug symbols in a separate file when we distribute C::B]

Installing a supported compiler

2025-03-04T17:41:38Z

MichaelAgarkov: Added Tiny C compiler.

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

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

== Compiler-neutral setup steps ==

Before using a compiler with Code::Blocks you have to install it. The method for installing the compiler depends on the Operating system you're using, the Compiler you intend to use and so on.
If you installed the compiler on its default installation directory, there is nothing more to configure (if the compiler is natively supported by Code::Blocks). Launch Code::Blocks and you're all set :)

* If that is not the case, launch Code::Blocks. If it is the first time you launch it, the compiler auto-detection will be launched.
* If your compiler was not auto-detected, go to "Settings->Compiler and Debugger->Global Compiler settings->Toolchain executables", select the compiler you installed and press "Auto-detect".
* If you get a message saying that the compiler was auto-detected, congratulations!
* If not, then press the button with the three dots next to the "Auto-detect" button and select the installation directory of your compiler manually.

NOTE: ''The compiler's installation directory is exactly this: the installation directory. Not the "bin" subdirectory nor any other.''

== Windows ==

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

At the time of this writing, Code::Blocks supports the following compilers in Windows:
* [https://osdn.net/projects/mingw/ MinGW GCC C/C++ Free Compiler, including GFortran]
** [http://www.cygwin.org Cygwin GCC C/C++ Free Compiler]
*** [[#HOWTO: Use Cygwin 1.7 with Code::Blocks|HOWTO: Use Cygwin 1.7 with Code::Blocks]]
* [http://www.ti.com/tool/msp430-gcc-opensource MSP430 GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html TriCore GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html PowerPC GCC C/C++]
* [http://altd.embarcadero.com/download/bcppbuilder/freecommandLinetools.exe Borland's C/C++ Free Compiler 5.5]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.digitalmars.com/ Digital Mars Free C/C++ Compiler]
* [https://bellard.org/tcc/ Tiny C Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-windows.html Digital Mars D Compiler for Windows]
These compilers are generally still under active development by their publishers, so a new version of their software could be released that is incompatible with the current version of Code::Blocks.

The following compilers are still supported by Code::Blocks, but are no longer available from their original publishers.
* Microsoft's Visual C++ 2003 - 2010

The following publishers have released newer versions of their compilers which should be tested against the current configuration. In other words, it is not known yet whether these compilers still work with Code::Blocks.

* [http://www.openwatcom.org/download.php OpenWatcom Free C/C++ Compiler]
* [https://software.intel.com/en-us/c-compilers/ipsxe Intel C/C++ Compiler] 

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

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

==== Official MinGW ====
You can install '''MinGW''' yourself, by using an automatic downloader/installer or by downloading and unpacking the required packages by hand from [https://osdn.net/projects/mingw/ OSDN], if needed, here is the [https://sourceforge.net/projects/mingw/ old sourceforge repository].

Packages required (suggested) for MinGW/GCC:

* Compiler:
** gcc-build-3.4.5-20060117-3.tar.gz
** gcc-core-3.4.5-20060117-3.tar.gz
** gcc-g++-3.4.5-20060117-3.tar.gz
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz

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

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

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

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

'''Solution'''

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

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

After this, compilation and linking worked fine.

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

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

See also: [[Installing Cygwin Compiler]]

==== (Unofficial) TDM - "Twilight Dragon Media" ====
These packages are called '''TDM's GCC/mingw32 Builds''' and can be obtained from [https://jmeubank.github.io/tdm-gcc/ here].

Packages required (suggested) for TDM's GCC/mingw32 Builds v4.4.1-tdm-2 SJLJ:
...which can be found here: [http://sourceforge.net/projects/tdm-gcc/files/] under: TDM-GCC 4.4 series -> 4.4.1-tdm-2 SJLJ.
* Compiler:
** gcc-4.4.1-tdm-2-core.zip
** gcc-4.4.1-tdm-2-g++.zip
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326-3.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz
These packages are included in both the Bundled Installer and the On-Demand Installer available via TDMs [https://jmeubank.github.io/tdm-gcc/download/ download page].

=== Embarcadero C++ Compiler BCC32C ===
Formerly Borland's C++ Compiler, this compiler is now published by Embarcadero, with active on-going development; the current version is 10.1 as of this writing. Go to [https://www.embarcadero.com/free-tools/ccompiler their product download page] to download. You will be asked to enter some registration information (registration is free) then the download will begin. You will receive a ZIP archive which contains installation instructions in a text file in the root directory of the archive; it does not have an installer program.

=== Digital Mars C/C++ Free Compiler ===
Go to [http://www.digitalmars.com/download/dmcpp.html DigitalMars]. Accept the license agreement and you'll be redirected to a page containing download links.

In that page, download:
*The '''Digital Mars C/C++ Compiler''' (<tt>dm8**c.zip</tt>)
*The '''Basic Utilities''' (<tt>bup.zip</tt>)
*The '''STLport''' library (<tt>stlport.zip</tt>)

Open <tt>dm\bin\sc.ini</tt> in a text editor, and replace the line
INCLUDE="%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%
with
INCLUDE="%@P%\..\stlport\stlport";"%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%

=== Tiny C Compiler ===
The [https://bellard.org/tcc/ Tiny C compiler] is supported. Go to the [http://download.savannah.gnu.org/releases/tinycc/ download page] and select the version that you want. If you chose the Win32 version, make sure to also get the winapi. Extract the compiler to "C:\tcc" so that the binary is at "C:\tcc\tcc.exe". Code::Blocks should auto-detect the compiler there.

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

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

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

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

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

=== Digital Mars D Compiler for Windows ===
Now Digital Mars D Compiler (DMD) supports 32bit Windows, and in future it will support 64bit Windows.
If you want to build D program in CodeBlocks on 32bit Windows, please following the instructions as bellow.

1). Install DMD(2.0) into your Windows system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Windows http://www.digitalmars.com/d/2.0/dmd-windows.html

The newest DMD2 source you can get here: https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''

2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
2.2). click "Compiler settings -> Other options", add '''-m32''' into the field;
2.3). click "Linker settings", and add "'''D:\Program\DMD2\windows\lib\phobos.lib'''" into the "Link libraries";
2.4). click "Search directories -> Compiler", and add "'''D:\Program\DMD2\src\phobos'''" into the field;
2.5). click "Search directories -> Linker", and add "'''D:\Program\DMD2\windows\lib'''" into the field;
2.6). click "Toolchain executables", add "'''D:\Program\DMD2\windows'''" into the "Compiler's installation directory" filed;
(if you installed DMD2 correctly acc. to Installation setp, just click 'Auto-detect' button.)
2.7). Additional: If you wan to specify the DMC (Digital Mars C/C++ Compiler) you can do like this:
click "Toolchain executables -> Additional Paths", and add "D:\Program\DMC\bin" into the field.

The "D:\Program\DMD2" or "D:\Program\DMC\bin" here should change to your own DMD or DMC path in your system.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

== Linux ==

At the time of this writing, Code::Blocks supports the following compilers in Linux:
* [http://gcc.gnu.org/ GNU GCC C/C++ Free Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-linux.html Digital Mars D Compiler for Linux]

===Digital Mars D Compiler for Linux===
Now Digital Mars D Compiler (DMD) supports 32bit and 64bit Linux, and 'support Linux library' is under construction. If you want to build D program in CodeBlocks on 32bit and 64bit Linux, please following the instructions as bellow.

1). Install DMD(2.0) into your Linux system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Linux http://www.digitalmars.com/d/2.0/dmd-linux.html

The newest DMD2 source you can get here:
https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

A). 32bit Linux & 32bit DMD2.

On 32bit Linux, you should combine 32bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''.

A.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
A.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
A.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
A.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
A.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
A.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
A.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B1). 64bit Linux & '''64bit DMD2'''.

On 64bit Linux, you can combine 64bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B1.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B1.2). click "Compiler settings -> Other options", add '''-m64''' into the field.
B1.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib64/libphobos2.a'''" into the "Link libraries".
B1.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B1.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib64'''" into the field.
B1.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B1.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m64 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B2). 64bit Linux with '''32bit DMD2'''.

On 64bit Linux, you can combine 32bit DMD2 with 64bit together from DMD2 source and install them into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B2.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
B2.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
B2.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B2.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
B2.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B2.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Linux you'll, most probably, already have everything that is needed in order to compile. All major Linux distributions (RedHat, Debian, SuSE, Mandriva, Gentoo, ArchLinux, etc) come with GCC & GDB preinstalled. To make sure you have have gcc installed, go to your terminal and type 'gcc -v'. In case you have GCC installed, you will get GCC's compile options and version number.

==Mac OS X==
The Mac OS X port efforts has began recently, but it should be a matter of time until these compilers will be supported:
* [http://gcc.gnu.org/ GNU GCC]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel Compiler beta (not yet released to public)]
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Mac you'll need to install a ''compatible'' version Xcode Tools from http://developer.apple.com/tools/ (or http://developer.apple.com/downloads). You need the "Command Line Tools".

This will install Apple versions of:

http://www.gnu.org/software/gcc/

http://www.gnu.org/software/gdb/

http://www.gnu.org/software/make/

=== Setting up compiler switches ===

Usually you need to tweak the compiler options to be able to compile C++ applications - that's the stuff Xcode hides from your eyes, but you better should know. You need to point to the GNU compiler's C/C++ include folders, to the GNU linkers libraries folder and a adjust the compiler options to setup the GNU compiler root path. Those path's differ depending on what hardware (processor architecture) and what version of MacOS is used. For an Intel based Mac with MacOS 10.6.2 and Xcode v3.2.2 the following should work:

Compiler search directories ("include" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1
</code>

Linker search directories ("library" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib/gcc/i686-apple-darwin10/4.2.1
</code>

Additional compiler flags:

<code>
-isysroot /Developer/SDKs/MacOSX10.6.sdk -mmacosx-version-min=10.6 -gdwarf-2
</code>

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

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

== Misc. Custom Compilers ==
There are several user contributions for different (non-C/C++) compiler which are listed here:

https://wiki.codeblocks.org/index.php?title=User_documentation#Compilers

Main Page

2025-03-04T17:36:10Z

MichaelAgarkov: Add Tiny C compiler.

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

Wiki Editors: In order to edit pages, you must create an account on the [https://forums.codeblocks.org/ forums] and authenticate there. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

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


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

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

|-

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

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


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

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


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

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

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


|}
</div>

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

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

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

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

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

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

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

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

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/binaries 20.03]
* Nightly builds: [https://forums.codeblocks.org/index.php/board,20.0.html Forum board]
* Source code: [https://www.codeblocks.org/downloads/source 20.03], [https://www.codeblocks.org/downloads/svn current trunk]
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [https://forums.codeblocks.org/ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3ABug_Report+or+_type%3AUndefined bugs] or browse [http://alpha0010.github.io/cb-history/bugs.html old bugs]
* '''Features''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3AFeature_Request+or+_type%3AUndefined features] or browse [http://alpha0010.github.io/cb-history/features.html old features]
* '''Patches''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3APatch+or+_type%3AUndefined patches] or browse [http://alpha0010.github.io/cb-history/patches.html old patches]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [https://www.mingw-w64.org/ MinGW-w64] (Win)
* [https://github.com/jmeubank/tdm-gcc/ TDM GCC] (Win)
* [https://www.msys2.org/ MSYS2] (Win)
* [https://www.cygwin.com/ Cygwin] (Win)
* [https://winlibs.com/ WinLibs GCC] (Win)
* [https://osdn.net/projects/mingw/ MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore and PowerPC GCC] (Win32, Linux)
* [https://developer.apple.com/xcode/ Apple XCode (GCC)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [https://visualstudio.microsoft.com/vs/community/ Microsoft Visual Community Edition] (Win)
* [http://altd.embarcadero.com/download/bcppbuilder/freecommandLinetools.exe Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [https://github.com/open-watcom/open-watcom-v2 OpenWatcom V2] (Win32)
* [https://software.intel.com/en-us/c-compilers Intel C++ compiler] (Win32)
* [https://bellard.org/tcc/ Tiny C compiler] (Win32, Linux)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://dlang.org/ Digital Mars D] (Win32, Linux, Mac OS X)
* [https://gdcproject.org/ GDC D Compiler] (Linux)
* [https://github.com/ldc-developers/ldc/ LLVM D Compiler] (Win32, Linux, Mac OS X)
}}
|}

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

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

User:MichaelAgarkov

2025-01-03T22:55:41Z

MichaelAgarkov: Fix typo

Contact email: [mailto:michaelagarkov@internet.ru michaelagarkov@internet.ru]

Codeberg: https://codeberg.org/MichaelAgarkov

User:MichaelAgarkov

2025-01-03T22:55:21Z

MichaelAgarkov: Change my email to the new one and replace GitHub link to Codeberg.

Contact email: [mailto:michaelagarkov@internet.ru michaelagarkov@internet.ru]

CodebergL https://codeberg.org/MichaelAgarkov

FAQ-General

2024-12-27T18:22:58Z

MichaelAgarkov:

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: What is Code::Blocks? ====

'''A:''' Code::Blocks is an Integrated Development Environment, aka [[wikipedia:Integrated development environment|IDE]]. Thus, a framework for working with source code and using compilers and linkers (in the case of Code::Blocks, these can be several).

==== Q: What Code::Blocks is not? ====

'''A:''' Code::Blocks is not a [[wikipedia:Compiler|compiler]], nor a [[wikipedia:Linker (computing)|linker]]. Release packages of Code::Blocks may include a compiler suite (MinGW/GCC), if not provided by the target platform already. However, this is provided "as-is" and not developed/maintained by the Code::Blocks development team.

==== Q: What license is Code::Blocks released under? ====

'''A:''' GNU General Public License 3 ([http://www.gnu.org/licenses/gpl-3.0.html GPL]) with an exception for third party plugins that can be of any license (including closed source) as long as they use only the SDK sources of Code::Blocks.

As an example: If you use the Code::Blocks SDK to develop a plugin, this could be even commercial. When you start using/modifying source code of other parts (i.e. the Code::Blocks core or other GPL3 plugins) the modifications or relevant (affected) parts must be provided as source code, too. However, usually (probably 99.9% of the cases) you'll only need to use the SDK.

==== Q: When will the next stable version of Code::Blocks be released? ====

'''A:''' When it will be ready.

==== Q: Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ====

'''A:''' Yes, this is implemented, but you'll need the [[help plugin]]. So if you are using the installer, make sure you enable this plugin.

----

Return to '''[[FAQ]]'''.

User:MichaelAgarkov

2024-12-21T10:58:29Z

MichaelAgarkov: Reverted to old version

Contact email: [mailto:michaelagarkov@outlook.com michaelagarkov@outlook.com]

GitHub: https://github.com/MichaelAgarkov

CodeBlocks:Privacy policy

2024-12-11T11:47:02Z

MichaelAgarkov: Created blank page

Code::Blocks Plugins

2024-12-10T19:19:35Z

MichaelAgarkov: Fixed old text to relevant information

[[Category: User Documentation]]
== General ==

Code::Blocks' features can be extend by using '''plugins''', most of them listed on this page. There are generally three types of plugins:
# Core plugins - developed and maintained by the core C::B team.
# Contrib plugins - developed and maintained by the community and proven to be very valuable. So they are integrated into the C::B SVN.
# 3rd party plugins - developed and maintained by the community but not (yet?) in the C::B repository. Theses plugins often have their own repository or are being posted (including the source code) in the forums.

'''If you are looking for plugins:'''
# Look in the official release. Notice that the installer / package manager might require you to enable some of the plugins specifically. So READ carefully.
# Search the forums for announcements, especially the forums at [/index.php/board,14.0.html].
# There might be information on the WiKi concerning other plugins on this page and '''[[Announcement_for_plugins/patches|here]]'''.

For Windows users, the default behavior of the current installer (20.03) installs the contrib plugins.

'''If you are developing plugins:'''

* Please read [https://wiki.codeblocks.org/index.php/Managing_Plug-in_Resources this page] for creating and producing a plugin.
* You will need to store the source code for the plugin for other developers to have access to it. You can do this on SourceForge or Github or your favorite source code repository web site.
* Setup your own webpage on a file sharing platform that can be used for documenting and distribution of the plugin. This will allow users to download the plugin to install on their Code::Blocks installation.

Once you have a working and production ready plugin for other developers to use then you can do the following:
* Read [https://wiki.codeblocks.org/index.php/Announcement_for_plugins/patches this page] for information on how to announce you have a plugin on the Code::Blocks forum.
* In your announcement in the [https://forums.codeblocks.org/index.php/board,14.0.html forum] please also ask for your plugin to be added to the Code::Blocks wiki [https://wiki.codeblocks.org/index.php?title=Code::Blocks_Plugins plugin page] with the details you would like to see on the page.

== Core Plugins ==

The core plugins are installed by default and offer the basic functions of Code::Blocks. The core plugins are maintained / developed by the official development team.

'''[[Abbreviations plugin|Abbreviations]]'''
:Code::Blocks AutoComplete plugin.

'''[[Autosave plugin|Autosave]]'''

:Saves project files between intervals.

'''[[Class Wizard plugin|Class Wizard]]'''

:Provides wizard for creating new classes.

'''[[Code Completion plugin|Code Completion]]'''

:Provides code completion functionality and class browser.

'''[[CB Clangd Client|CB Clangd Client]]'''

:Provides code completion functionality and class browser by Clangd through LSP.

'''[[Compiler plugin|Compiler]]'''

:Provides support for various compilers in one interface.

'''[[Debugger plugin|Debugger]]'''

:Provides support for various debuggers in one interface.

'''[[File Extension Handler plugin|File Extensions Handler]]'''

:Adds extra file extension handlers.

'''[[Header Guard plugin|Header Guard]]''' ''(Disabled by default.)''

:Create header guards (if needed) on file save.

'''[[LogHacker plugin|LogHacker]]''' ''(Disabled by default.)''

:Manipulate loggers.

'''[[ModPoller plugin|ModPoller]]''' ''(Disabled by default.)''

:Frequently check for external modification.

'''[[Open Files List plugin|Open Files List]]'''

:Manages a list of all opened files (editors).

'''[[Projects Importer plugin|Projects Importer]]'''

:Imports projects from other IDE's, e.g. MS Visual Studio and DevC++.

'''[[Scripted Wizard plugin|Scripted Wizard]]'''

:Provides scripted wizard functionality.

'''[[Source Code Formatter plugin|Source Code Formatter]]''' (AStyle)

:Formats source code files with specific style.

'''[[Tidycmt plugin|Tidycmt]]''' ''(Disabled by default.)''

:Formats comments on file save.

'''[[To-Do List plugin|To-Do List]]'''

:Adds to-do items to source code.

'''[[WinXP Look'n'Feel plugin|WinXP Look'n'Feel]]'''

:Creates manifest file which enables the version 6.0 of the Common Controls on Windows XP.

== Contrib Plugins ==

The user-''contrib''uted plugins are not installed by default and offer extended functionality for Code::Blocks. The contrib plugins are maintained / developed by third-party developers.

'''[[Aligner plugin|Aligner]]'''

:Code alignment.

'''[[AutoVersioning plugin|Auto Versioning]]'''

:Helps you keep track of your project version and status.

'''[[Browse Tracker plugin|Browse Tracker]]'''

:Browse to previous source positions.

'''[[C::B Games plugin|C::B Games]]'''

:Games in a integrated development environment? You bet.

'''[[CCCC plugin|CCCC]]'''

:Integrates CCCC tool for measurement of source code metrics (http://sourceforge.net/projects/cccc/) into Code::Blocks.

'''[[Code Profiler plugin|Code Profiler]]'''

:Provides graphical interface to GNU GProf profiler.

'''[[Code Snippets plugin|Code Snippets]]'''

:Manages small pieces of code (i.e. snippets).

'''[[Code Statistics plugin|Code Statistics]]'''

:Shows various statistics from source code files.

'''[[Copy Strings to Clipboard plugin|Copy Strings to Clipboard]]'''

:Copies literal strings from the current editor to clipboard.

'''[[CppCheck plugin|CppCheck]]'''

:Integrates the static code analyzer Cppcheck into Code::Blocks.

'''[[Cscope plugin|Cscope]]'''

:Integrates Cscope (http://cscope.sourceforge.net/) into Code::Blocks.

'''[[DevPak Installer plugin|DevPak Installer]]'''

:Installs and updates DevC++ DevPaks.

'''[[DoxyBlocks plugin|DoxyBlocks]]'''

:This plugin provides doxygen integration for Code::Blocks.

'''[[DragScroll plugin|DragScroll]]'''

:Enables dragging and scrolling with mouse.

'''[[EditorConfig plugin|EditorConfig]]'''

:This plugin implements the http://EditorConfig.org/ file format.

'''[[Editor Tweaks plugin|Editor Tweaks]]'''

:This plugin provides some additional tweaks for Code::Blocks editor.

'''[[Environment Variables plugin|Environment Variables]]'''

:Sets environment variables within the focus of Code::Blocks.

'''[[File Manager plugin|File Manager]]'''

:This plugin provides a simple file manager as a tab in the Code::Blocks management pane.

'''[[Header Fixup plugin|Header Fixup]]'''

:Adds missing includes/forward declarations to C++ source files.

'''[[Help plugin|Help]]'''

:Integrates third-party help files to the interface.

'''[[HexEditor plugin|HexEditor]]'''

:Opens files in a Code::Blocks integrated HexEditor.

'''[[Incremental Search plugin|Incremental Search]]'''

:Searches and highlights a marked text incrementally within the open editor.

'''[[Keyboard Shortcuts plugin|Keyboard Shortcuts]]'''

:Manages menu shortcuts.

'''[[Koders plugin|Koders]]'''

:Queries the Koders webpage for keywords.

'''[[Library finder plugin|Library finder]]'''

:Tool for automatically searching for installed libraries, and adding them to the project.

'''[[NassiShneiderman plugin|NassiShneiderman]]'''

:Allows the creation of Nassi Shneiderman diagrams within Code::Blocks.

'''[[RegEx Testbed plugin|RegEx Testbed]]'''

:Regular expressions testbed.

'''[[ReopenEditor plugin|ReopenEditor]]'''

:Reopen a closed editor via hotkey, menu-item, or from a list.

'''[[Rndgen plugin|Rndgen]]'''

:Generates random values (numbers or strings) when saving a file.

'''[[SmartIndent plugin|SmartIndent]]'''

:A suite of plugins that supply smart indenting for various languages.

'''[[Source Exporter plugin|Source Exporter]]'''

:Exports source code files to other formats such as HTML and PDF.

'''[[SpellChecker plugin|SpellChecker]]'''

:A plugin to check the spelling of strings and comments.

'''[[Symbol Table plugin|Symbol Table]]'''

:A simple graphical interface to the GNU symbol table displayer (nm).

'''[[ThreadSearch plugin|ThreadSearch]]'''

:Multi-threaded 'Search in files' with preview window.

'''[[Tools+ plugin|Tools+]]'''

:Creation and management of custom tools.

'''[[Valgrind plugin|Valgrind]]'''

:Valgrind analysis tools integration. (Valgrind does not run on Windows)

'''[[wxSmith plugin|wxSmith]]'''

:RAD tool for creating wxWidgets dialogs.

== 3rd Party Plugins ==

3rd party plugins - developed and maintained by the community but not (yet?) in the C::B repository. The contrib plugins are maintained / developed by third-party developers.

'''[[DisplayEvents plugin|DisplayEvents]]'''

:Display events that are registered with <tt>RegisterEventSink</tt>, in the Code::Blocks Debug log.

'''[[Fortran Project plugin|Fortran Project]]'''

:This plugin provides symbol browser and code-completion for Fortran files.

'''[[IPDefend Toolkit plugin|IPDefend Toolkit]]'''

:This plugin enables creation of a licensed application in an easy way. Available at [http://www.comsytec.com/ipdefend.php]

'''[[KeyMacs plugin|KeyMacs]]'''

:KeyMacs (or Keyboard Macros) plugin enables Recording, Playback, and editing of keystroke macros.

'''[[OccurrenceHighlighter plugin|OccurrenceHighlighter]]'''

:This plugin highlights all occurrences of keywords on a list.

'''[[Python plugins|Python]]'''

:A set of plugins that provide a user interface for debugging python programs, completion hints for python code, and a python interpreter in a dockable window.

'''[[Rss::Blocks plugin|Rss::Blocks]]'''

:This plugin is an rss feeds reader. Available at [http://sourceforge.net/projects/rssblocks/ sourceforge/rssblocks]

'''[[TRACE32 Debugger plugin|TRACE32 Debugger]]'''

:Extends the Debugger plugin of Code::Blocks to work with the TRACE32 Debuggers. TRACE32 documentation "int_codeblock.pdf" and debuggert32.cbplugin are located on the enclosed SW CD on purchase of TRACE32

'''[[EPS Debugger for STM32 plugin|EPS Debugger for STM32]]'''

:Developing embedded applications for STM32 with ST Link 2. Available at [http://www.comsytec.eu/epsdebugger.php]

'''[[Vim emulator plugin|Vim Plugin]]'''

:Emulate the Vim's shortkeys in Code::Blocks editor. Available at [https://github.com/zmj64351508/cbvike cbvike on Github]

If you have questions -> ask in the [/index.php/board,14.0.html forums].

'''[[OpenFilesListPlus Plugin]]'''

:Enhanced version of the OpenFilesList plugin. Available at [https://github.com/earlgrey-bis/cb-OpenFilesListPlus on Github]

'''[[SourceTrail Plugin]]'''

:Interface to [https://www.sourcetrail.com/ on SourceTrail]. Available at [https://github.com/martim01/sourcetrail on Github]

If you have questions -> ask in the [/index.php/topic,23588.0.html forums].

'''[[cbSystemView]]'''

:A plugin to use SVD files for embedded development. Available at [https://github.com/bluehazzard/cbSystemView on Github]

'''[[cbMemoryView]]'''

:A plugin to view memory locations with multiple tabs. Available at [https://github.com/bluehazzard/cbMemoryView on Github]

'''[[cbBuildTools ]]'''

:A little plugin that displays the targets in a tree, for easy building. Available at [https://github.com/bluehazzard/cbBuildTools on Github]

==See also==
* [[Announcement for plugins/patches|Announcement for plugins/patches]] These are not stable plugins in many cases

User:MichaelAgarkov

2024-12-10T18:35:53Z

MichaelAgarkov: Added more links

Михаил Агарков

Email:

* Email (clearnet): [mailto:michaelagarkov@outlook.com michaelagarkov@outlook.com]
* Email (I2P): [mailto:michaelagarkov@mail.i2p michaelagarkov@mail.i2p] (Requires I2P)

Net:

* Website: https://michaelagarkov.neocities.org
* GitHub: https://github.com/MichaelAgarkov
* Codeberg: https://codeberg.org/MichaelAgarkov
* GitLab: https://gitlab.com/MichaelAgarkov
* Gitea: https://gitea.com/MichaelAgarkov
* I2P Git: http://git.community.i2p/MichaelAgarkov (Requires I2P)

Public keys:

* [https://michaelagarkov.ru/MichaelAgarkov.gpg Public GPG keys]
* [https://michaelagarkov.ru/MichaelAgarkov.keys Public SSH key]

Talk:CB Clangd Client

2024-12-09T16:37:14Z

MichaelAgarkov: Created blank page

Developer documentation

2024-11-21T16:10:53Z

MichaelAgarkov: Removed my mirror since I'm no longer going to maintain it.

Developer documentation

2024-11-20T20:02:03Z

MichaelAgarkov: Added my mirror of Code::Blocks to the list

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
{{Layout_box2|1=
'''Official Code repository Subversion''' 
* Web-interface by ViewVC: http://sourceforge.net/p/codeblocks/code/log/
* Subversion URL: <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki> or <nowiki>http://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>

'''Mirror by Carsten Arnholm''' (Read-only; )
* Web-interface: https://github.com/arnholm/codeblocks_sfmirror
* Git URL: see the above page.

'''Mirror by Michael Agarkov''' (Read-only)
* Web-interface: https://michaelagarkov.ru/MichaelAgarkov/codeblocks
* Git URL: see the above page.

'''Mirror by biplab''' (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)
* Subversion URL: <nowiki>svn://cb.biplab.in/codeblocks/trunk</nowiki> 
* Web-interface: http://cb.biplab.in/websvn/
* Git URL: git://cb.biplab.in/codeblocks.git
* Web-interface:http://cb.biplab.in/cgit/

'''Mirror by Jens''' (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)
* Web-interface: http://cgit.jenslody.de/
* Git URL: git://jenslody.de/git/codeblocks
* the above Web-interface link contains many other mirrors such as wxWidgets trunk, git mirror, and git mirror of codeblocks.github

'''Mirror by Obf''' (Read-only; refreshed manually. As 2022-09-12, it looks dead.)
* Web-interface: https://github.com/obfuscated/codeblocks_sf
* Git URL: see the above page.
}}

'''Articles for Code::Blocks developers.'''

* '''Documentation'''
:[https://www.codeblocks.org/manual.shtml User's manual] in various formats and languages.
:Browse SDK documentation at http://alpha0010.github.io/cb-docs/ as html.

* Compile the complete Code::Blocks from sources on '''[[Installing Code::Blocks from source on Windows|Windows]]''' and '''[[Installing Code::Blocks from source on Linux|Linux]]'''

* '''[[Compile Code::Blocks plugins based on a nightly]]''' without the need to compile wxWidgets or the Code::Blocks core.

:Code::Blocks uses Launchpad to coordinate translation efforts.
* '''[http://launchpad.net/products/codeblocks/ Old Translation page]'''
* '''[http://launchpad.net/products/codeblocks-gd/ New Translation page]'''
:See also [https://forums.codeblocks.org/index.php/topic,1022.msg159075.html#msg159075 Code::Blocks' translation]

* '''[[Coding style]]'''
:The source code formatting style used in the Code::Blocks' source.

* '''[[Creating a custom lexer for Code::Blocks editor]]'''
:How to add support for new syntax lighting schemes.

* '''[[Creating a patch to submit (Patch Tracker)]]'''
:Creating a diff file and then submitting it to the patch tracker.

* '''[[Unicode Standards]]'''
:Information about unicode standards and how unicode is handled in Code::Blocks' source code.

* '''[[Various development tips]]'''
:List of various development tips for Code::Blocks.

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

* '''[[A short overview about Code::Blocks architecture]]'''
:Information about the architecture of Code::Blocks.

* '''[[Code::Blocks SDK events]]'''
:Information about the Code::Blocks SDK events and how to work with them.

* '''[[File formats description]]'''
:Description of the format of each file Code::Blocks produces.

* '''[[Version control]]'''
:Tips and trick for working with our version control system.

== Plug-In development ==

* [[Plugin structure of C::B]]
* [[Creating a simple "Hello World" plugin]]
* [[Creating a Plug-in which modifies CB's Menus]]
* [[Creating a plugin that actually does something]]
* [[Linking the plugin to a Nightly Build]]
* [[Managing Plug-in Resources]]

* [[Research on doing a Plug-in for embedded help in CB]]

* [[wxSmith extensions]]
* [[Code::Completion Rewrite]] and [[Code Completion plugin]] and [[Code Completion Design]]

== Scripting ==

Using scripting to extend Code::Blocks' functionality

* [[Wizard scripts|Creating a new project wizard]]

== Developing C::B with Git ==
For devs who want to use Git to develop C::B, here are some steps to follow, especially you need to correctly set the SVN and GIT properties so that you can make your local git commits back to the official SVN repo. See [https://forums.codeblocks.org/index.php/topic,16096.msg128152.html#msg128152 Re: Read-only Git, SVN Repo for Code::Blocks], also stahta01 has a nice instruction about how to use git, see [https://forums.codeblocks.org/index.php/topic,19533.msg133422.html#msg133422 Development How to use a Code::Blocks Git Repo].

If you want to create a SVN style patch from git, see: [https://forums.codeblocks.org/index.php/topic,19391.msg132530.html#msg132530 This forum post].

It's possible to build Code::Blocks through GitHub Actions, see [https://wiki.codeblocks.org/index.php/Building_Code::Blocks_through_GitHub_Actions Building Code::Blocks through GitHub Actions].

== Debugging C::B ==

* When C::B crashes, it will generate a call-stack file "codeblocks.RPT", at the crash point (see [[FAQ-Compiling_(general)#Q: How do I report a compilation problem on the forums?|this]] for more information). This is a text file that you can open; if your C::B contains the debug information, it will have file and line information about each call. If your C::B is a stripped version, but you have the debug version of C::B, you can try to run the [https://forums.codeblocks.org/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is an address2line UI interface that works under Windows.
* You can debug C::B under C::B (with the debugger plugin), also, you can link C::B to the debug version of wxWidgets library, so you can see whether a bug is located in C::B source code or wxWidgets' source code, see here: [https://forums.codeblocks.org/index.php/topic,17316.msg130972.html#msg130972 patch to build C::B against wx debug library]

FAQ-General

2024-11-19T15:26:11Z

MichaelAgarkov: Added mention of the 24.12 branch.

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: What is Code::Blocks? ====

'''A:''' Code::Blocks is an Integrated Development Environment, aka [[wikipedia:Integrated development environment|IDE]]. Thus, a framework for working with source code and using compilers and linkers (in the case of Code::Blocks, these can be several).

==== Q: What Code::Blocks is not? ====

'''A:''' Code::Blocks is not a [[wikipedia:Compiler|compiler]], nor a [[wikipedia:Linker (computing)|linker]]. Release packages of Code::Blocks may include a compiler suite (MinGW/GCC), if not provided by the target platform already. However, this is provided "as-is" and not developed/maintained by the Code::Blocks development team.

==== Q: What license is Code::Blocks released under? ====

'''A:''' GNU General Public License 3 ([http://www.gnu.org/licenses/gpl-3.0.html GPL]) with an exception for third party plugins that can be of any license (including closed source) as long as they use only the SDK sources of Code::Blocks.

As an example: If you use the Code::Blocks SDK to develop a plugin, this could be even commercial. When you start using/modifying source code of other parts (i.e. the Code::Blocks core or other GPL3 plugins) the modifications or relevant (affected) parts must be provided as source code, too. However, usually (probably 99.9% of the cases) you'll only need to use the SDK.

==== Q: When will the next stable version of Code::Blocks be released? ====

'''A:''' The [https://sourceforge.net/p/codeblocks/code/HEAD/tree/branches/release-24.12/ 24.12] branch was made in the SVN repo (Meaning December 2024).

==== Q: Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ====

'''A:''' Yes, this is implemented, but you'll need the [[help plugin]]. So if you are using the installer, make sure you enable this plugin.

----

Return to '''[[FAQ]]'''.

Developer documentation

2024-11-06T16:02:29Z

MichaelAgarkov: Added link to "Building Code::Blocks through GitHub Actions" article

Talk:Building Code::Blocks through GitHub Actions

2024-11-06T15:26:28Z

MichaelAgarkov: Created blank page

Building Code::Blocks through GitHub Actions

2024-11-06T15:13:00Z

MichaelAgarkov: Create page for building Code::Blocks through GitHub Actions

Progress is currently being made on creating a build script for compiling Code::Blocks in GitHub Actions with MSYS2: [https://github.com/zxunge/x86-codeblocks-builds zxunge/x86-codeblocks-builds]

Also see: [https://github.com/zxunge/winstyle-codeblocks-bins zxunge/winstyle-codeblocks-bins]
----An attempt to rewrite the build script for Woodpecker CI is being made here: [https://codeberg.org/MichaelAgarkov/x86-codeblocks-builds MichaelAgarkov/x86-codeblocks-builds]

Feature List

2024-10-12T20:57:07Z

MichaelAgarkov: Listed Clangd LSP support as a feature

[[Category: User Documentation]]
==Highlights==
* '''Open Source!''' GPLv3, no hidden costs.
* '''Cross-platform.''' Runs on Linux, Mac, Windows (uses wxWidgets).
* Written in C++. No interpreted languages or proprietary libs needed.
* Extensible through [[Code::Blocks Plugins|plugins]]

==Compiler==
* '''Multiple compiler support:'''
** [[Installing a supported compiler#Downloading the GNU GCC compiler .26 GDB debugger|GNU GCC]] ([[Fortran support in Code::Blocks|incl. GFortran]]) (Linux)
** [[Installing a supported compiler#MinGW.2FGCC|MinGW GCC]] ([[Fortran support in Code::Blocks|incl. GFortran]]) (Win32)
** MSP430 GCC (Win32)
** TriCore GCC (Win32, Linux)
** PowerPC GCC (Win32, Linux)
** [[Installing a supported compiler#Downloading the GNU GCC compiler .26 GDB debugger 2|Apple GCC (Xcode)]] (Mac OS X)
** [[Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE|Microsoft Visual C++ Toolkit 2003]] (Win32)
** [[Installing a supported compiler#Microsoft Visual C.2B.2B|Microsoft Visual C++ 2005]] (Win32)
** [[Installing a supported compiler#Borland C.2B.2B Compiler 5.5|Borland's C++ Compiler 5.5]] (Win32)
** [[Installing a supported compiler#Digital Mars C.2FC.2B.2B Free Compiler|DigitalMars C/C++]] (Win32)
** [[Using Code::Blocks with Open Watcom|Open Watcom]] (Win32)
** [[Installing a supported compiler#Intel C.2B.2B Compiler|Intel C++ compiler]] (Win32)
** [[Using the Code::Blocks IDE with SDCC on PIC MCUs|Small Device C Compiler (SDCC)]]
** [[Installing Cygwin Compiler|Cygwin]] (Win32)
** [[Installing Objective-C Compiler|GNU GCC Objective-C]]
** [[Installing a supported compiler#Digital Mars D Compiler for Windows|Digital Mars D]]
** GDC D Compiler
** LLVM D Compiler
* '''Very fast''' custom build system (no makefiles needed)
* Support for '''parallel builds''' (utilizing your CPU's extra cores)
* [[Creating a new project#Adding a new build target|Multi-target]] projects
* Workspaces to combine multiple projects
* [[The build process of Code::Blocks#Using project dependencies|Inter-project dependencies]] inside workspace
* [[Integrating Microsoft Visual C 6 with Code::Blocks IDE#Working with "legacy" MSVC6 workspaces/projects|Imports MSVC projects and workspaces]] (NOTE: assembly code not supported yet)
* Imports Dev-C++ projects
* [[CB Clangd Client|Clangd LSP support]]

==Debugger==
* Interfaces [[Debugging with Code::Blocks|GNU GDB]]
* Also supports MS CDB (not fully featured)
* '''Full breakpoints support:'''
** Code breakpoints
** Data breakpoints (read, write and read/write)
** Breakpoint conditions (break only when an expression is true)
** Breakpoint ignore counts (break only after certain number of hits)
* Display local function symbols and arguments
* User-defined watches (support for watching user-defined types through scripting)
* Call stack
* Disassembly
* Custom memory dump
* Switch between threads
* View CPU registers

==Interface==
* [[Languages supported by Code::Blocks lexers|Syntax highlighting]], customizable and [[Creating a custom lexer for Code::Blocks editor|extensible]]
* Code folding for C++, Fortran, Python, XML, and multiple other languages
* Tabbed interface
* [[Code Completion plugin|Code completion]]
* Class Browser
* Smart indent
* [[Keyboard Shortcuts#Editor|One-key swap]] between .h and .c/.cpp files
* Custom [[Keyboard Shortcuts plugin|keyboard shortcuts]]
* Open files list for quick switching between files (optional)
* [[Tools+ reference|External customizable "Tools"]]
* [[To-Do List plugin|To-do list]] management with different users

==Plugins==
* Fully customizable through [[Code::Blocks Plugins|plugins]]
* Automatically [[Source Code Formatter plugin|format source code]] to the desired style
* [[SpellChecker plugin|Spell-check]] on strings and comments ([[Nightly Cookbook|svn]] only)
* [[WxSmith tutorials|Rapid application development tool]] for [[Using wxWidgets|wxWidgets]] based GUIs
* [[NassiShneiderman plugin|Nassi–Shneiderman]] diagramming
* Integrated [[HexEditor plugin|hex editor]]
* And much more...

Main Page

2024-10-12T18:33:34Z

MichaelAgarkov: Fix link to Borland's C++ Compiler 5.5

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

Wiki Editors: In order to edit pages, you must create an account on the [https://forums.codeblocks.org/ forums] and authenticate there. Read the [[Help:Contents|Help]] for editing guidelines. Look in the [[CodeBlocks:Community_Portal|community portal]] for things to do.

 
}}

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


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

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

|-

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

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


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

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


|-

|align="center"|
'''[[Creating a new project|...create a new project?]]''' 

[[Creating a new project#Changing file composition|Add files]] ·
[[Creating a new project#Modifying build options|Build options]] ·
[[Creating a new project#Virtual Targets|Virtual Targets]] ·
[[Creating a new project|more...]]


|align="center"|
'''[[Debugging_with_Code::Blocks|...debug my program?]]'''

|-

|align="center"|
'''[[FAQ-Settings#Q: How do I make Code::Blocks portable?|...make Code::Blocks portable?]]'''

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

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


|}
</div>

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

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

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

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

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

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

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

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

{{Layout_box4|1=
=== Download Code::Blocks ===
* Latest official release: [https://www.codeblocks.org/downloads/binaries 20.03]
* Nightly builds: [https://forums.codeblocks.org/index.php/board,20.0.html Forum board]
* Source code: [https://www.codeblocks.org/downloads/source 20.03], [https://www.codeblocks.org/downloads/svn current trunk]
}}

{{Layout_box2|1=
=== Other resources ===
* [https://www.codeblocks.org Main website]
* [https://forums.codeblocks.org/ Community forums]
* [irc://irc.freenode.net/codeblocks IRC channel] and [http://webchat.freenode.net/?channels=codeblocks IRC channel web access]
}}

{{Layout_box2|1=
=== Development ===
[[Image:Chk.png]][[Roadmap]]
* [[Developer documentation]]
* [http://sourceforge.net/projects/codeblocks/ Project page at Sourceforge]
* '''Bugs''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3ABug_Report+or+_type%3AUndefined bugs] or browse [http://alpha0010.github.io/cb-history/bugs.html old bugs]
* '''Features''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3AFeature_Request+or+_type%3AUndefined features] or browse [http://alpha0010.github.io/cb-history/features.html old features]
* '''Patches''': browse or submit [http://sourceforge.net/p/codeblocks/tickets/search/?q=_type%3APatch+or+_type%3AUndefined patches] or browse [http://alpha0010.github.io/cb-history/patches.html old patches]
}}

{{Layout_box3|1=
=== Supported compilers ===
* [http://gcc.gnu.org/ GNU GCC (incl. G77)] (Linux)
* [https://www.mingw-w64.org/ MinGW-w64] (Win)
* [https://github.com/jmeubank/tdm-gcc/ TDM GCC] (Win)
* [https://www.msys2.org/ MSYS2] (Win)
* [https://www.cygwin.com/ Cygwin] (Win)
* [https://winlibs.com/ WinLibs GCC] (Win)
* [https://osdn.net/projects/mingw/ MinGW GCC (incl. G77)] (Win32)
* [http://mspgcc.sourceforge.net MSP430 GCC] (Win32)
* [http://www.hightec-rt.com TriCore and PowerPC GCC] (Win32, Linux)
* [https://developer.apple.com/xcode/ Apple XCode (GCC)] (Mac OS X)

* [http://xona.com/2004/06/29.html Microsoft Visual C++ Toolkit 2003] (Win32)
* [https://visualstudio.microsoft.com/vs/community/ Microsoft Visual Community Edition] (Win)
* [http://altd.embarcadero.com/download/bcppbuilder/freecommandLinetools.exe Borland's C++ Compiler 5.5] (Win32)
* [http://www.digitalmars.com/ DigitalMars C/C++] (Win32)
* [https://github.com/open-watcom/open-watcom-v2 OpenWatcom V2] (Win32)
* [https://software.intel.com/en-us/c-compilers Intel C++ compiler] (Win32)
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]
* [http://dlang.org/ Digital Mars D] (Win32, Linux, Mac OS X)
* [https://gdcproject.org/ GDC D Compiler] (Linux)
* [https://github.com/ldc-developers/ldc/ LLVM D Compiler] (Win32, Linux, Mac OS X)
}}
|}

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

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

Installing a supported compiler

2024-10-12T18:28:57Z

MichaelAgarkov: Fix another link to MinGW

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

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

== Compiler-neutral setup steps ==

Before using a compiler with Code::Blocks you have to install it. The method for installing the compiler depends on the Operating system you're using, the Compiler you intend to use and so on.
If you installed the compiler on its default installation directory, there is nothing more to configure (if the compiler is natively supported by Code::Blocks). Launch Code::Blocks and you're all set :)

* If that is not the case, launch Code::Blocks. If it is the first time you launch it, the compiler auto-detection will be launched.
* If your compiler was not auto-detected, go to "Settings->Compiler and Debugger->Global Compiler settings->Toolchain executables", select the compiler you installed and press "Auto-detect".
* If you get a message saying that the compiler was auto-detected, congratulations!
* If not, then press the button with the three dots next to the "Auto-detect" button and select the installation directory of your compiler manually.

NOTE: ''The compiler's installation directory is exactly this: the installation directory. Not the "bin" subdirectory nor any other.''

== Windows ==

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

At the time of this writing, Code::Blocks supports the following compilers in Windows:
* [https://osdn.net/projects/mingw/ MinGW GCC C/C++ Free Compiler, including GFortran]
** [http://www.cygwin.org Cygwin GCC C/C++ Free Compiler]
*** [[#HOWTO: Use Cygwin 1.7 with Code::Blocks|HOWTO: Use Cygwin 1.7 with Code::Blocks]]
* [http://www.ti.com/tool/msp430-gcc-opensource MSP430 GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html TriCore GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html PowerPC GCC C/C++]
* [http://altd.embarcadero.com/download/bcppbuilder/freecommandLinetools.exe Borland's C/C++ Free Compiler 5.5]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.digitalmars.com/ Digital Mars Free C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-windows.html Digital Mars D Compiler for Windows]
These compilers are generally still under active development by their publishers, so a new version of their software could be released that is incompatible with the current version of Code::Blocks.

The following compilers are still supported by Code::Blocks, but are no longer available from their original publishers.
* Microsoft's Visual C++ 2003 - 2010

The following publishers have released newer versions of their compilers which should be tested against the current configuration. In other words, it is not known yet whether these compilers still work with Code::Blocks.

* [http://www.openwatcom.org/download.php OpenWatcom Free C/C++ Compiler]
* [https://software.intel.com/en-us/c-compilers/ipsxe Intel C/C++ Compiler] 

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

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

==== Official MinGW ====
You can install '''MinGW''' yourself, by using an automatic downloader/installer or by downloading and unpacking the required packages by hand from [https://osdn.net/projects/mingw/ OSDN], if needed, here is the [https://sourceforge.net/projects/mingw/ old sourceforge repository].

Packages required (suggested) for MinGW/GCC:

* Compiler:
** gcc-build-3.4.5-20060117-3.tar.gz
** gcc-core-3.4.5-20060117-3.tar.gz
** gcc-g++-3.4.5-20060117-3.tar.gz
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz

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

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

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

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

'''Solution'''

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

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

After this, compilation and linking worked fine.

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

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

See also: [[Installing Cygwin Compiler]]

==== (Unofficial) TDM - "Twilight Dragon Media" ====
These packages are called '''TDM's GCC/mingw32 Builds''' and can be obtained from [https://jmeubank.github.io/tdm-gcc/ here].

Packages required (suggested) for TDM's GCC/mingw32 Builds v4.4.1-tdm-2 SJLJ:
...which can be found here: [http://sourceforge.net/projects/tdm-gcc/files/] under: TDM-GCC 4.4 series -> 4.4.1-tdm-2 SJLJ.
* Compiler:
** gcc-4.4.1-tdm-2-core.zip
** gcc-4.4.1-tdm-2-g++.zip
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326-3.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz
These packages are included in both the Bundled Installer and the On-Demand Installer available via TDMs [https://jmeubank.github.io/tdm-gcc/download/ download page].

=== Embarcadero C++ Compiler BCC32C ===
Formerly Borland's C++ Compiler, this compiler is now published by Embarcadero, with active on-going development; the current version is 10.1 as of this writing. Go to [https://www.embarcadero.com/free-tools/ccompiler their product download page] to download. You will be asked to enter some registration information (registration is free) then the download will begin. You will receive a ZIP archive which contains installation instructions in a text file in the root directory of the archive; it does not have an installer program.

=== Digital Mars C/C++ Free Compiler ===
Go to [http://www.digitalmars.com/download/dmcpp.html DigitalMars]. Accept the license agreement and you'll be redirected to a page containing download links.

In that page, download:
*The '''Digital Mars C/C++ Compiler''' (<tt>dm8**c.zip</tt>)
*The '''Basic Utilities''' (<tt>bup.zip</tt>)
*The '''STLport''' library (<tt>stlport.zip</tt>)

Open <tt>dm\bin\sc.ini</tt> in a text editor, and replace the line
INCLUDE="%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%
with
INCLUDE="%@P%\..\stlport\stlport";"%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%

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

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

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

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

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

=== Digital Mars D Compiler for Windows ===
Now Digital Mars D Compiler (DMD) supports 32bit Windows, and in future it will support 64bit Windows.
If you want to build D program in CodeBlocks on 32bit Windows, please following the instructions as bellow.

1). Install DMD(2.0) into your Windows system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Windows http://www.digitalmars.com/d/2.0/dmd-windows.html

The newest DMD2 source you can get here: https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''

2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
2.2). click "Compiler settings -> Other options", add '''-m32''' into the field;
2.3). click "Linker settings", and add "'''D:\Program\DMD2\windows\lib\phobos.lib'''" into the "Link libraries";
2.4). click "Search directories -> Compiler", and add "'''D:\Program\DMD2\src\phobos'''" into the field;
2.5). click "Search directories -> Linker", and add "'''D:\Program\DMD2\windows\lib'''" into the field;
2.6). click "Toolchain executables", add "'''D:\Program\DMD2\windows'''" into the "Compiler's installation directory" filed;
(if you installed DMD2 correctly acc. to Installation setp, just click 'Auto-detect' button.)
2.7). Additional: If you wan to specify the DMC (Digital Mars C/C++ Compiler) you can do like this:
click "Toolchain executables -> Additional Paths", and add "D:\Program\DMC\bin" into the field.

The "D:\Program\DMD2" or "D:\Program\DMC\bin" here should change to your own DMD or DMC path in your system.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

== Linux ==

At the time of this writing, Code::Blocks supports the following compilers in Linux:
* [http://gcc.gnu.org/ GNU GCC C/C++ Free Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-linux.html Digital Mars D Compiler for Linux]

===Digital Mars D Compiler for Linux===
Now Digital Mars D Compiler (DMD) supports 32bit and 64bit Linux, and 'support Linux library' is under construction. If you want to build D program in CodeBlocks on 32bit and 64bit Linux, please following the instructions as bellow.

1). Install DMD(2.0) into your Linux system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Linux http://www.digitalmars.com/d/2.0/dmd-linux.html

The newest DMD2 source you can get here:
https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

A). 32bit Linux & 32bit DMD2.

On 32bit Linux, you should combine 32bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''.

A.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
A.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
A.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
A.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
A.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
A.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
A.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B1). 64bit Linux & '''64bit DMD2'''.

On 64bit Linux, you can combine 64bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B1.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B1.2). click "Compiler settings -> Other options", add '''-m64''' into the field.
B1.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib64/libphobos2.a'''" into the "Link libraries".
B1.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B1.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib64'''" into the field.
B1.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B1.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m64 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B2). 64bit Linux with '''32bit DMD2'''.

On 64bit Linux, you can combine 32bit DMD2 with 64bit together from DMD2 source and install them into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B2.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
B2.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
B2.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B2.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
B2.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B2.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Linux you'll, most probably, already have everything that is needed in order to compile. All major Linux distributions (RedHat, Debian, SuSE, Mandriva, Gentoo, ArchLinux, etc) come with GCC & GDB preinstalled. To make sure you have have gcc installed, go to your terminal and type 'gcc -v'. In case you have GCC installed, you will get GCC's compile options and version number.

==Mac OS X==
The Mac OS X port efforts has began recently, but it should be a matter of time until these compilers will be supported:
* [http://gcc.gnu.org/ GNU GCC]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel Compiler beta (not yet released to public)]
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Mac you'll need to install a ''compatible'' version Xcode Tools from http://developer.apple.com/tools/ (or http://developer.apple.com/downloads). You need the "Command Line Tools".

This will install Apple versions of:

http://www.gnu.org/software/gcc/

http://www.gnu.org/software/gdb/

http://www.gnu.org/software/make/

=== Setting up compiler switches ===

Usually you need to tweak the compiler options to be able to compile C++ applications - that's the stuff Xcode hides from your eyes, but you better should know. You need to point to the GNU compiler's C/C++ include folders, to the GNU linkers libraries folder and a adjust the compiler options to setup the GNU compiler root path. Those path's differ depending on what hardware (processor architecture) and what version of MacOS is used. For an Intel based Mac with MacOS 10.6.2 and Xcode v3.2.2 the following should work:

Compiler search directories ("include" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1
</code>

Linker search directories ("library" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib/gcc/i686-apple-darwin10/4.2.1
</code>

Additional compiler flags:

<code>
-isysroot /Developer/SDKs/MacOSX10.6.sdk -mmacosx-version-min=10.6 -gdwarf-2
</code>

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

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

== Misc. Custom Compilers ==
There are several user contributions for different (non-C/C++) compiler which are listed here:

https://wiki.codeblocks.org/index.php?title=User_documentation#Compilers

Installing a supported compiler

2024-10-12T17:53:30Z

MichaelAgarkov: Borland C/C++ Free Compiler 5.5 is actually available on the official website. For some reason the wiki said otherwise, fixed.

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

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

== Compiler-neutral setup steps ==

Before using a compiler with Code::Blocks you have to install it. The method for installing the compiler depends on the Operating system you're using, the Compiler you intend to use and so on.
If you installed the compiler on its default installation directory, there is nothing more to configure (if the compiler is natively supported by Code::Blocks). Launch Code::Blocks and you're all set :)

* If that is not the case, launch Code::Blocks. If it is the first time you launch it, the compiler auto-detection will be launched.
* If your compiler was not auto-detected, go to "Settings->Compiler and Debugger->Global Compiler settings->Toolchain executables", select the compiler you installed and press "Auto-detect".
* If you get a message saying that the compiler was auto-detected, congratulations!
* If not, then press the button with the three dots next to the "Auto-detect" button and select the installation directory of your compiler manually.

NOTE: ''The compiler's installation directory is exactly this: the installation directory. Not the "bin" subdirectory nor any other.''

== Windows ==

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

At the time of this writing, Code::Blocks supports the following compilers in Windows:
* [http://www.mingw.org MinGW GCC C/C++ Free Compiler, including GFortran]
** [http://www.cygwin.org Cygwin GCC C/C++ Free Compiler]
*** [[#HOWTO: Use Cygwin 1.7 with Code::Blocks|HOWTO: Use Cygwin 1.7 with Code::Blocks]]
* [http://www.ti.com/tool/msp430-gcc-opensource MSP430 GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html TriCore GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html PowerPC GCC C/C++]
* [http://altd.embarcadero.com/download/bcppbuilder/freecommandLinetools.exe Borland's C/C++ Free Compiler 5.5]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.digitalmars.com/ Digital Mars Free C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-windows.html Digital Mars D Compiler for Windows]
These compilers are generally still under active development by their publishers, so a new version of their software could be released that is incompatible with the current version of Code::Blocks.

The following compilers are still supported by Code::Blocks, but are no longer available from their original publishers.
* Microsoft's Visual C++ 2003 - 2010

The following publishers have released newer versions of their compilers which should be tested against the current configuration. In other words, it is not known yet whether these compilers still work with Code::Blocks.

* [http://www.openwatcom.org/download.php OpenWatcom Free C/C++ Compiler]
* [https://software.intel.com/en-us/c-compilers/ipsxe Intel C/C++ Compiler] 

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

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

==== Official MinGW ====
You can install '''MinGW''' yourself, by using an automatic downloader/installer or by downloading and unpacking the required packages by hand from [https://osdn.net/projects/mingw/ OSDN], if needed, here is the [https://sourceforge.net/projects/mingw/ old sourceforge repository].

Packages required (suggested) for MinGW/GCC:

* Compiler:
** gcc-build-3.4.5-20060117-3.tar.gz
** gcc-core-3.4.5-20060117-3.tar.gz
** gcc-g++-3.4.5-20060117-3.tar.gz
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz

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

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

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

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

'''Solution'''

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

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

After this, compilation and linking worked fine.

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

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

See also: [[Installing Cygwin Compiler]]

==== (Unofficial) TDM - "Twilight Dragon Media" ====
These packages are called '''TDM's GCC/mingw32 Builds''' and can be obtained from [https://jmeubank.github.io/tdm-gcc/ here].

Packages required (suggested) for TDM's GCC/mingw32 Builds v4.4.1-tdm-2 SJLJ:
...which can be found here: [http://sourceforge.net/projects/tdm-gcc/files/] under: TDM-GCC 4.4 series -> 4.4.1-tdm-2 SJLJ.
* Compiler:
** gcc-4.4.1-tdm-2-core.zip
** gcc-4.4.1-tdm-2-g++.zip
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326-3.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz
These packages are included in both the Bundled Installer and the On-Demand Installer available via TDMs [https://jmeubank.github.io/tdm-gcc/download/ download page].

=== Embarcadero C++ Compiler BCC32C ===
Formerly Borland's C++ Compiler, this compiler is now published by Embarcadero, with active on-going development; the current version is 10.1 as of this writing. Go to [https://www.embarcadero.com/free-tools/ccompiler their product download page] to download. You will be asked to enter some registration information (registration is free) then the download will begin. You will receive a ZIP archive which contains installation instructions in a text file in the root directory of the archive; it does not have an installer program.

=== Digital Mars C/C++ Free Compiler ===
Go to [http://www.digitalmars.com/download/dmcpp.html DigitalMars]. Accept the license agreement and you'll be redirected to a page containing download links.

In that page, download:
*The '''Digital Mars C/C++ Compiler''' (<tt>dm8**c.zip</tt>)
*The '''Basic Utilities''' (<tt>bup.zip</tt>)
*The '''STLport''' library (<tt>stlport.zip</tt>)

Open <tt>dm\bin\sc.ini</tt> in a text editor, and replace the line
INCLUDE="%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%
with
INCLUDE="%@P%\..\stlport\stlport";"%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%

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

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

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

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

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

=== Digital Mars D Compiler for Windows ===
Now Digital Mars D Compiler (DMD) supports 32bit Windows, and in future it will support 64bit Windows.
If you want to build D program in CodeBlocks on 32bit Windows, please following the instructions as bellow.

1). Install DMD(2.0) into your Windows system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Windows http://www.digitalmars.com/d/2.0/dmd-windows.html

The newest DMD2 source you can get here: https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''

2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
2.2). click "Compiler settings -> Other options", add '''-m32''' into the field;
2.3). click "Linker settings", and add "'''D:\Program\DMD2\windows\lib\phobos.lib'''" into the "Link libraries";
2.4). click "Search directories -> Compiler", and add "'''D:\Program\DMD2\src\phobos'''" into the field;
2.5). click "Search directories -> Linker", and add "'''D:\Program\DMD2\windows\lib'''" into the field;
2.6). click "Toolchain executables", add "'''D:\Program\DMD2\windows'''" into the "Compiler's installation directory" filed;
(if you installed DMD2 correctly acc. to Installation setp, just click 'Auto-detect' button.)
2.7). Additional: If you wan to specify the DMC (Digital Mars C/C++ Compiler) you can do like this:
click "Toolchain executables -> Additional Paths", and add "D:\Program\DMC\bin" into the field.

The "D:\Program\DMD2" or "D:\Program\DMC\bin" here should change to your own DMD or DMC path in your system.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

== Linux ==

At the time of this writing, Code::Blocks supports the following compilers in Linux:
* [http://gcc.gnu.org/ GNU GCC C/C++ Free Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-linux.html Digital Mars D Compiler for Linux]

===Digital Mars D Compiler for Linux===
Now Digital Mars D Compiler (DMD) supports 32bit and 64bit Linux, and 'support Linux library' is under construction. If you want to build D program in CodeBlocks on 32bit and 64bit Linux, please following the instructions as bellow.

1). Install DMD(2.0) into your Linux system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Linux http://www.digitalmars.com/d/2.0/dmd-linux.html

The newest DMD2 source you can get here:
https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

A). 32bit Linux & 32bit DMD2.

On 32bit Linux, you should combine 32bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''.

A.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
A.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
A.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
A.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
A.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
A.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
A.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B1). 64bit Linux & '''64bit DMD2'''.

On 64bit Linux, you can combine 64bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B1.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B1.2). click "Compiler settings -> Other options", add '''-m64''' into the field.
B1.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib64/libphobos2.a'''" into the "Link libraries".
B1.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B1.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib64'''" into the field.
B1.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B1.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m64 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B2). 64bit Linux with '''32bit DMD2'''.

On 64bit Linux, you can combine 32bit DMD2 with 64bit together from DMD2 source and install them into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B2.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
B2.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
B2.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B2.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
B2.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B2.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Linux you'll, most probably, already have everything that is needed in order to compile. All major Linux distributions (RedHat, Debian, SuSE, Mandriva, Gentoo, ArchLinux, etc) come with GCC & GDB preinstalled. To make sure you have have gcc installed, go to your terminal and type 'gcc -v'. In case you have GCC installed, you will get GCC's compile options and version number.

==Mac OS X==
The Mac OS X port efforts has began recently, but it should be a matter of time until these compilers will be supported:
* [http://gcc.gnu.org/ GNU GCC]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel Compiler beta (not yet released to public)]
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Mac you'll need to install a ''compatible'' version Xcode Tools from http://developer.apple.com/tools/ (or http://developer.apple.com/downloads). You need the "Command Line Tools".

This will install Apple versions of:

http://www.gnu.org/software/gcc/

http://www.gnu.org/software/gdb/

http://www.gnu.org/software/make/

=== Setting up compiler switches ===

Usually you need to tweak the compiler options to be able to compile C++ applications - that's the stuff Xcode hides from your eyes, but you better should know. You need to point to the GNU compiler's C/C++ include folders, to the GNU linkers libraries folder and a adjust the compiler options to setup the GNU compiler root path. Those path's differ depending on what hardware (processor architecture) and what version of MacOS is used. For an Intel based Mac with MacOS 10.6.2 and Xcode v3.2.2 the following should work:

Compiler search directories ("include" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1
</code>

Linker search directories ("library" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib/gcc/i686-apple-darwin10/4.2.1
</code>

Additional compiler flags:

<code>
-isysroot /Developer/SDKs/MacOSX10.6.sdk -mmacosx-version-min=10.6 -gdwarf-2
</code>

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

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

== Misc. Custom Compilers ==
There are several user contributions for different (non-C/C++) compiler which are listed here:

https://wiki.codeblocks.org/index.php?title=User_documentation#Compilers

CB Clangd Client

2024-10-12T16:34:29Z

MichaelAgarkov: Reformat page to be properly formatted, removed double spacebars

The repository page of this plugin is: [https://svn.code.sf.net/p/codeblocks/code/trunk/src/plugins/contrib/clangd_client https://sourceforge.net/projects/cb-clangd-client/]

It uses [https://clangd.llvm.org/ clangd] through [https://en.wikipedia.org/wiki/Language_Server_Protocol Language Server Protocol].

The related forum discussion is: — [https://forums.codeblocks.org/index.php/topic,24357.html Code completion using LSP and clangd]
== '''What is Clangd'''==
clangd understands your C++ code and adds smart features to your editor

* code completion
* compile errors
* go-to-definition
* go-to-implementation
* find references

and more.

clangd is a language server that can work with your editor via a plugin.
CodeBlocks provides Clangd_client as the needed plugin.

Clangd_client additionally enhances the clangd server by providing:

* call tips
* function definitions
* parameter definitions
* previous and next function positioning
* symbols browser
* go-to-file
* go-to-function
* symbol renaming

----

=='''Configuring clangd_client'''==
Clangd_client requires the third-party binary clangd executable.

See '''Windows: Compiler Clangd/LLVM Package Installer''' below to install it.

or '''Linux: Clangd executable install process'''

After a successful clangd executable install, perform the following:<blockquote>Disable the "CodeCompletion" plugin.

* Navigate to Setting->Plugins->Manage Plugins and '''disable''' CodeCompletion.
* Navigate to Setting->Plugins->Manage Plugins and '''enable''' Clangd_client.

'''Restart Codeblocks'''.

Tell CodeBlocks (or verify) where the clangd executable resides:

* Navigate to Setting->Editor->Clangd_client->C/C++ parser(tab) and verify or enter the location of the clangd executable in the box labeled "Specify clangd executable to use".
</blockquote>
----

== '''Installing Clangd_client from source or pre-built binary ''' ==
Note: Clangd_client is now included as a contrib plugin within the "Nightly" builds.

Using a "Nightly" build is the easiest way to update to clangd_client.

Simply install the "Nightly" and configure as specified below.

See the Nightly builds at https://forums.codeblocks.org/index.php/board,20.0.html

# Install the LLVM or Clangd.exe as documented in the section below entitled:
#:'''Windows Clangd executable install process'''
# Disable the Code completion plugin as follows:
#: a) Open the Plugin manager via Code::Blocks menu
#:: "MainMenu=>Plugins=>Manage plugins..."
#: b) In the Manage Plugin dialog do the following:
#:: i ) Find and select the "Code completion" plugin via it's title
#:: ii ) Press the "Disable" button on the right near the top
#:: iii) If you get any errors please try again.
# Install the Clangd-Client Plugin using one of the following options, which are documented below:
#: a) Install via the Plugin Manager
#: b) Manually install the plugin files
# Configure the Clangd-Client Plugin for use as follows:
#: a) Select the CodeBlocks menu item "Settings->Editor..."
#: b) In the list on the left click/select the "clangd_client" option.
#: c) In the "C/C++ parser" tab change the "Specify clangd executable to use" to reference the clangd.exe you installed via step 1) above.
#: Some examples of this could be:
#:* C:\msys64\clang64\bin\clangd.exe
#:* C:\msys64\clang32\bin\clangd.exe
#:* C:\msys64\mingw64\bin\clangd.exe
#:* C:\msys64\mingw32\bin\clangd.exe
#:* C:\LLVM\bin\clangd.exe
#:* C:\comilers\clang\clangd.exe
----

== '''Manually Remove Clangd-Client Plugin''' ==

# Exit Code::Blocks!
# If you manually installed the files or used the Plugin manager then you can do the following:
#: a) In the Code::Blocks '''...\share\CodeBlocks''' folder delete the clangd_client.zip file
#: b) In the Code::Blocks '''...\share\CodeBlocks\plugins''' folder delete the clangd_client.dll file
# If you installed via the Plugin manager then you can delete the files with the following commands:
#: a) del '''%APPDATA%\CodeBlocks\share\codeblocks\plugins\clangd_client.dll'''
#: b) del '''%APPDATA%\CodeBlocks\share\codeblocks\clangd_client.zip'''
# If you want to reuse older code completion remember to re-enable the plugin and restart CodeBlocks.
----

== '''Windows: Clangd executable install process:''' ==
There are three main options to install the clangd.exe:
# Install the LLVM compiler.
# Manully extract the required files from the LLVM compiler.
# Install the Clangd package for the Windows compiler you are using if it is available.
The process for the three options above are detailed below.
----

== '''Windows: Install the LLVM compiler''' ==

# Download the latest (non RC/Beta) LLVM Windows executable for your OS (Win32 or Win64) from the following
#: Github LLVM download page: https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.8
#: As of Jan 2022 the Windows files are named as follows:
#:* LLVM-<version>-win64.exe
#:* LLVM-<version>-win32.exe
#: where <version> is the LLVM version, like 13.0.0 or 13.0.1.
# Run the LLVM-<version>-win<xx>.exe you downloaded to install the LLVM compiler.

----

== '''Windows: Compiler Clangd/LLVM Package Installer''' ==
Due to the number of different compilers available for Windows not all of the compilers will have either/both the Clang or LLVM required files.

If you want to install the specific package(s) for the Windows compiler you are using in order to use it's clangd.exe file please follow the instructions below for the specific compiler you have installed:

'''MSYS2 Compiler - MinGW64'''
There are two main options to install the clangd.exe as follows:
1) The first option in order to minimise disk space is to install the Clang extra
tools using one of the following packages:
+------------------------------------------+------------------------+
<nowiki>| Package |</nowiki> Clangd executable |
+------------------------------------------+------------------------+
<nowiki>| mingw-w64-clang-x86_64-clang-tools-extra |</nowiki> clang64/bin/clangd.exe |
<nowiki>| mingw-w64-x86_64-clang-tools-extra |</nowiki> mingw64/bin/clangd.exe |
<nowiki>| mingw-w64-ucrt-x86_64-clang-tools-extra |</nowiki> ucrt64/bin/clangd.exe |
+------------------------------------------+------------------------+
<nowiki> </nowiki> To intall the package do the following:
<nowiki> </nowiki> a) Open the msys2.exe bash shell
<nowiki> </nowiki> b) Run the following command:
<nowiki> </nowiki> pacman -S <Package name in the table above>
<nowiki> </nowiki> <nowiki>'''</nowiki>OR<nowiki>'''</nowiki>
<nowiki> </nowiki> 2) The second option is to intall the full Clang tool chain as follows:
<nowiki> </nowiki> a) Open the msys2.exe bash shell
<nowiki> </nowiki> b) Run the following command:
<nowiki> </nowiki> pacman -S mingw-w64-clang-x86_64-toolchain
'''MSYS2 Compiler - MinGW32'''
<pre>
There are two main options to install the clangd.exe as follows:

1) The first option in order to minimise disk space is to install the Clang extra
tools using one of the following packages:

+------------------------------------------+------------------------+
| Package | Clangd executable |
+------------------------------------------+------------------------+
| mingw-w64-clang-i686-clang-tools-extra | clang32/bin/clangd.exe |
| mingw-w64-i686-clang-tools-extra | mingw32/bin/clangd.exe |
+------------------------------------------+------------------------+

To intall the package do the following:
a) Open the msys2.exe bash shell
b) Run the following command:
pacman -S <Package name in the table above>

'''OR'''

2) The second option is to install the full Clang tool chain as follows:
a) Open the msys2.exe bash shell
b) Run the following command:
pacman -S mingw-w64-clang-i686-toolchain
</pre>'''[https://forums.codeblocks.org/index.php/topic,24357.msg169412.html#msg169412 Notes from the CodeBlocks forum to avoid mixing incompatible gcc/clangd executables]'''

'''Don't mix mingw64 with clang64'''.

If you are using the gcc from msys2, (the compilers in the folder '''msys64\mingw64\bin'''), you should use "mingw-w64-x86_64-clang-tools-extra", (the clangd.exe is under the folder '''msys64\mingw64\bin''') the same folder as your gcc.exe. If you are using the clang tool chain, (the folder '''msys64\clang64\bin'''), you should use "mingw-w64-clang-x86_64-clang-tools-extra". I found that I just make a big mistake. That is: I used the gcc toolchain from '''msys64\mingw64\bin''', but I used the clangd.exe from '''msys64\clang64\bin'''. The result is I got a lot of LSP diagnostics messages and errors. Luckily I found the reason, and fixed this issue. Hope this will help others.
-----
== '''Linux: Clangd executable install process:''' ==
NOTE: Clangd_client plugin requires a clangd executable version 13 or greater.

Check your current clangd version by running '''clangd --version'''

If the version is less than 13 you will have to install a newer version.

See https://clangd.llvm.org/installation.html<blockquote>Installing the clangd package will usually give you a slightly older version.

Test this by issuing '''apt-get install --dry-run clangd'''

As of 2022/11/16, this suggest that clangd version 10 will be installed.</blockquote>If the clangd version shows less than version 13, you'll have to install a specific version as follows:<blockquote>Install a packaged release (''must be version 13 or greater''):

'''sudo apt-get install clangd-13''' ''(Must be version 13 or greater)''.</blockquote>This will install clangd as '''/usr/bin/clangd-13'''.

You can now configure clangd_client plugin by following the above instructions at

[https://wiki.codeblocks.org/index.php/CB_Clangd_Client#Configuring_clangd_client] '''Configuring clangd_client'''

If you prefer to install the entire LLVM/Clang package, for convenience, there is an automatic installation script available that installs LLVM for you.

To install the latest stable version: see [https://apt.llvm.org/] '''Automatic installation script'''.

Note that you can specify the version number with this script.
----

MinGW installation

2024-10-12T13:30:19Z

MichaelAgarkov: Fix links to MinGW and 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. 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 ==

[https://jmeubank.github.io/tdm-gcc/ 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 ==

[https://osdn.net/projects/mingw/ 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]

User talk:MichaelAgarkov

2024-10-12T13:24:40Z

MichaelAgarkov: Created blank page

User:MichaelAgarkov

2024-10-12T12:22:23Z

MichaelAgarkov: Added email link

Contact email: [mailto:michaelagarkov@outlook.com michaelagarkov@outlook.com]

GitHub: https://github.com/MichaelAgarkov

User:MichaelAgarkov

2024-10-12T12:21:41Z

MichaelAgarkov: Added a personal page with contact information

Contact email: michaelagarkov@outlook.com
GitHub: https://github.com/MichaelAgarkov

Installing a supported compiler

2024-10-12T12:13:19Z

MichaelAgarkov: Fix old MinGW sourceforge repository link

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

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

== Compiler-neutral setup steps ==

Before using a compiler with Code::Blocks you have to install it. The method for installing the compiler depends on the Operating system you're using, the Compiler you intend to use and so on.
If you installed the compiler on its default installation directory, there is nothing more to configure (if the compiler is natively supported by Code::Blocks). Launch Code::Blocks and you're all set :)

* If that is not the case, launch Code::Blocks. If it is the first time you launch it, the compiler auto-detection will be launched.
* If your compiler was not auto-detected, go to "Settings->Compiler and Debugger->Global Compiler settings->Toolchain executables", select the compiler you installed and press "Auto-detect".
* If you get a message saying that the compiler was auto-detected, congratulations!
* If not, then press the button with the three dots next to the "Auto-detect" button and select the installation directory of your compiler manually.

NOTE: ''The compiler's installation directory is exactly this: the installation directory. Not the "bin" subdirectory nor any other.''

== Windows ==

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

At the time of this writing, Code::Blocks supports the following compilers in Windows:
* [http://www.mingw.org MinGW GCC C/C++ Free Compiler, including GFortran]
** [http://www.cygwin.org Cygwin GCC C/C++ Free Compiler]
*** [[#HOWTO: Use Cygwin 1.7 with Code::Blocks|HOWTO: Use Cygwin 1.7 with Code::Blocks]]
* [http://www.ti.com/tool/msp430-gcc-opensource MSP430 GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html TriCore GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html PowerPC GCC C/C++]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.digitalmars.com/ Digital Mars Free C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-windows.html Digital Mars D Compiler for Windows]
These compilers are generally still under active development by their publishers, so a new version of their software could be released that is incompatible with the current version of Code::Blocks.

The following compilers are still supported by Code::Blocks, but are no longer available from their original publishers.
* Microsoft's Visual C++ 2003 - 2010
* Borland's C/C++ Free Compiler 5.5

The following publishers have released newer versions of their compilers which should be tested against the current configuration. In other words, it is not known yet whether these compilers still work with Code::Blocks.

* [http://www.openwatcom.org/download.php OpenWatcom Free C/C++ Compiler]
* [https://software.intel.com/en-us/c-compilers/ipsxe Intel C/C++ Compiler] 

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

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

==== Official MinGW ====
You can install '''MinGW''' yourself, by using an automatic downloader/installer or by downloading and unpacking the required packages by hand from [https://osdn.net/projects/mingw/ OSDN], if needed, here is the [https://sourceforge.net/projects/mingw/ old sourceforge repository].

Packages required (suggested) for MinGW/GCC:

* Compiler:
** gcc-build-3.4.5-20060117-3.tar.gz
** gcc-core-3.4.5-20060117-3.tar.gz
** gcc-g++-3.4.5-20060117-3.tar.gz
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz

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

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

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

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

'''Solution'''

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

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

After this, compilation and linking worked fine.

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

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

See also: [[Installing Cygwin Compiler]]

==== (Unofficial) TDM - "Twilight Dragon Media" ====
These packages are called '''TDM's GCC/mingw32 Builds''' and can be obtained from [https://jmeubank.github.io/tdm-gcc/ here].

Packages required (suggested) for TDM's GCC/mingw32 Builds v4.4.1-tdm-2 SJLJ:
...which can be found here: [http://sourceforge.net/projects/tdm-gcc/files/] under: TDM-GCC 4.4 series -> 4.4.1-tdm-2 SJLJ.
* Compiler:
** gcc-4.4.1-tdm-2-core.zip
** gcc-4.4.1-tdm-2-g++.zip
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326-3.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz
These packages are included in both the Bundled Installer and the On-Demand Installer available via TDMs [https://jmeubank.github.io/tdm-gcc/download/ download page].

=== Embarcadero C++ Compiler BCC32C ===
Formerly Borland's C++ Compiler, this compiler is now published by Embarcadero, with active on-going development; the current version is 10.1 as of this writing. Go to [https://www.embarcadero.com/free-tools/ccompiler their product download page] to download. You will be asked to enter some registration information (registration is free) then the download will begin. You will receive a ZIP archive which contains installation instructions in a text file in the root directory of the archive; it does not have an installer program.

=== Digital Mars C/C++ Free Compiler ===
Go to [http://www.digitalmars.com/download/dmcpp.html DigitalMars]. Accept the license agreement and you'll be redirected to a page containing download links.

In that page, download:
*The '''Digital Mars C/C++ Compiler''' (<tt>dm8**c.zip</tt>)
*The '''Basic Utilities''' (<tt>bup.zip</tt>)
*The '''STLport''' library (<tt>stlport.zip</tt>)

Open <tt>dm\bin\sc.ini</tt> in a text editor, and replace the line
INCLUDE="%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%
with
INCLUDE="%@P%\..\stlport\stlport";"%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%

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

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

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

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

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

=== Digital Mars D Compiler for Windows ===
Now Digital Mars D Compiler (DMD) supports 32bit Windows, and in future it will support 64bit Windows.
If you want to build D program in CodeBlocks on 32bit Windows, please following the instructions as bellow.

1). Install DMD(2.0) into your Windows system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Windows http://www.digitalmars.com/d/2.0/dmd-windows.html

The newest DMD2 source you can get here: https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''

2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
2.2). click "Compiler settings -> Other options", add '''-m32''' into the field;
2.3). click "Linker settings", and add "'''D:\Program\DMD2\windows\lib\phobos.lib'''" into the "Link libraries";
2.4). click "Search directories -> Compiler", and add "'''D:\Program\DMD2\src\phobos'''" into the field;
2.5). click "Search directories -> Linker", and add "'''D:\Program\DMD2\windows\lib'''" into the field;
2.6). click "Toolchain executables", add "'''D:\Program\DMD2\windows'''" into the "Compiler's installation directory" filed;
(if you installed DMD2 correctly acc. to Installation setp, just click 'Auto-detect' button.)
2.7). Additional: If you wan to specify the DMC (Digital Mars C/C++ Compiler) you can do like this:
click "Toolchain executables -> Additional Paths", and add "D:\Program\DMC\bin" into the field.

The "D:\Program\DMD2" or "D:\Program\DMC\bin" here should change to your own DMD or DMC path in your system.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

== Linux ==

At the time of this writing, Code::Blocks supports the following compilers in Linux:
* [http://gcc.gnu.org/ GNU GCC C/C++ Free Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-linux.html Digital Mars D Compiler for Linux]

===Digital Mars D Compiler for Linux===
Now Digital Mars D Compiler (DMD) supports 32bit and 64bit Linux, and 'support Linux library' is under construction. If you want to build D program in CodeBlocks on 32bit and 64bit Linux, please following the instructions as bellow.

1). Install DMD(2.0) into your Linux system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Linux http://www.digitalmars.com/d/2.0/dmd-linux.html

The newest DMD2 source you can get here:
https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

A). 32bit Linux & 32bit DMD2.

On 32bit Linux, you should combine 32bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''.

A.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
A.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
A.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
A.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
A.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
A.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
A.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B1). 64bit Linux & '''64bit DMD2'''.

On 64bit Linux, you can combine 64bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B1.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B1.2). click "Compiler settings -> Other options", add '''-m64''' into the field.
B1.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib64/libphobos2.a'''" into the "Link libraries".
B1.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B1.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib64'''" into the field.
B1.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B1.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m64 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B2). 64bit Linux with '''32bit DMD2'''.

On 64bit Linux, you can combine 32bit DMD2 with 64bit together from DMD2 source and install them into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B2.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
B2.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
B2.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B2.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
B2.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B2.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Linux you'll, most probably, already have everything that is needed in order to compile. All major Linux distributions (RedHat, Debian, SuSE, Mandriva, Gentoo, ArchLinux, etc) come with GCC & GDB preinstalled. To make sure you have have gcc installed, go to your terminal and type 'gcc -v'. In case you have GCC installed, you will get GCC's compile options and version number.

==Mac OS X==
The Mac OS X port efforts has began recently, but it should be a matter of time until these compilers will be supported:
* [http://gcc.gnu.org/ GNU GCC]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel Compiler beta (not yet released to public)]
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Mac you'll need to install a ''compatible'' version Xcode Tools from http://developer.apple.com/tools/ (or http://developer.apple.com/downloads). You need the "Command Line Tools".

This will install Apple versions of:

http://www.gnu.org/software/gcc/

http://www.gnu.org/software/gdb/

http://www.gnu.org/software/make/

=== Setting up compiler switches ===

Usually you need to tweak the compiler options to be able to compile C++ applications - that's the stuff Xcode hides from your eyes, but you better should know. You need to point to the GNU compiler's C/C++ include folders, to the GNU linkers libraries folder and a adjust the compiler options to setup the GNU compiler root path. Those path's differ depending on what hardware (processor architecture) and what version of MacOS is used. For an Intel based Mac with MacOS 10.6.2 and Xcode v3.2.2 the following should work:

Compiler search directories ("include" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1
</code>

Linker search directories ("library" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib/gcc/i686-apple-darwin10/4.2.1
</code>

Additional compiler flags:

<code>
-isysroot /Developer/SDKs/MacOSX10.6.sdk -mmacosx-version-min=10.6 -gdwarf-2
</code>

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

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

== Misc. Custom Compilers ==
There are several user contributions for different (non-C/C++) compiler which are listed here:

https://wiki.codeblocks.org/index.php?title=User_documentation#Compilers

Installing a supported compiler

2024-10-12T12:11:59Z

MichaelAgarkov: Replace old MinGW and TDM-GCC links with new working ones

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

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

== Compiler-neutral setup steps ==

Before using a compiler with Code::Blocks you have to install it. The method for installing the compiler depends on the Operating system you're using, the Compiler you intend to use and so on.
If you installed the compiler on its default installation directory, there is nothing more to configure (if the compiler is natively supported by Code::Blocks). Launch Code::Blocks and you're all set :)

* If that is not the case, launch Code::Blocks. If it is the first time you launch it, the compiler auto-detection will be launched.
* If your compiler was not auto-detected, go to "Settings->Compiler and Debugger->Global Compiler settings->Toolchain executables", select the compiler you installed and press "Auto-detect".
* If you get a message saying that the compiler was auto-detected, congratulations!
* If not, then press the button with the three dots next to the "Auto-detect" button and select the installation directory of your compiler manually.

NOTE: ''The compiler's installation directory is exactly this: the installation directory. Not the "bin" subdirectory nor any other.''

== Windows ==

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

At the time of this writing, Code::Blocks supports the following compilers in Windows:
* [http://www.mingw.org MinGW GCC C/C++ Free Compiler, including GFortran]
** [http://www.cygwin.org Cygwin GCC C/C++ Free Compiler]
*** [[#HOWTO: Use Cygwin 1.7 with Code::Blocks|HOWTO: Use Cygwin 1.7 with Code::Blocks]]
* [http://www.ti.com/tool/msp430-gcc-opensource MSP430 GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html TriCore GCC C/C++]
* [http://www.hightec-rt.com/en/downloads/evaluation-version.html PowerPC GCC C/C++]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.digitalmars.com/ Digital Mars Free C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-windows.html Digital Mars D Compiler for Windows]
These compilers are generally still under active development by their publishers, so a new version of their software could be released that is incompatible with the current version of Code::Blocks.

The following compilers are still supported by Code::Blocks, but are no longer available from their original publishers.
* Microsoft's Visual C++ 2003 - 2010
* Borland's C/C++ Free Compiler 5.5

The following publishers have released newer versions of their compilers which should be tested against the current configuration. In other words, it is not known yet whether these compilers still work with Code::Blocks.

* [http://www.openwatcom.org/download.php OpenWatcom Free C/C++ Compiler]
* [https://software.intel.com/en-us/c-compilers/ipsxe Intel C/C++ Compiler] 

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

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

==== Official MinGW ====
You can install '''MinGW''' yourself, by using an automatic downloader/installer or by downloading and unpacking the required packages by hand from [https://osdn.net/projects/mingw/ OSDN], if needed, here is the [[http:projects/mingw/files/|old sourceforge repository]].

Packages required (suggested) for MinGW/GCC:

* Compiler:
** gcc-build-3.4.5-20060117-3.tar.gz
** gcc-core-3.4.5-20060117-3.tar.gz
** gcc-g++-3.4.5-20060117-3.tar.gz
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz

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

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

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

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

'''Solution'''

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

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

After this, compilation and linking worked fine.

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

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

See also: [[Installing Cygwin Compiler]]

==== (Unofficial) TDM - "Twilight Dragon Media" ====
These packages are called '''TDM's GCC/mingw32 Builds''' and can be obtained from [https://jmeubank.github.io/tdm-gcc/ here].

Packages required (suggested) for TDM's GCC/mingw32 Builds v4.4.1-tdm-2 SJLJ:
...which can be found here: [http://sourceforge.net/projects/tdm-gcc/files/] under: TDM-GCC 4.4 series -> 4.4.1-tdm-2 SJLJ.
* Compiler:
** gcc-4.4.1-tdm-2-core.zip
** gcc-4.4.1-tdm-2-g++.zip
* Components:
** binutils-2.19.1-mingw32-bin.tar.gz
** gdb-6.8-mingw-3.tar.bz2
** mingw32-make-3.81-20080326-3.tar.gz
** mingwrt-3.16-mingw32-dev.tar.gz
** mingwrt-3.16-mingw32-dll.tar.gz
** w32api-3.13-mingw32-dev.tar.gz
These packages are included in both the Bundled Installer and the On-Demand Installer available via TDMs [https://jmeubank.github.io/tdm-gcc/download/ download page].

=== Embarcadero C++ Compiler BCC32C ===
Formerly Borland's C++ Compiler, this compiler is now published by Embarcadero, with active on-going development; the current version is 10.1 as of this writing. Go to [https://www.embarcadero.com/free-tools/ccompiler their product download page] to download. You will be asked to enter some registration information (registration is free) then the download will begin. You will receive a ZIP archive which contains installation instructions in a text file in the root directory of the archive; it does not have an installer program.

=== Digital Mars C/C++ Free Compiler ===
Go to [http://www.digitalmars.com/download/dmcpp.html DigitalMars]. Accept the license agreement and you'll be redirected to a page containing download links.

In that page, download:
*The '''Digital Mars C/C++ Compiler''' (<tt>dm8**c.zip</tt>)
*The '''Basic Utilities''' (<tt>bup.zip</tt>)
*The '''STLport''' library (<tt>stlport.zip</tt>)

Open <tt>dm\bin\sc.ini</tt> in a text editor, and replace the line
INCLUDE="%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%
with
INCLUDE="%@P%\..\stlport\stlport";"%@P%\..\include";"%@P%\..\mfc\include";%INCLUDE%

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

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

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

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

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

=== Digital Mars D Compiler for Windows ===
Now Digital Mars D Compiler (DMD) supports 32bit Windows, and in future it will support 64bit Windows.
If you want to build D program in CodeBlocks on 32bit Windows, please following the instructions as bellow.

1). Install DMD(2.0) into your Windows system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Windows http://www.digitalmars.com/d/2.0/dmd-windows.html

The newest DMD2 source you can get here: https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''

2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
2.2). click "Compiler settings -> Other options", add '''-m32''' into the field;
2.3). click "Linker settings", and add "'''D:\Program\DMD2\windows\lib\phobos.lib'''" into the "Link libraries";
2.4). click "Search directories -> Compiler", and add "'''D:\Program\DMD2\src\phobos'''" into the field;
2.5). click "Search directories -> Linker", and add "'''D:\Program\DMD2\windows\lib'''" into the field;
2.6). click "Toolchain executables", add "'''D:\Program\DMD2\windows'''" into the "Compiler's installation directory" filed;
(if you installed DMD2 correctly acc. to Installation setp, just click 'Auto-detect' button.)
2.7). Additional: If you wan to specify the DMC (Digital Mars C/C++ Compiler) you can do like this:
click "Toolchain executables -> Additional Paths", and add "D:\Program\DMC\bin" into the field.

The "D:\Program\DMD2" or "D:\Program\DMC\bin" here should change to your own DMD or DMC path in your system.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

== Linux ==

At the time of this writing, Code::Blocks supports the following compilers in Linux:
* [http://gcc.gnu.org/ GNU GCC C/C++ Free Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-linux.html Digital Mars D Compiler for Linux]

===Digital Mars D Compiler for Linux===
Now Digital Mars D Compiler (DMD) supports 32bit and 64bit Linux, and 'support Linux library' is under construction. If you want to build D program in CodeBlocks on 32bit and 64bit Linux, please following the instructions as bellow.

1). Install DMD(2.0) into your Linux system.

You should correctly combine the DMD compiler and install it into your system. Please view the instructions on digitalmars.com website.
DMD for Linux http://www.digitalmars.com/d/2.0/dmd-linux.html

The newest DMD2 source you can get here:
https://github.com/D-Programming-Language

2). Settings in CodeBlocks.

A). 32bit Linux & 32bit DMD2.

On 32bit Linux, you should combine 32bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD pathes into CodeBlocks '''Global compiler settings'''.

A.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
A.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
A.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
A.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
A.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
A.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
A.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B1). 64bit Linux & '''64bit DMD2'''.

On 64bit Linux, you can combine 64bit DMD2 from DMD2 source and install it into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B1.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B1.2). click "Compiler settings -> Other options", add '''-m64''' into the field.
B1.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib64/libphobos2.a'''" into the "Link libraries".
B1.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B1.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib64'''" into the field.
B1.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B1.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m64 -lrt'''" or "'''gcc -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

B2). 64bit Linux with '''32bit DMD2'''.

On 64bit Linux, you can combine 32bit DMD2 with 64bit together from DMD2 source and install them into your system.

You should add correct DMD paths into CodeBlocks '''Global compiler settings'''.

B2.1). "Settings -> Compiler and debugger settings" and choose compiler to "'''Digital Mars D Compiler'''";
B2.2). click "Compiler settings -> Other options", add '''-m32''' into the field.
B2.3). click "Linker settings", and add "'''/opt/dmd2/linux/lib32/libphobos2.a'''" into the "Link libraries".
B2.4). click "Search directories -> Compiler", and add "'''/opt/dmd2/src/phobos'''" into the field.
B2.5). click "Search directories -> Linker", and add "'''/opt/dmd2/linux/lib32'''" into the field.
B2.6). click "Toolchain executables", add "'''/opt/dmd2/linux'''" into the "Compiler's installation directory" filed.
B2.7). change the value of "Program Files -> Linker for dynamic libs" to "'''gcc -m32 -lrt'''".

If you installed DMD2 to a different path, please modify "/opt/dmd2" to your own DMD2 path.

3). Testing D program in CodeBlocks.

In CodeBlocks, produce a '''D Application''' project, and input your own D code into the .d file in the project, then '''build/run'''.

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Linux you'll, most probably, already have everything that is needed in order to compile. All major Linux distributions (RedHat, Debian, SuSE, Mandriva, Gentoo, ArchLinux, etc) come with GCC & GDB preinstalled. To make sure you have have gcc installed, go to your terminal and type 'gcc -v'. In case you have GCC installed, you will get GCC's compile options and version number.

==Mac OS X==
The Mac OS X port efforts has began recently, but it should be a matter of time until these compilers will be supported:
* [http://gcc.gnu.org/ GNU GCC]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel Compiler beta (not yet released to public)]
* [http://sdcc.sourceforge.net/ Small Device C Compiler (SDCC)]

=== Downloading the GNU GCC compiler & GDB debugger ===

Under Mac you'll need to install a ''compatible'' version Xcode Tools from http://developer.apple.com/tools/ (or http://developer.apple.com/downloads). You need the "Command Line Tools".

This will install Apple versions of:

http://www.gnu.org/software/gcc/

http://www.gnu.org/software/gdb/

http://www.gnu.org/software/make/

=== Setting up compiler switches ===

Usually you need to tweak the compiler options to be able to compile C++ applications - that's the stuff Xcode hides from your eyes, but you better should know. You need to point to the GNU compiler's C/C++ include folders, to the GNU linkers libraries folder and a adjust the compiler options to setup the GNU compiler root path. Those path's differ depending on what hardware (processor architecture) and what version of MacOS is used. For an Intel based Mac with MacOS 10.6.2 and Xcode v3.2.2 the following should work:

Compiler search directories ("include" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/include/c++/4.2.1
</code>

Linker search directories ("library" folders):

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib
</code>

<code>
/Developer/SDKs/MacOSX10.6.sdk/usr/lib/gcc/i686-apple-darwin10/4.2.1
</code>

Additional compiler flags:

<code>
-isysroot /Developer/SDKs/MacOSX10.6.sdk -mmacosx-version-min=10.6 -gdwarf-2
</code>

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

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

== Misc. Custom Compilers ==
There are several user contributions for different (non-C/C++) compiler which are listed here:

https://wiki.codeblocks.org/index.php?title=User_documentation#Compilers

FAQ-General

2023-09-11T19:47:27Z

MichaelAgarkov:

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: What is Code::Blocks? ====

'''A:''' Code::Blocks is an Integrated Development Environment, aka [[wikipedia:Integrated development environment|IDE]]. Thus, a framework for working with source code and using compilers and linkers (in the case of Code::Blocks, these can be several).

==== Q: What Code::Blocks is not? ====

'''A:''' Code::Blocks is not a [[wikipedia:Compiler|compiler]], nor a [[wikipedia:Linker (computing)|linker]]. Release packages of Code::Blocks may include a compiler suite (MinGW/GCC), if not provided by the target platform already. However, this is provided "as-is" and not developed/maintained by the Code::Blocks development team.

==== Q: What license is Code::Blocks released under? ====

'''A:''' GNU General Public License 3 ([http://www.gnu.org/licenses/gpl-3.0.html GPL]) with an exception for third party plugins that can be of any license (including closed source) as long as they use only the SDK sources of Code::Blocks.

As an example: If you use the Code::Blocks SDK to develop a plugin, this could be even commercial. When you start using/modifying source code of other parts (i.e. the Code::Blocks core or other GPL3 plugins) the modifications or relevant (affected) parts must be provided as source code, too. However, usually (probably 99.9% of the cases) you'll only need to use the SDK.

==== Q: When will the next stable version of Code::Blocks be released? ====

'''A:''' It was promised to be released after summer holidays of 2023 ([https://forums.codeblocks.org/index.php/topic,25371.0.html forum post]).

==== Q: Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ====

'''A:''' Yes, this is implemented, but you'll need the [[help plugin]]. So if you are using the installer, make sure you enable this plugin.

----

Return to '''[[FAQ]]'''.

FAQ-General

2023-09-11T19:45:59Z

MichaelAgarkov:

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: What is Code::Blocks? ====

'''A:''' Code::Blocks is an Integrated Development Environment, aka [[wikipedia:Integrated development environment|IDE]]. Thus, a framework for working with source code and using compilers and linkers (in the case of Code::Blocks, these can be several).

==== Q: What Code::Blocks is not? ====

'''A:''' Code::Blocks is not a [[wikipedia:Compiler|compiler]], nor a [[wikipedia:Linker (computing)|linker]]. Release packages of Code::Blocks may include a compiler suite (MinGW/GCC), if not provided by the target platform already. However, this is provided "as-is" and not developed/maintained by the Code::Blocks development team.

==== Q: What license is Code::Blocks released under? ====

'''A:''' GNU General Public License 3 ([http://www.gnu.org/licenses/gpl-3.0.html GPL]) with an exception for third party plugins that can be of any license (including closed source) as long as they use only the SDK sources of Code::Blocks.

As an example: If you use the Code::Blocks SDK to develop a plugin, this could be even commercial. When you start using/modifying source code of other parts (i.e. the Code::Blocks core or other GPL3 plugins) the modifications or relevant (affected) parts must be provided as source code, too. However, usually (probably 99.9% of the cases) you'll only need to use the SDK.

==== Q: When will the next stable version of Code::Blocks be released? ====

It was promised to be released after summer holidays of 2023 ([https://forums.codeblocks.org/index.php/topic,25371.0.html forum post]).

==== Q: Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ====

'''A:''' Yes, this is implemented, but you'll need the [[help plugin]]. So if you are using the installer, make sure you enable this plugin.

----

Return to '''[[FAQ]]'''.

FAQ-General

2023-09-11T19:42:02Z

MichaelAgarkov: Added information about the time when the next stable release is promised to be out.

[[Category:Code::Blocks Documentation]]
__TOC__
Return to '''[[FAQ]]'''.

----

==== Q: What is Code::Blocks? ====

'''A:''' Code::Blocks is an Integrated Development Environment, aka [[wikipedia:Integrated development environment|IDE]]. Thus, a framework for working with source code and using compilers and linkers (in the case of Code::Blocks, these can be several).

==== Q: What Code::Blocks is not? ====

'''A:''' Code::Blocks is not a [[wikipedia:Compiler|compiler]], nor a [[wikipedia:Linker (computing)|linker]]. Release packages of Code::Blocks may include a compiler suite (MinGW/GCC), if not provided by the target platform already. However, this is provided "as-is" and not developed/maintained by the Code::Blocks development team.

==== Q: What license is Code::Blocks released under? ====

'''A:''' GNU General Public License 3 ([http://www.gnu.org/licenses/gpl-3.0.html GPL]) with an exception for third party plugins that can be of any license (including closed source) as long as they use only the SDK sources of Code::Blocks.

As an example: If you use the Code::Blocks SDK to develop a plugin, this could be even commercial. When you start using/modifying source code of other parts (i.e. the Code::Blocks core or other GPL3 plugins) the modifications or relevant (affected) parts must be provided as source code, too. However, usually (probably 99.9% of the cases) you'll only need to use the SDK.

==== Q: When will the next stable version of Code::Blocks be released? ====

It was promised to be released after summer holidays of 2023 ([https://forums.codeblocks.org/index.php/topic,25371.0.html forum post])

==== Q: Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ====

'''A:''' Yes, this is implemented, but you'll need the [[help plugin]]. So if you are using the installer, make sure you enable this plugin.

----

Return to '''[[FAQ]]'''.