CLion 2020.1 Release Candidate is Here

Anastasia Kazakova

Please welcome the Release Candidate for the upcoming CLion 2020.1!

To install CLion 2020.1 RC (build 201.6668.86), download it from the website, update from our Toolbox App, or use a snap package (for Ubuntu). Please note that to use CLion 2020.1 RC, you need to either have an active subscription or start a 30-day evaluation period. No patches are provided for this release candidate, but you can expect a patch to update the latest 2019.3 build to the 2020.1 release version.


The main highlights:

  • The Clangd-based engine received the following improvements:
    • A fix for the Clangd crash in the name hints.
    • Incorrect completion in multi-cursor mode is fixed (CPP-19680).
    • Concepts are working again in CLion with the Microsoft Visual C++ toolchain, after recently being broken.
  • CLion no longer fails if the Clang-cl compiler bitness doesn’t correspond to the toolchain bitness. Instead, the IDE passes the correct flags to build the proper binaries.
  • Unit testing improvements:
    • CLion’s automatic arguments for Boost.Test are no longer in conflict with the user’s arguments (CPP-17734).
    • The Google Test built-in test runner no longer incorrectly reports a certain failing test as succeeding (CPP-14927).
    • Google Test targets for v1.8.1+ are now correctly recognized by CLion as Google Test targets, and corresponding Run/Debug configurations are created automatically.

Follow the link to check out the full release notes.

We are now busy putting the final touches on the release, so please report any problems you encounter to our issue tracker. This way, we can sort them out before the final release (though, depending on their priority, the actual fixes might be postponed for later 2020.1.x bug-fix updates).

Your CLion team
The Drive to Develop

Comments below can no longer be edited.

12 Responses to CLion 2020.1 Release Candidate is Here

  1. Victor Sergienko says:

    April 4, 2020

    Would love to migrate, but have to stay on 2019.3.4 because of my pet IDEA-232215.

    • Anastasia Kazakova says:

      April 6, 2020

      We are trying to reproduce it on our side. For now, the root of the problem is not yet clear. Sorry.

      • Victor Sergienko says:

        April 6, 2020

        Thanks for a heads up!

  2. Taw says:

    April 7, 2020

    After a few days of playing with it, it seems stable, nice job.:)
    My general problem with IDEA(not with CLion!!!, CLion team is great) is that sometimes they did not test on XFCE, I found a lot of XFCE problems, they ask me to do some kind of stuff, test another java, but they could also install an Xubuntu in 10 min (or run from USB) and reproduce it very easily.
    Like this one: IDEA-234989 , the memory font is huge on XFCE

    • Anastasia Kazakova says:

      April 7, 2020

      Thank you, Taw.
      Unfortunately, sometimes we have to ask users to reproduce in particular environments. Thank you for your collaboration and I hope we’ll be able to get a fix soon.

  3. Benedict Schwind says:

    April 8, 2020

    Dear Jetbrains Team,
    I’m currently working on porting a Keil uVision Project to CLion & CMake.
    Its building, but some code insight features and other features are not working correctly.

    I thought I read you mention the support of the ARMCC(used by Keil) Toolchain, but the current EAP release only added support for the IAR Toolchain.

    Do you plan to add support for the ARMCC toolchain and if so when?

    • Anastasia Kazakova says:

      April 8, 2020

      We were planning to add support for armcc, but we don’t have an access to the toolchain/compiler yet.
      Maybe you can share some details of your work with us and we’ll try to assist?

      • Benedict Schwind says:

        April 14, 2020

        That’s good to hear!
        I’ll try to explain our current results:

        1. We are setting the ARMCC Compiler in a CMAKE_TOOLCHAIN_FILE
        2. The Compiler is detected by CMake, but CLion is throwing a warning (cmake output):

        “C:\Program Files\JetBrains\CLion 2020.1\bin\cmake\win\bin\cmake.exe” -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE:FILEPATH=C:\workspace\project-name\externals\CMakeToolchainLib\cmake\armcc_lpc17xx.cmake -G “CodeBlocks – MinGW Makefiles” C:\workspace\project-name
        — The C compiler identification is ARMCC 5.6.750
        — The ASM compiler identification is ARMCC
        — Found assembler: C:/Keil/ARM/ARMCC/bin/armcc.exe
        — Check for working C compiler: C:/Keil/ARM/ARMCC/bin/armcc.exe
        — Check for working C compiler: C:/Keil/ARM/ARMCC/bin/armcc.exe — works
        — Detecting C compiler ABI info
        — Detecting C compiler ABI info – done
        — Configuring done
        — Generating done
        — Build files have been written to: C:/workspace/project-name/cmake-build-debug-gnu-arm-mingw

        Problems were encountered while collecting compiler information:
        Fatal error: C3900U: Unrecognized option ‘-xc’.
        Fatal error: C3900U: Unrecognized option ‘-fpch-preprocess’.
        Fatal error: C3900U: Unrecognized option ‘-v’.
        Unexpected compiler output. This compiler might be unsupported.
        If you are using GCC/Clang, please report the bug in


        3. Regardless of the warning we were able to compile, link and flash within Clion.
        4. But we are experiencing errors with the code insight features, like resolving header files, functions and variables.
        By that I mean it works sometimes and sometimes it doesn’t
        We think this might be related to the warning mentioned above or a problem with our CMakeLists file.

        • Anastasia Kazakova says:

          April 14, 2020

          Yes, that means that CLion can’t get compiler info correctly, because the compiler is unsupported. When we support the compiler, the issue will be away.

    • elmot says:

      April 8, 2020

      Feel free to upvote and watch the issue CPP-19341

  4. Taw says:

    April 8, 2020

    Anastasia, short question: what is the difference between Reformat and Rearrange code in the commit dialog? Which one does the clang-format? (I have a .clang-format file)



Subscribe for updates