New CLion 1.2 EAP (142.4859.12) is available

Anastasia Kazakova

The new Early Access build for CLion 1.2 (142.4859.12) is now available for trying. An update from the previous EAP build is also available.

Here are the most important changes and fixes addressed in this build. The most notable improvements are:

CMake commands in upper and lower case
The names of commands in CMake are case insensitive; the usual convention is to type the command names in uppercase. If you still prefer lower case for CMake commands or mixed style, use new setting in Editor | Code Style | CMake | Other to select the preferred variant:
cmake_case_settings
This setting affects the CMake commands completion: if you select ‘To lower’, then only lower case options will be suggested to you. And vice versa:
сmake_compl
In case of ‘Do not change’ the result depends on the case of the first symbol you’ve typed.
The setting also affects the result of code reformat (Ctrl+Alt+L on Windows/Linux, Alt+Cmd+L on OS X).

__LINE__
Macros __LINE__ is used widely in Unreal Engine 4 code and many other projects. New CLion EAP parses this macro definition correctly. (However, some issues are still left – CPP-4451)

LLDB on OS X version
The version of LLDB bundled into CLion on OS X is updated to 3.7 in this EAP.

Perforce
In case you are a Perforce user you’ll be glad to learn that CLion now allows you to shelve changes in Perforce from the UI. Shelve the changes by invoking Shelve in Perforce… action, browse perforce shelf and unshelve it anytime you want.

Download the EAP build now, give it a try and share your feedback!

Sincerely yours,
The CLion Team

Comments below can no longer be edited.

6 Responses to New CLion 1.2 EAP (142.4859.12) is available

  1. Anton says:

    September 19, 2015

    I understand that you have a development plan and every customer has his own list of the most critical issues. But please, focus on the debugger performance if possible. This is not just a useful feature, this is one of the key components of any IDE. I’m forced to switch to QtCreator/Eclipse every time I need to debug my code because CLion’s debugger integration is horribly slow.

    • Anastasia Kazakova says:

      September 19, 2015

      That’s exactly what we are doing now. Debugger performance is currently our top priority. Some improvements were already introduced in the EAP, like lazy GDB creation. Have you checked how it goes for you now?

      • Anton says:

        September 20, 2015

        Yes, I’ve checked the latest EAP. The debugger performance is better, but it still much slower than implementations of open-source analogs. Just try to expand any complex object (which has 15-20 member variables) in the variables view and do a few trace steps.

        • Anastasia Kazakova says:

          September 21, 2015

          Do you mean you compare separate GDB and CLion’s implementation with bundled GDB as a backend?

          • Anton says:

            September 21, 2015

            No, I compare CLion with Eclipse and QtCreator.

            • Anastasia Kazakova says:

              September 21, 2015

              Ah, ok, I see. Thanks. We are constantly working on debugger performance and the work is not over yet.

Subscribe

Subscribe for updates