Restart CLion and check 'Settings' -> 'Build, Execution, Deployment' to make sure CLion has picked up the right versions of Cygwin, make and gdb.Add full path to Cygwin 'bin' directory to Windows Environment variables.Install Cygwin with GCC, G , GDB and CMake (the required versions).SHORT ANSWER (should be similar for MinGW too but I haven't tried it): Below is the short answer with steps I used to fix the issue. My OS is installed in C:\ drive and CLion 1.2.1 and Cygwin (64-bit) are installed in D:\ drive. It was working fine before I had updated my OS. Otherwise, when the checkbox is cleared, your custom values will overwrite the system ones.I ran into the same issue with CLion 1.2.1 (at the time of writing this answer) after updating Windows 10. Select the Include system environment variables checkbox link if you want the values you specify to be appended to system variables. Use, , and buttons to manage the list of custom variables. You can always click to type the required options in the editor window.Ĭlick to invoke the Environment Variables pane and select there the environment variables to be passed to CMake on the generation phase. For example, if the make generator is selected, the default value is -j, while for Microsoft Visual C this field is empty. If nothing is specified in this field, CLion uses the default settings, which depend on the selected environment. For example, if you specify -j 5 -clean-first -d -p, then -j 5 -clean-first will be processed by CMake, while -d -p will be passed to the build tool. Options from this field are passed to CMake during the build phase (see the description of the CMake build command for more information).įor the arguments to be used by the underlying build tool (make, Ninja, or another one), they should be preceded with. In this field, specify the options to be passed either to the build tool used by CMake or as command line parameters to CMake itself. Navigation actions like Navigate to file will not work for these files. If you select a subdirectory of the project root as the generation output, the IDE marks the files of that subdirectory as excluded from the project and considers them as non-project files. idea/workspace.xml and is not supposed to be shared. Leave this field empty to use the default location, which is cmake-build- under the project root. This path can be either absolute (for example, c:\CLion_Projects\My_Project\cmake-build-debug) or relative to the current project root (for example, cmake-build-debug). Specify here the desired location for the generated CMake files. You can also insert project path macros in this field by clicking : You can always press Shift Enter or click to type in the editor window, each option on a new line. In this field, specify additional CMake options, separated by spaces.įor example, here you can specify a custom CMake generator via -G. ![]() If nothing is selected, then CLion uses the toolchain that is currently set as default (the first one in the toolchains list).Īlternatively, you can set the generator via CMake options. This list consists of toolchains you created in the Toolchain settings dialog. Note that the Default option corresponds to the empty value of CMAKE_BUILD_TYPE.įrom this drop down list, select the desired toolchain. This field represents the name of the selected profile.įrom this drop down list, select the desired build type.īy default, in case this field has not been set manually, the type is Debug. Use this option to disable the profiles you don't need at the moment. If you disable a profile, it will not be included in CMake reload. ![]() Note: this list of CMake profiles determines the profiles available in the Run/Debug Configurations switcher and the list of resolve contexts. By default, profile is named according to the currently selected build type and toolchain.Ĭlick the button to delete the selected profile from the list.Ĭlick the button to create a copy of the selected profile. You can edit, delete, or add profiles here.Ĭlick the button to add a profile to the list.
0 Comments
Leave a Reply. |