CLion 2018.1 EAP: CMake 3.10, Google Test with MSVC and C++ support improvements


The new CLion 2018.1 EAP, build 181.3986.16 is now available! Get it from our site or via JetBrains Toolbox App. Or, if you have the previous EAP build (181.3870.21) installed, you should soon get a notification in the IDE about a patch update.

Download CLion 2018.1 EAP

C++ support

In this build we’ve fixed an incorrect ‘Can’t resolve constructor’ error that happened in some cases when using = ... statement was used. It now works correctly in CLion:

Besides, this EAP build addresses several regressions:

  • Incorrect Can’t access class error (CPP-11393)
  • Incorrect Incompatible types in initializer error in some cases (CPP-11407)
  • Failed resolve of the structure’s member in case of typedef before the declaration (CPP-12046) and some other cases (CPP-12082)

Google Test with MSVC

CLion integrates with Google Test, Boost.Test and Catch frameworks. In this EAP build we’ve fixed an issue with Google Test output not handled correctly in case the Microsoft Visual C++ compiler toolchain is used.

CMake 3.10

Bundled CMake was updated to v3.10. As a side effect, minimum supported Cygwin version was set to 2.8.

That’s it! Full release notes are available by the link.

CLion 2018.1 EAP: quick overview

Here is a quick reminder of the main changes we’ve already made to CLion 2018.1 EAP:

  • Windows Subsystem for Linux support in CLion (with debug support and Valgrind Memcheck)
  • Support for if and switch with initializers from C++17
  • Code folding of the control statements
  • Ability to open single file/folder in CLion, load and unload CMake actions
  • Support for CMake Install
  • Support for Clang-Tidy options and configs
  • Objective-C/Objective-C++ support
  • Partial commits in Git
  • And many others changes and improvements

Feel free to share your feedback with us and suggest a new feature or report a problem in any way that’s convenient for you: this blog post (in comments), the issue tracker, or Twitter (@clion_ide).

Download CLion 2018.1 EAP

Your CLion Team
The Drive to Develop

This entry was posted in Announcement, Early Access Preview and tagged , , , , . Bookmark the permalink.

27 Responses to CLion 2018.1 EAP: CMake 3.10, Google Test with MSVC and C++ support improvements

  1. Tano says:

    Anastasia, another question pls: clang-tidy providedi in the package is the LLVM original or JetBrains fork? If fork, what are the differences? thanks

    • Anastasia Kazakova says:

      It’s LLVM original, we’ve contributed a few patches to the LLVM repo, however.

      • Tano says:

        Nice, I saw that you are using version 7 (which is in progress) instead of stable 5 or the 6 (which will be released this month).
        TBH I don’t understand LLVM, 6 is not released yet but in the clang-tidy documentation it’s written version 7.

  2. Tano says:

    “External tools” are project based or something?
    Because after the update, it seems that all are lost…:(((

  3. Henry says:

    Always get so excited about every single update. Only features I really want now is MSVC debugging (to help with writing Windows Python extensions) and CTest integration. Every other feature is just a nice addition and makes my CPP coding experience better.

    Great job at keeping me a happy CLion user.

  4. Christian Wieden says:

    Any chance this will be supported in CLion directly?

    Because it seeam very mature.

    Best Regards

  5. Tano says:

    Question: how do I copy Inspections settings from one project to another?
    I tried to export/import all settings but it doesn’t seem to work.

  6. Sergiy Yevtushenko says:

    Would be great to see support for Scons-based builds. There are several popular libraries for embedded C++ development which are based on scons –, xpcc, stm32plus, just to name a few.

  7. M.H. says:

    Hi, Why i cant debug with MVS compiler?! I get the following error. Debugging is not yet supported with Visual Studio

    • Anastasia Kazakova says:

      Indeed. Debugger for MSVC is not yet implemented (and we can’t integrate with MS debugger).

Leave a Reply to Anastasia Kazakova Cancel reply

Your email address will not be published. Required fields are marked *