CLion 1.2.2 Update is Out

Hi,

While we’ve already started working on features planned for CLion 1.5, today we are happy to announce a bug-fix update, CLion 1.2.2. Download the newest version from the official site.

CLion1.2.2

Have you noticed our new brand?! Read more about it in our company blog.

Talking about new features and fixes, we’d like to highlight:

Search Everywhere
Search Everywhere is now more powerful. In addition to IDE settings and actions, you can find C and C++ project symbols there as well:
search_everywhere

CMake
As far as CMake support goes:

  • We’ve added the latest CMake 3.4 to the list of supported versions.
  • Fixed the problem when build output directory was set to “.” and the problem with project dir, content dir or build output path saved in a platform-dependent way.
  • In addition to the new CMake formatter option for forcing upper/lower case for CMake commands introduced in CLion 1.2, this update brings ‘Align when multiline’ setting to take control over several arguments alignment for multiline cases:
    cmake_align

Debugger performance
We’ve implemented more debugger performance optimizations for working with the GDB backend, especially the rendering of huge C arrays and STL collections. This update also includes a fix for a timeout that was happening during the ‘set value debugger’ operation.

And more

Find the complete release notes list at this link.

Yours as always,
The CLion Team

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

8 Responses to CLion 1.2.2 Update is Out

  1. Rich Eakin says:

    Just wanted to say thanks for continuing to make CLion a more and more powerful C++ idea. I’ve been loving its refactoring features, and especially debugging with LLDB. Keep up the great work!

  2. Grigoriy says:

    The CLion update is great,
    but the new design is objectionable…
    Website is just confusing and difficult to navigate. Application icons became meaningless and difficult to distinguish. Never expected that from Jetbrains.

  3. lmiguel says:

    Hello,
    I have this problem when using OpenCV. The next line is erroneously treated like a error of syntax:

    Mat window,
    char a1 = window.at<unsigned char>(1, 1);

    but this is correct:

    Mat window,
    char a1 = window.at<char>(1, 1);

    I think the problem is because the space in between “<unsigned char>”.

Leave a Reply

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