This tutorial will guide you through the process of installing, updating, and initial configuration of CLion on macOS.
Cross-platform here means you run them on your PC or Mac, but the result can be only run under the target environment, which is ARM MCU in our case. There are a number of toolchains for ARM, for instance, Clang and GCC are free and both supported by CLion, and there are a number of other compilers (Keil, IAR, Raisonance, etc). I'm on Clion 2019.2 Mac OS X 10.14.6. Igorbulakh1987 Created September 18, 2019 00:04. Comment actions Permalink. But how to reset Clion? May be it will work. I am ready to try any method to fix this. Igorbulakh1987 Created September 18, 2019 06:31. Comment actions Permalink. Finally I did it.
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.
Download the latest release or EAP version of CLion for macOS (earlier versions are available on the Previous CLion Releases page).
Open the downloaded CLion-*.dmg package and drag CLion to the Applications folder.
Open the Applications folder and launch the CLion installer.
If the security warning appears, agree to open the application:
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:
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.
Download Toolbox and launch the setup file.
Now you can choose which version of CLion to install:
Toolbox shows the list of the installed versions:
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:
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 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.
Run the following command:
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
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.
As an alternative, you can separately install compilers and make, and then provide the paths in Preferences Build, Execution, Deployment Toolchains.
Note that you can use multiple compilers for the needs of your project, see Switching Compilers.
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 10.0.1 (the default debugger) and GDB v 10.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 ):
Note that enabling this option is not equivalent to setting
set startup-with-shell off in your .gdbinit script.
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.
Now that you have CLion installed and configured, you may find the following articles useful for further steps of the development: