Difference between revisions of "MinGW installation"
m |
m |
||
| Line 4: | Line 4: | ||
A compiler suite is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler 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 specific compiler toolchain talked about in this page is a "MinGW" compiler. That means "Minimalist GCC for Windows." And "GCC" expands to "GNU Compiler Collection." There are many MinGW-based compiler suites, on this page we will concentrate on TDM-GCC. | A compiler suite is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler 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 specific compiler toolchain talked about in this page is a "MinGW" compiler. That means "Minimalist GCC for Windows." And "GCC" expands to "GNU Compiler Collection." There are many MinGW-based compiler suites, on this page we will concentrate on TDM-GCC. | ||
| + | |||
| + | For most MinGW-based compiler suites, having your toolchain in your PATH is important because it means that during development the compiler 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 Dynamic Link Libraries out of your toolchain folder 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 the won't have the compiler toolchain so there you provide the .dll files with your program. | ||
| + | |||
| + | TDM-GCC does not strictly follow the preceding however, it tends to statically link the required libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself. | ||
== TDM-GCC == | == TDM-GCC == | ||
| Line 18: | Line 22: | ||
[[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]] | [[Image:TDM_Inst_Dir.png]] [[Image:TDM_Inst_Options.png]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
Once you are ready, click Install to proceed. | Once you are ready, click Install to proceed. | ||
Revision as of 05:02, 26 December 2015
Overview
A compiler suite is what Code::Blocks uses to turn the code you type into it into numbers that the computer understands. As a compiler 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 specific compiler toolchain talked about in this page is a "MinGW" compiler. That means "Minimalist GCC for Windows." And "GCC" expands to "GNU Compiler Collection." There are many MinGW-based compiler suites, on this page we will concentrate on TDM-GCC.
For most MinGW-based compiler suites, having your toolchain in your PATH is important because it means that during development the compiler libraries will be accessible by default to your programs as you develop them and also makes it easier to use utilities such as 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 Dynamic Link Libraries out of your toolchain folder 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 the won't have the compiler toolchain so there you provide the .dll files with your program.
TDM-GCC does not strictly follow the preceding however, it tends to statically link the required libraries into your final executable. Which means that when you create your installer for your final program there are less files to include - they are built into your executable itself.
TDM-GCC
The fastest way to set up a working compiler is to install a recent GCC release targeting the MinGW compiler system from TDM-GCC. The Code::Blocks team recommends TDM builds of MinGW.
Installation
Download the on-demand installer and run it.
Go through the installation pages, the red arrows are all the default options which we will be keeping and the last blue arrow is to indicate that you will be putting TDM-GCC into your system's PATH.
Once you are ready, click Install to proceed.
Code::Blocks Configuration
Go to your Compiler settings:
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 choose the blue arrow ellipsis first then for each ellipsis you click on under "Program Files" you will already be in your TDM-GCC bin folder where the actual programs are.
Now, go to your Debugger settings:
Choose your default debugger (red arrow), and then fill in the Executable path for it as shown for TDM-GCC 32-bit (blue arrow).
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 compilers no matter the source - just follow the same basic procedure.
Alternative MinGW Compilers
MinGW-Builds ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.
Mingw-w64 - the parent project of MinGW-Builds, includes much more than is necessary - MinGW-Builds will usually suffice instead of the full works.
Development Tools
Normally you should not need many of these tools. ZIP is convenient, especially when building Code::Blocks itself, but other than that these tools only serve specialized purposes.
