Tutorial: Configure CLion on macOS

Before you start CLionLion installation on macOS, make sure your machine meets the hardware requirements, and the version of your macOS is 10.9.4+.

note

You can always have multiple instances of CLion installed on the same OS, including both release and EAP builds.

tip

Alternatively, you can install CLion via the Homebrew package manager: brew cask install clion. However, this option is unofficial, as the CLion team is not involved in its maintenance or support.

After the installation or upgrade, you will be prompted to import, inherit, or create new settings for the IDE.

CLion needs to be provided with C and C++ compilers. These tools may be pre-installed on your system: check it in Settings | Build, Execution, Deployment | Toolchains - the compiler and make detection should perform successfully.

If your system does not have working installations of compilers, the simplest solution is to install Xcode command line developer tools.

With Xcode command line tools, you get the Clang compiler installed by default. To check the compiler presence and its version, run clang --version.

Command line tools may not update automatically along with the system or Xcode update. This may cause error messages like invalid active developer path during project loading in CLion. To fix this, run the same xcode-select --install command, and the tools will be updated accordingly.

Note that you can use multiple compilers for the needs of your project, refer to Compilers.

Now you need to configure the toolchain to work with, which means choosing the CMake executable, the build tool, the C/C++ compilers, and the debugger.

Navigate to Settings | Build, Execution, Deployment | Toolchains and edit the default toolchain, or click to add a new one.

tip

See Toolchains for general information.

For more information about Remote Host toolchains, refer to Remote with local sources. If you are working with a Docker container, refer to Docker toolchain.

CMake, build tool, and compilers

In the CMake field, specify the CMake binary that you want to use. You may stick to the bundled CMake, or use your custom CMake executable (see the minimum supported version in Software requirements).

By default, CLion will use bundled Ninja as the Build Tool. You can specify another build tool of your choice, for example, make.

The chosen CMake attempts to detect the compilers considering the packages installed on your system. If detection succeeds, the C Compiler and C++ Compiler fields are filled automatically:

tip

The detection of compilers fails when CMake cannot locate the appropriate tools. This may happen, for instance, if you installed them separately without the Xcode developer tools. In this case, you need to provide the actual paths manually.

Debugger

CLion for macOS comes with the bundled LLDB v 19.1.3, which is the default debugger. You can also switch to a custom GDB (supported versions are 7.8.x-14.1).

Select the debugger in Settings | Build, Execution, Deployment | Toolchains:

Issues are possible when working with GDB on macOS. To improve the behavior, enable the cidr.debugger.gdb.workaround.macOS.startupWithShell option in Registry (select Help | Find Action from the main menu and type Registry):

note

A combination of GDB and Clang implies certain limitations to debugging your projects on macOS. For more information and a workaround, refer to STL renderers for GDB on macOS.

Note that enabling this option is not equivalent to setting set startup-with-shell off in your .gdbinit script.

Now that you have CLion installed and configured, you may find the following articles useful for further steps of the development:

• Project formats supported in CLion

• Quick CMake tutorial

• Toolchains

• Compilers

• Run/Debug configurations