Source control is handled by github (), so you'll need to check out a copy.Various modules are disabled by default, such as the MAME interactive debugger, but can be enabled through arguments when building and may require additional MSYS2 packages to be installed.It allows easier editing of system environment variables on Windows.A compiler toolchain is what Code:: Blocks uses to turn the code you type into it into numbers that the computer understands.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. Min GW-Builds ➡ In, "Toolchains targeting Win32 or Win64," ➡ "Personal Builds," ➡ "mingw-builds," ➡ Version, ➡ Threading Model, ➡ Exception Model, ➡ Revision.
I will not go over this as it is clearly documented.
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 directory 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).
When you actually distribute your programs to other computers then you will copy the needed 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 files with your program.