Toolchains For Eclipse Mac

Cmake-eclipse-helper is a very simple plugin that helps you setting up CMake projects for eclipse. You can even use it to switch between different toolchains within the same project. It fully relies on the built-in CMake generator and only adds a little spice to it:. It adds a CMake context menu where you can switch between build types and toolchains. You can setup project templates, so.

This tutorial will guide you through the process of installing, updating, and initial configuration of CLion on macOS.

Installation procedures

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

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

  1. Download the latest release or EAP version of CLion for macOS (earlier versions are available on the Previous CLion Releases page). Start inking not available.

  2. Open the downloaded CLion-*.dmg package and drag CLion to the Applications folder.

  3. Open the Applications folder and launch the CLion installer.

  4. If the security warning appears, agree to open the application:

  5. When you install CLion manually, the update checking is performed automatically by default (every time the IDE is ready to update, you will see a message in the status bar). To configure the update process, go to Preferences Appearance and Behaviour System Settings Updates and select the update channel:

    Click Check now to perform the checking right away. In case there are available updates according to the chosen channel, you will see a dialog like the following:

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.

Toolbox is a control panel that allows you to manage all JetBrains developer tools, including CLion, as well as your projects, from a single point of access. It enables you to maintain different versions of CLion, install updates and roll them back if needed. Toolbox remembers your JetBrains Account and uses it to automatically log in when you install and register new tools.

  1. Download Toolbox and launch the setup file.

  2. When the installation is complete, accept the JetBrains privacy policy and sign in to your JetBrains Account.

  3. Now you can choose which version of CLion to install:

  4. Toolbox shows the list of the installed versions:

  5. In the Settings dialog, configure the way of updating CLion:

    Note that in case of using Toolbox, the update process cannot be configured from within the IDE. The Preferences Appearance and Behaviour System Settings Updates dialog shows the following message:

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

Required tools

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

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

  1. Run the following command:

  2. When prompted to install command line developer tools, click the Install button:

    You can also choose to install the full package of Xcode, though it is not necessary for CLion.

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, see Switching Compilers.

Configure toolchains

Now you need to configure the toolchain to work with, which means choosing the CMake executable, the make and C/C++ compilers location, and the debugger. Navigate to Preferences Build, Execution, Deployment Toolchains and edit the default toolchain, or click to add a new one.

CMake, make, 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).

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

The detection of compilers and make fails if 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.


CLion for macOS comes with the bundled LLDB v 9.0 (the default debugger) and GDB v 8.0.1. You can also switch to a custom GDB (supported versions are 7.8.x-8.1.x). Select the debugger in Preferences Build, Execution, Deployment Toolchains:

Issues are possible when working with both bundled or custom 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):

A combination of GDB and Clang implies certain limitations to debugging your projects on macOS. See STL renderers for GDB on macOS for details and a workaround.

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

Further steps

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

Last modified: 20 February 2020

Before setting up your toolchain preferences, make sure that all the below software packages have already been downloaded and installed.

Refer to Installation Guide and CLion Quick start guide.

File Settings Build,Execution, Deployment Toolchains for Windows and Linux
CLion Preferences Build,Execution, Deployment Toolchains for macOS

Use this page as the reference when creating a toolchain. See also Toolchains for CMake projects.

Toolchains list

Here you can create or delete a toolchain and modify an existing one:

- use button to create a new toolchains configuration.
- use this button to delete a selected toolchain.
- use this button to move the selected toolchain up in the list.
- use this button to move the selected toolchain down in the list.

Toolchain name and type




Specify the toolchain name.

Type (Linux and macOS)

Choose from the drop down list:

  • System - the default value for a toolchain not to be used for remote development.

  • Remote Host - choose this option for Remote Development and provide the remote host credentials in the Credentials field.

Environment (Windows)

Select the preferred environment from the drop down list:




Choose this item to use MinGW. In the text field, specify the path to the MinGW home or use the one detected by CLion.


Choose this item to use Cygwin. In the text field, specify the path to the Cygwin home or use the one detected by CLion.

Visual Studio

Choose this item to use Microsoft Visual C++ compiler.

In the text field, specify the path to the Microsoft Visual Studio home (for example, C:Program Files (x86)Microsoft Visual Studio 14 .0). To do that, use one of the following ways:

  • Type the full path to the desired directory.

  • Click the button and select a path from the dialog that opens.

In the Architecture, Platform, and Version fields, specify the architecture (x86, amd64, x86_arm, amd64_arm, etc), type of a platform (store, uwp, onecore, or leave it blank) and version (Windows SDK name or leave it blank).


Choose this item to use the WSL toolset. Select the automatically detected path to WSL distribution from the drop down list.

Credentials - this field represents the SSH credentials that will be used to work with the selected WSL distribution. Click the button to configure credentials such as username, password and port. User name and password should be the same as you entered during the WSL set up procedure.

Remote Host

Choose this item for Remote Development. In the Credentials field, provide the remote host credentials.





Specify the path to CMake home directory, bundled or custom.


Specify the path to the Make utility or use the one detected by CMake.

C Compiler

Specify the path to the desired C compiler or use the one detected by CMake.

C++ compiler

Specify the path to the desired C++ compiler or use the one detected by CMake.





You can switch between the bundled GDB (currently v 8.0.1 for macOS, v 8.3 for Windows and Linux) and LLDB (version 9.0, only on macOS or Linux) or choose a custom GDB.
Note that custom LLDB is not currently supported.