CLion 2016.3 Help

Requirements for CLion

On this page:

Hardware requirements

  • 2 GB free RAM
  • 1024x768 minimum screen resolution

System requirements

JRE 1.8 is bundled with distributions for all platforms. You don't need any Java to be installed on your machine in order to run CLion.

General requirements to start development with CLion

In general to develop in C/C++ with CLion you need:

  • CMake at least version 2.8.11 (if you do not want to use the bundled version), make
  • GCC/G++ or Clang, which in case of Windows means using toolchains: MinGW 3.* or MinGW - w64 3.*-5.* or Cygwin 1.7.32 (minimum required) up to 2.0.*.
  • GDB: at least 7.8 (if you do not want to use the bundled version)


System RequirementsInstallation
  • Windows 7.0 x64, 8.* x64
  • Cygwin x64 with installed packages: GCC/G++, make, gdb 7.8+
    MinGW with installed packages: GCC/G++ and make
  1. Download CLion from the Download page.
  2. Run the CLion-*.exe file that starts the Installation Wizard.
  3. Follow all steps suggested by the wizard. Pay special attention to the corresponding installation options.


System Requirements Installation
  • OS X 10.9.4+
  • GCC/G++ or Clang
  1. Download the CLion-*.dmg OS X Disk Image file from the Download page.
  2. Double-click the downloaded CLion-*.dmg OS X Disk Image file to mount it.
  3. Copy CLion to your Applications folder.


System RequirementsInstallation
  • OS Linux 64 bit
  • KDE, GNOME or Unity DE desktop
  • GCC/G++ or Clang
  1. Download the CLion-*.tar.gz file from the Download page.
  2. Unpack the CLion-*.tar.gz file to a different folder, if your current "Download" folder doesn't support file execution:
    tar xfz CLion-*.tar.gz <new_archive_folder>

    The recommended install location according to the filesystem hierarchy standard (FHS) is /opt. For example, it's possible to enter the following command:

    sudo tar xf CLion-*.tar.gz -C /opt/
  3. Switch to the bin directory:
    cd <new archive folder>/CLion-*/bin
    For example,
    cd opt/CLion-*/bin
  4. Run from the bin subdirectory.

See Also

Last modified: 29 March 2017