This new compiler setup can now be used in any new or existing projects. Now go back to the Settings -> Compiler dialog, select the new compiler under "Selected compiler", select the Toolchain executables and Program Files tabs, and change the Debugger selection to the new configuration e.g. Other settings (Debugger Type: GDB, etc.) can stay the same as for the Default configuration (unless you have some specific requirement, and you can always change them later). Under Executable path, select the corresponding gdb debugger for mingw64, e.g. In the popup window, enter the name for the new configuration - e.g. C:\tdm-gcc-64-5.1.0-2Įnter the following items, or click the Browse button beside each Program Files option, and browse from the compiler’s installation directory into the \bin folder, and select each item, as follows:ĭebugger: Set after configuring debugger - see belowĬlick on main menu Settings -> Debugger., select GDB/CDB debgger in the tree on the left, underneath which you should see the Default setting for the existing 32 bit debugger, and then click the Create Config button.
Modify the compiler’s installation directory to the directory where you installed MinGW64, e.g. You will need to update the toolchain for the compiler under the tab Toolchain executables. With the new compiler selected, review the compiler settings. "tdm64-gcc 64-bit Compiler" and click OK. "GNU GCC Compiler" (or the nearest equivalent if you are running a nightly build with a custom compiler), click Copy, then in the "Add new compiler" dialog enter the name for the new compiler, e.g. Under Selected Compiler, select your existing built-in compiler i.e. In 2015, Gabriel Aul, head of the Windows Insider Program, reported that "92.8% of systems with a BIOS age Compiler to open the Global compiler settings dialog.
0 kommentar(er)
