CLion 2018.1.1 update is available

Anastasia Kazakova

CLion 2018.1.1, build 181.4445.84, a bug-fix update to the recently released major CLion update, is now available for download.

Please use the Check for updates action manually (Help | Check for Updates… on Windows/Linux or CLion | Check for Updates… on macOS) to receive the latest update if you are working with CLion 2018.1 or CLion 2018.1.1 EAP.

For future updates it will work automatically if you have Settings/Preferences | Appearance & Behavior | System Settings | Updates | Automatically check updates for… option enabled.

This update addresses:

  • C++ support: incorrect parsing and resolving of unordered_map, shared_ptr with a forward declaration and some more related issues (CPP-12079).
  • WSL issue, when the CMake project loading can take forever (CPP-12519). And a couple of other WSL-related issues.
  • GDB debugger: a fix for STL containers that were not updated during stepping, if the breakpoint was set before the containers were filled (CPP-7166, CPP-7574, CPP-7720).
  • Bundled CMake 3.10 is built with macOS 10.9 support to avoid incompatibility issues (CPP-12518).

Full release notes are available by the link. And to learn about our roadmap for CLion 2018.2 read this blog post.


Download CLion 2018.1.1

Your CLion Team

JetBrains
The Drive to Develop

Comments below can no longer be edited.

10 Responses to CLion 2018.1.1 update is available

  1. Kirill Sapozhnikov says:

    April 12, 2018

    After updating Kotlin/Native plugin these were added to all my projects’ cmake options:
    -D
    CMAKE_Kotlin_COMPILER=/home/skr/.konan/kotlin-native-linux-0.6.2/bin/konanc
    -D
    CMAKE_Kotlin_CINTEROP=/home/skr/.konan/kotlin-native-linux-0.6.2/bin/cinterop

    Why? What for?

  2. Kirill Sapozhnikov says:

    April 13, 2018

    CPP-12451 is just killing me in 2018.1.1. It started in 2018.1 RC2 and never happened in 2018.1.
    Had to roll back to 2018.1

    • Anastasia Kazakova says:

      April 14, 2018

      Could you please specify, if it started in 2018.1.1 or in 2018.1 RC2?

      • Kirill Sapozhnikov says:

        April 16, 2018

        In RC2

  3. Mario Frank says:

    April 18, 2018

    Dear CLion Team,
    I am using the current CLion version (just updated today to 2018.1.1) and have problems that are mentioned as fixed. Specifically, I use the pImpl pattern with a unique_ptr (std::unique_ptr p) where Private is forward declared in the header and defined in the cpp file. All pointer access attempts are marked as faulty, meaning, the members of Private defined in the cpp file are not resolved correctly. Also code completion for p-> yields no suggestion for members.

    For reference, I am using CMake 3.10.3 and clang 6.0.0.

    • Anastasia Kazakova says:

      April 18, 2018

      Could you please submit a full code sample to reproduce the issue to the issue tracker: https://youtrack.jetbrains.com/issues/CPP? We’ll check what’s going on there for you

      • Mario Frank says:

        April 18, 2018

        Hey Anastasia,

        this is really weird. I created a minimal example but the problem is not reproducible in this example. So for new files, everything is resolved correctly. But not in the files that were already existent before. Is there some cache or index that has to be cleared/rebuilt?

        • Mario Frank says:

          April 18, 2018

          Okay, I could reproduce it with the example files. It only happens when the pImpl’ed class is not in the global namespace. Posted the issue (CPP-12731)

          • Anastasia Kazakova says:

            April 18, 2018

            That’s the duplicate of https://youtrack.jetbrains.com/issue/CPP-12526 which is fixed, but not yet published. Fix version says Next CLion 2018.1.2 EAP, which is gonna be available shortly.

Subscribe

Subscribe for updates