CLion 2020.1.1 Bug-fix Update

Anastasia Kazakova

Today we’re making available the first bug-fix for the recently released CLion 2020.1. CLion 2020.1.1 (build 201.7223.86) is now available for download from our website, via the Toolbox App, or via snap (for Ubuntu). A patch update will be available shortly.


Here are the main highlights:

  • Toolchains:
    • CLion 2020.1 introduced CUDA support. This update fixes the issue where CLion was not able to pick the non-default host compiler for CUDA.
      There are two different ways of specifying the host-compiler that NVCC should use during compilation.

      • For older CUDA projects using find_package(CUDA), the important CMake variables are CUDA_HOST_COMPILER and CUDA_NVCC_FLAGS.
      • For newer projects that specify CUDA explicitly as a language, CMake uses the variables CMAKE_CUDA_HOST_COMPILER and CMAKE_CUDA_FLAGS instead.

      For details check here.

    • The compiler is now detected correctly for Cygwin (CPP-19908).
    • CLion 2020.1.1 recognizes WSL Ubuntu20.04 distribution.
  • In Qt code: QStringLiteral and QByteArrayLiteral are now highlighted correctly (CPP-19916).
  • Clang tools:
    • A fix for a Clangd crash on C++20 code.
    • A fix for the Reformat Code action that caused an IDE freeze when ClangFormat was in use.
  • Code completion:
    • Completion was skipping parenthesis when Tab indentation was used (CPP-19902).
    • An issue with header name autocompletion has been fixed (CPP-19675).
    • A few issues with incorrect (CPP-10037) or redundant (CPP-19310) symbols completed were fixed.

The full release notes are available here. If you haven’t yet updated your CLion to 2020.1, now is a great time to do so!


Your CLion Team
The Drive to Develop

Comments below can no longer be edited.

9 Responses to CLion 2020.1.1 Bug-fix Update

  1. Ernst says:

    April 30, 2020

    hi team

    any idea why old parser could find an includes, but enabled clangd could not.
    I can send a logs if needed

  2. Ernst says:

    April 30, 2020

    please ignore – re-enable clangd mostly solved the problem

    • Anastasia Kazakova says:

      April 30, 2020

      Am I right it’s ok now?

  3. Tibor says:

    May 1, 2020

    Is there a way to know when this bugfix (linked below) will be in stable version (i.e. I can download it with toolbox or manually), is it possible to get this fixed build: 201.7376 some other way?


    I hoped this update would bring this fix too (because I need it for a project refactor), is there a workaround to set this different include directive options? maybe the internal defaults could be changed?

    Thank you for your time,

    • Anastasia Kazakova says:

      May 1, 2020

      This fix will join the 2020.1.2 in a few weeks.

  4. Taw says:

    May 7, 2020

    I wait also for 2020.1.2, this version is full of runtime exceptions, every hour I get one (different one). Of course I opened bugs for all, thanks.

    • Anastasia Kazakova says:

      May 7, 2020

      Is there any particular exception that breaks things? I mean if there is anything that stops working after the exception happens

  5. Johnny Depp says:

    May 14, 2020

    So, I updated fresh to 2020.1. And this message pops up:
    It seems you’re using ‘idea.config.path’ property to specify the location of the settings directory. In 2020.1, default locations of application directories were changed. For compatibility, the IDE picked the old location of plugins, but to avoid any ambiguity in the future (and to get rid of this warning) please set ‘idea.plugins.path’ property, too.

    This is kind of useless message. Where do I go to set ‘idea.plugins.path’? Shouldn’t that be in the message?


Subscribe for updates