Code::Blocks - User contributions [en]

Fortran support in Code::Blocks

2016-05-10T19:03:47Z

Briedis:

Feature List

2015-04-04T05:42:37Z

Briedis: /* Compiler */

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

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

Feature List

2015-04-04T05:40:37Z

Briedis: /* Compiler */

[[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]] ([[Installing Fortran Compiler|incl. GFortran]]) (Linux)
** [[Installing a supported compiler#MinGW.2FGCC|MinGW GCC]] ([[Installing Fortran Compiler|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

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

Fortran Project plugin

2015-04-04T05:29:24Z

Briedis: /* See also */

[[Category:Code::Blocks 3rd Party Plugins]]
{{Infobox_Plugin|
name = FortranProject |
logo = [[File:Generic-plugin.png]] |
developer = Darius Markauskas |
maintainer = |
version = 0.8
}}

FortranProject plugin makes C::B more useful for Fortran programmers. It adds a symbol browser and code completion for Fortran files. Source code and pre-built binaries can be downloaded from the [http://darmar.vgtu.lt Fortran Project homepage] .

==See also==
* [[Fortran support in Code::Blocks|Fortran support in Code::Blocks]]

Fortran support in Code::Blocks

2015-04-04T05:28:05Z

Briedis:

Fortran support in Code::Blocks

2015-04-04T05:24:01Z

Briedis: /* Using gfortran instead of g77 */

Fortran support in Code::Blocks

2015-04-04T05:23:48Z

Briedis: /* Troubleshooting */

Fortran support in Code::Blocks

2015-04-04T05:23:34Z

Briedis: /* Setting up Fortran projects */

Fortran support in Code::Blocks

2015-04-04T05:22:58Z

Briedis: /* Adding new Fortran file type */

[[Category:User Documentation]]
Presently Code::Blocks IDE has support not only for C/C++ but for Fortran also. Features of Code::Blocks useful for Fortran:
* Editor with syntax highlighting for fixed and free Fortran source code
* Support for GFortran and PGI Fortran compilers. Other Fortran compilers can be added by users too. “Support for compiler” means: (a) the graphical interface for the options of the compiler and (b) catching of compilation errors and warnings and jumping to the corresponding code line
* During the compilation Code::Blocks cares about the dependencies between Fortran files in the project (it is important when Fortran modules are used)
* Symbol browser with program units and variables defined in Fortran files
* Code-completion
* Call-tips
* and some more.

Most of the functionality useful for Fortran is implemented through FortranProject plugin. More information about the use of Code::Blocks with Fortran can be found here [http://darmar.vgtu.lt/ here].

== Setting up Fortran projects ==
To work with Fortran files, do the following:
Add a (new) file to the project, saved as "your_fortran_file.f". Verify it's recognised as "Fortran Sources" file type. If not verify you have done the steps above correctly. To enable compiling the project which includes Fortran files follow these steps:
* Right click on the project, select "Build options" and make sure you have selected the "GNU G77 compiler" (see steps above).
* Right click on the "your_fortran_file.f" file and select "Properties".

1.) Enable "Compile file" and "Link file".

2.) Under the "Advanced" tab enter "CC" as compiler variable

* Compile the project, it should work by now.

== Troubleshooting ==
For troubleshooting enable the "Full command line" Under menu "Settings" -> "Compiler" -> "Other" tab, "Compiler logging". If you see that still the gcc compiler is invoked, make sure you setup the right compiler in the build options for your project '''AND''' your target (e.g. "default").

== Using gfortran instead of g77 ==
The preceding steps can also be used to set up Code::Blocks to use the GNU gfortran Fortran '95 compiler, albeit with the following changes:

* Setup the compiler as follows:

1.) The "Compiler's installation directory" should point to the location of the root directory of the gfortran installation, for example if gfortran.exe is located in C:\gfortran\bin the path should read "C:\gfortran" (minus quotes).

2.) Under the "Programs" tab, select "gfortran.exe" as both the C compiler and the linker for dynamic libs instead of "g77.exe"

3.) DO NOT add the linker commands as given previously; leave these fields blank.

* Adding new Fortran file type
Proceed as above, but add "*.f95" as a file type instead of "*.f77".

Follow the rest of the steps above and gfortran should work.

== See also ==
* [[Fortran Project plugin]] - Fortran code completion and symbol browser.

Fortran support in Code::Blocks

2015-04-04T05:22:27Z

Briedis: /* Fortran in Code::Blocks */

[[Category:User Documentation]]
Presently Code::Blocks IDE has support not only for C/C++ but for Fortran also. Features of Code::Blocks useful for Fortran:
* Editor with syntax highlighting for fixed and free Fortran source code
* Support for GFortran and PGI Fortran compilers. Other Fortran compilers can be added by users too. “Support for compiler” means: (a) the graphical interface for the options of the compiler and (b) catching of compilation errors and warnings and jumping to the corresponding code line
* During the compilation Code::Blocks cares about the dependencies between Fortran files in the project (it is important when Fortran modules are used)
* Symbol browser with program units and variables defined in Fortran files
* Code-completion
* Call-tips
* and some more.

Most of the functionality useful for Fortran is implemented through FortranProject plugin. More information about the use of Code::Blocks with Fortran can be found here [http://darmar.vgtu.lt/ here].

== Adding new Fortran file type ==
It makes sense to add a new "Fortran Sources" filetype to have the Fortran source code files being seperated. Steps to do so:
* Goto menu "Project" -> "Project tree" -> "Edit file types categories"
* Click on "Add" to add a new type of files
* Select "Fortran Sources" as group name
* Enter the following in the file-mask (without quotation marks): "*.f;*.f77;*.cmn;*.inc;"
* Click OK to close the dialog.
For your interest: "*.f;*.f77" are normally the default extensions for source code files, "*.cmn" is the extension for Fortran common-blocks and "*.inc" if often used as include file with e.g. variable declarations.

== Setting up Fortran projects ==
To work with Fortran files, do the following:
Add a (new) file to the project, saved as "your_fortran_file.f". Verify it's recognised as "Fortran Sources" file type. If not verify you have done the steps above correctly. To enable compiling the project which includes Fortran files follow these steps:
* Right click on the project, select "Build options" and make sure you have selected the "GNU G77 compiler" (see steps above).
* Right click on the "your_fortran_file.f" file and select "Properties".

1.) Enable "Compile file" and "Link file".

2.) Under the "Advanced" tab enter "CC" as compiler variable

* Compile the project, it should work by now.

== Troubleshooting ==
For troubleshooting enable the "Full command line" Under menu "Settings" -> "Compiler" -> "Other" tab, "Compiler logging". If you see that still the gcc compiler is invoked, make sure you setup the right compiler in the build options for your project '''AND''' your target (e.g. "default").

== Using gfortran instead of g77 ==
The preceding steps can also be used to set up Code::Blocks to use the GNU gfortran Fortran '95 compiler, albeit with the following changes:

* Setup the compiler as follows:

1.) The "Compiler's installation directory" should point to the location of the root directory of the gfortran installation, for example if gfortran.exe is located in C:\gfortran\bin the path should read "C:\gfortran" (minus quotes).

2.) Under the "Programs" tab, select "gfortran.exe" as both the C compiler and the linker for dynamic libs instead of "g77.exe"

3.) DO NOT add the linker commands as given previously; leave these fields blank.

* Adding new Fortran file type
Proceed as above, but add "*.f95" as a file type instead of "*.f77".

Follow the rest of the steps above and gfortran should work.

== See also ==
* [[Fortran Project plugin]] - Fortran code completion and symbol browser.

Talk:Installing Fortran Compiler

2015-04-04T05:11:44Z

Briedis: moved Talk:Installing Fortran Compiler to Talk:Fortran support in Code::Blocks: Obsolete information

#REDIRECT [[Talk:Fortran support in Code::Blocks]]

Talk:Fortran support in Code::Blocks

2015-04-04T05:11:44Z

Briedis: moved Talk:Installing Fortran Compiler to Talk:Fortran support in Code::Blocks: Obsolete information

need to incorporate discussion of lexers (fortran 77 vs fortran 90+) and debugging fortran programs. either here or on a linked page.

References:

/index.php/topic,6526.0.html
[[User:Dmoore|Dmoore]] 16:29, 26 July 2007 (UTC)

Installing Fortran Compiler

2015-04-04T05:11:43Z

Briedis: moved Installing Fortran Compiler to Fortran support in Code::Blocks: Obsolete information

#REDIRECT [[Fortran support in Code::Blocks]]

Fortran support in Code::Blocks

2015-04-04T05:11:43Z

Briedis: moved Installing Fortran Compiler to Fortran support in Code::Blocks: Obsolete information

[[Category:User Documentation]]
== Attaching the compiler framework ==
To attach the GNU Fortran 77 Compiler (G77) the following steps are required:
* Make a copy of the GNU GCC compiler as follows:

1.) Goto menu "Settings" -> "Compiler"

2.) Select the "GNU GCC Compiler", click the "Copy Button"

3.) Save the copy e.g. under "GNU G77 Compiler"

* Setup the compiler as follows:

1.) The path etc. should be as of the GCC Compiler. If this has been setup correctly, no changes are required. Otherwise refer to the setup of the GNU GCC compiler.

2.) Change under the "Programs" tab: "C compiler" = "g77.exe", "Linker for dynamic libs": "g77.exe"

3.) If you mix Fortran with C programs then add "-lg2c" in the "Linker" tab (and "-lstdc++" if you have mixed Fortran/C and C++ projects) under "Other linker options".

* Important: Make sure the path environment is setup to really point a path that contains the Fortran compiler suite. C::B with MinGW does '''NOT''' include the Fortran compiler. You may download the compiler under [http://www.mingw.org MinGW webpage]. "gcc-g77-3.4.2-20040916-1.tar.gz" is the name of the package I expect you want.

== Adding new Fortran file type ==
It makes sense to add a new "Fortran Sources" filetype to have the Fortran source code files being seperated. Steps to do so:
* Goto menu "Project" -> "Project tree" -> "Edit file types categories"
* Click on "Add" to add a new type of files
* Select "Fortran Sources" as group name
* Enter the following in the file-mask (without quotation marks): "*.f;*.f77;*.cmn;*.inc;"
* Click OK to close the dialog.
For your interest: "*.f;*.f77" are normally the default extensions for source code files, "*.cmn" is the extension for Fortran common-blocks and "*.inc" if often used as include file with e.g. variable declarations.

== Setting up Fortran projects ==
To work with Fortran files, do the following:
Add a (new) file to the project, saved as "your_fortran_file.f". Verify it's recognised as "Fortran Sources" file type. If not verify you have done the steps above correctly. To enable compiling the project which includes Fortran files follow these steps:
* Right click on the project, select "Build options" and make sure you have selected the "GNU G77 compiler" (see steps above).
* Right click on the "your_fortran_file.f" file and select "Properties".

1.) Enable "Compile file" and "Link file".

2.) Under the "Advanced" tab enter "CC" as compiler variable

* Compile the project, it should work by now.

== Troubleshooting ==
For troubleshooting enable the "Full command line" Under menu "Settings" -> "Compiler" -> "Other" tab, "Compiler logging". If you see that still the gcc compiler is invoked, make sure you setup the right compiler in the build options for your project '''AND''' your target (e.g. "default").

== Using gfortran instead of g77 ==
The preceding steps can also be used to set up Code::Blocks to use the GNU gfortran Fortran '95 compiler, albeit with the following changes:

* Setup the compiler as follows:

1.) The "Compiler's installation directory" should point to the location of the root directory of the gfortran installation, for example if gfortran.exe is located in C:\gfortran\bin the path should read "C:\gfortran" (minus quotes).

2.) Under the "Programs" tab, select "gfortran.exe" as both the C compiler and the linker for dynamic libs instead of "g77.exe"

3.) DO NOT add the linker commands as given previously; leave these fields blank.

* Adding new Fortran file type
Proceed as above, but add "*.f95" as a file type instead of "*.f77".

Follow the rest of the steps above and gfortran should work.

== See also ==
* [[Fortran Project plugin]] - Fortran code completion and symbol browser.

Installing a supported compiler

2015-04-04T04:58:27Z

Briedis: /* Windows */

[[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://mspgcc.sourceforge.net/ MSP430 GCC C/C++]
* [http://www.hightec-rt.com/ TriCore GCC C/C++]
* [http://www.hightec-rt.com/ PowerPC GCC C/C++]
* [http://msdn.microsoft.com/visualc/vctoolkit2003 Microsoft's Visual C++ Free Toolkit 2003]
* [http://www.borland.com/products/downloads/download_cbuilder.html Borland's C/C++ Free Compiler 5.5]
* [http://www.digitalmars.com/ Digital Mars Free C/C++ Compiler]
* [http://store.scitechsoft.com/product_info.php?products_id=37/ OpenWatcom Free C/C++ Compiler]
* [http://sdcc.sourceforge.net/ Small Device Free C Compiler (SDCC)]
* [http://www.intel.com/cd/software/products/asmo-na/eng/compilers/index.htm Intel C/C++ Compiler]
* [http://www.digitalmars.com/d/2.0/dmd-windows.html Digital Mars D Compiler for Windows]

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

'''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.org ====
You can install '''MinGW''' yourself, by using an automatic downloader/installer or by downloading and unpacking the required packages by hand from [http://www.mingw.org mingw.org], here: [http://sourceforge.net/projects/mingw/files/].

Packages required (suggested) for MinGW/GCC v3.4.5:
* 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

Packages required (suggested) for MinGW/GCC v4.4.0:
* Compiler:
** gcc-full-4.4.0-mingw32-bin-2.tar.lzma
* 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 [/index.php/topic,10508.0.html] or [http://www.tdragon.net/recentgcc/].

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 [http://sourceforge.net/projects/tdm-gcc/files/TDM-MinGW%20Installer/1.908.0/tdm-mingw-1.908.0-4.4.1-2.exe/download Bundled Installer] and the [http://sourceforge.net/projects/tdm-gcc/files/TDM-MinGW%20Installer/1.908.0/tdm-mingw-1.908.0-webdl.exe/download On-Demand Installer] available via TDMs page referenced above for users who do not wish to download and install them manually.

=== Microsoft Visual C++ ===
The official Visual C++ website is at [http://msdn.microsoft.com/en-us/visualc/default.aspx http://msdn.microsoft.com/en-us/visualc/default.aspx].

Code::Blocks will work with any edition of Visual C++ since the 2003 edition (MSVC 7.1). The commercial editions of Visual Studio may require additional configuration in Code::Blocks to work correctly. You can also download the most recent "Express" edition of Visual C++ for free from [http://www.microsoft.com/express/vc/ microsoft.com/express/vc]. If you choose an "Express" edition of Visual C++, it is highly recommended that you also install Microsoft's Platform SDK in order to develop programs for Windows.

=== Borland C++ Compiler 5.5 ===
NOTE: ''At some point, you will be asked to register with Borland and fill out a survey. Registration is free.''

Go to [http://www.borland.com/products/downloads/download_cbuilder.html# Borland's downloads] and click on the link labeled "Compiler". After you accept the license agreement, you will be provided with download links to the setup file. (Borland was bought by, and now available at [http://edn.embarcadero.com/article/20633 Embarcadero].)

=== 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.next.codeblocks.org/index.php?title=User_documentation#Compilers

FortranProject plugin

2010-01-30T14:29:40Z

Briedis:

* Author: darmar
* Purpose: Add support for Fortran language
* Version: 0.3; State: beta
* Last update: 22. Jan. 2010
* Forum thread for discussion: [/index.php/topic,11033.0.html]
* Link for download: [http://darmar.vgtu.lt]
* Notes: Any support is welcome.
 
...back to [[Announcement for plugins/patches]]:

FortranProject plugin

2010-01-30T14:27:52Z

Briedis:

* Author: darmar
* Purpose: Add support for Fortran language
* Version: 0.3; State: beta
* Last update: 22. Jan. 2010
* Forum thread for discussion: [/index.php/topic,11033.0.html]
* Link for download: [http://darmar.vgtu.lt]
* Notes: Please have a look in the forum before using this lexer/template. Any support is welcome.
 
...back to [[Announcement for plugins/patches]]:

FortranProject plugin

2010-01-30T14:27:18Z

Briedis:

* Author: darmar
* Purpose: Add support for Fortran language
* Version: 0.3; State: beta
* Last update: 22. Jan. 2010
* Forum thread for discussion: [[/index.php/topic,11033.0.html]]
* Link for download: [[http://darmar.vgtu.lt]]
* Notes: Please have a look in the forum before using this lexer/template. Any support is welcome.
 
...back to [[Announcement for plugins/patches]]:

FortranProject plugin

2010-01-30T14:26:45Z

Briedis:

* Author: darmar
* Purpose: Add support for Fortran language
* Version: 0.3; State: beta
* Last update: 22. Jan. 2010
* Forum thread for discussion: [[/index.php/topic,11033.0.html]]
* Link for download: [[darmar.vgtu.lt]]
* Notes: Please have a look in the forum before using this lexer/template. Any support is welcome.
 
...back to [[Announcement for plugins/patches]]:

FortranProject plugin

2010-01-30T14:20:43Z

Briedis: Created page with '* Author: MyNameHere * Purpose: Add support for language XXX * Version: (not versioned); State: '''alpha''' - beta - stable * Last update: 10. Dec. 2005 * Forum thread for discus…'

* Author: MyNameHere
* Purpose: Add support for language XXX
* Version: (not versioned); State: '''alpha''' - beta - stable
* Last update: 10. Dec. 2005
* Forum thread for discussion: [[Link Into The Forum]]
* Link for download: [[Link Into The Forum]]
* Notes: Please have a look in the forum before using this lexer/template. Any support is welcome.
 
...back to [[Announcement for plugins/patches]]:

'''Please note: Edit this template and copy/paste the content into your lexer/template site in the WiKi to stay consistent with other developers. Don't forget to remove this note before ;-)'''

Announcement for plugins/patches

2010-01-30T14:18:45Z

Briedis: /* Plugin announcements */

=== HowTo announce a new plugin/patch or similar ===

''Please read carefully:''

This WiKi section is to announce:
* a new plugin that is '''not''' within the contrib folder of the SVN repository
* a patch that is '''not''' a bugfix or similar and/or will '''not''' be applied to the SVN repository (e.g. because it's very specific)
* a new lexer/template that is '''not''' completed or approved and/or will '''not''' be added to the SVN

If a plugin/patch/lexer/template is moved to the repository don't forget to remove it from here! This section is intended to '''collect''' the information about available plugins/patches/lexerers/templates in one place. So the announcement should be short and clear. It should (however) include at least the following content:
* Name of the plugin/patch/lexer/template and purpose 
* Version (state) and date of last update (or release in the first place) 
* Link to a thread (to be created) in the developers (plugin) forum for discussion of features, bugs, wishlist etc. 
* A link where the '''most up-to-date''' version can be downloaded (e.g. in the forum). 
The best way may be to copy the section from the '''template''' plugin/patch/lexer/template and update it with your information. This will ensure consistency in the best way! Read the article [[How to add another announcement]] to read how to change the WiKi accordingly.

=== Patch announcements ===

So far there are no new patches.

* [[Template for patch announcement]] (Read this before posting a new patch!)

=== Plugin announcements ===

These are the user-contributed plugins:

* [[Replace in Files]] (MortenMacFly)
* [[Tab versus Space]] (MortenMacFly)
* [[Edit Project]] (Killerbot)
* [[Matching Brace]] (Killerbot)
* [[Library Finder]] (byo)
* [[Environment Variables Editor]] (MortenMacFly)
* [[ThreadSearch]] (Dje)
* [[Code Snippets plugin]] (Artoj/Pecan)
* [[Interpreted Languages plugin]] (dmoore) ** OBSOLETE **
* [[Shell Extensions plugin]] (dmoore)
* [[Python plugin]] (dmoore)
* [[FindBrokenFiles scripted plugin]] (MortenMacFly)
* [[AutoVersioning]] (JGM)
* [[DragScroll plugin]]
* [[BrowseTracker plugin]]
* [[FortranProject plugin]]

* [[Template for plugin announcement]] (Read this before posting a new plugin!)

=== Lexer/Templates announcements ===

* [[Template for lexer/template announcement]] (Read this before posting a new lexer/template!)

Fortran Project plugin

2010-01-30T14:14:05Z

Briedis:

FortranProject plugin makes C::B more useful for Fortran programmers. It adds symbol browser and code completion for Fortran files. Source code and pre-build binaries can be downloaded from [http://darmar.vgtu.lt] .

Fortran Project plugin

2010-01-30T14:13:42Z

Briedis:

Fortran Project plugin

2010-01-30T14:11:59Z

Briedis: Created page with 'FortranProject plugin makes C::B more useful for Fortran programmers. It adds symbol browser and code completion for Fortran files. Source code and pre-build binaries can be down…'

Code::Blocks Plugins

2010-01-30T13:53:24Z

Briedis:

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

If you are developing plugins:
Surely you can work with plugin as you like, but here are some suggestions:
* Announce them in the plugin development board in the forums - including the (initial) source code at [/index.php/board,14.0.html].

OR

* Setup your own webpage (or use a file sharing platform) and post the link to the sources/binaries/svn access in the plugin development board in the forums at [/index.php/board,14.0.html].

OR

* Setup a repository, probably at BerliOS or SourceForge, post the link to the sources/binaries/svn access in the plugin development board in the forums at [/index.php/board,14.0.html]. Notice: This is very convenient as attachments in our forum might be deleted from time to time. So it is not safe to post source code in the forums.

THEN

# Enter the plugins description on this page.
# Announce the pugin '''[[Announcement_for_plugins/patches|here]]''' using '''[[Template_for_plugin_announcement|this]]''' template.

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

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

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

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

:Formats source code files with specific style.

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

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

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

'''[[Browse Tracker plugins|Browse Tracker]]'''

:Browse to previous source positions.

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

:Games in a integrated development environment? You bet.

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

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

:Installs and updates DevC++ DevPaks.

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

:Enables dragging and scrolling with mouse.

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

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

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

:Integrates third-party help files to the interface.

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

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

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

:Manages menu shortcuts.

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

:Queries the Koders webpage for keywords.

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

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

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

:Regular expressions testbed.

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

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

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

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

'''[[ThreadSearch]]'''

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

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

:Valgrind analysis tools integration.

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

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

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

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