Before starting with CLion, check this Quick Start Guide.
Configure and use different toolchains for different projects in CLion, or even inside one project for different configurations.
You can change CMake executable, Make, C and C++ compilers and debugger. Note that you can use either bundled or custom version of CMake and debugger executable.
Use Remote toolchains for building, running and debugging on a remote host.
On Windows use WSL/WSL2 toolchains. Compile, run, and debug Linux binaries while working on Windows. Test targets under Valgrind Memcheck to detect possible errors and leaks.
CLion supports and auto-detects Microsoft Visual C++ compiler from Visual Studio 2013, 2015 , 2017, and 2019.
An experimental debugger for Microsoft Visual C++ toolchain is available when turned on explicitly: call up the Maintenance dialog (Shift+Ctrl+Alt+/) | Experimental features, and select cidr.debugger.lldb.windows to control it. The debugger implemented by the JetBrains team on top of LLDB and is bundled into CLion. To enable bundled support for native visualizers, use Settings | Build, Execution, Deployment | Debugger Data Views | Enable NatVis renderers for LLDB.
All work in CLion is done within the context of a project, which serve as the basis for coding assistance, bulk refactoring, coding style consistency, and other smart features.
To start a completely new project, use
File | New Project... to
sample project. For C and C++ CLion will create a CMake project and pre-fill root
CMakeLists.txt with the necessary information.
To start with an existing project in CLion, select one of the following options:
New files can be added to the project by using the New menu. In the Project tree view, press Alt+Insert or select New in the context menu.