CLion 2018.2.2 EAP

Hi,

CLion 2018.2.2 EAP (build 182.4129.15) is now available. Get it now from our Confluence page:

Download CLion 2018.2.2 EAP

Please, note that this EAP build requires an active subscription (or you can start a 30-day evaluation period). A patch-update will be available shortly (in case you are using CLion 2018.2.1).

This build includes the following improvements:

  • Performance improvement for CMake projects generation/loading.
  • When debugging on Windows, if you prefer to run the app in the separate console, not in the one integrated into CLion (which happens by default for GDB version 8.0 and higher), you can turn it on in Registry via the cidr.debugger.gdb.workaround.windows.forceExternalConsole setting.
  • Clangd-based language engine got a few improvements:
    • Correct handling of header search paths for non-CMake projects (CPP-13715).
    • Better diagnostic in case of unresolved includes (CPP-13498).
    • Performance optimization (CPP-13729).
  • Several issues related to enums were fixed in the CLion’s own language engine: CPP-7797, CPP-4957, CPP-6138

Full release notes are available here.

Your CLion Team

JetBrains
The Drive to Develop

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

6 Responses to CLion 2018.2.2 EAP

  1. Tano says:

    Anastasia, is there a strong reason for enabling clangd?
    I am satisfied without it, except of the known performance issues of CLion, of course.

    • Anastasia Kazakova says:

      Yes, there is a very strong reason – correct code errors and warnings displayed in the editor as quickly as possible. I agree there are situations where problems still exist, that’s why it’s still experimental, but for the majority of projects / users it works like a charm and makes the IDE experience much better.

      • Tano says:

        From what I see the number of errors that clangd shows is limited, that list contains only 5-6 items (-Wno-unused-variable,-Wno-shadow, …etc)
        Also I think it’s better to add these erros in the CMake flags, not in the CLion, so other team colleagues (that don’t use CLion) can benefit from them.

        And another question please, not related to this: how I can disable the “auto-load last project” in CLion? I want to have a list of project shown in CLion when starting it. I had it in the past and perhaps I checked some box and it stays like this now…Thanks.

        • Anastasia Kazakova says:

          For the second question: Settings/Preferences | Appearance & Behavior | System Settings | Startup/Shutdown | Reopen last project on startup

        • Anastasia Kazakova says:

          As for the first one, clang has a long list of checks available as warnings and errors. What we have in settings is just a tune to the clang default configuration to make it compatible with the CLion default inspections settings. This is done to avoid conflicts, as two language engines are working in parallel.
          We don’t think adding to CMake is a good idea, as usually developers don’t expect this from us. If your team configuration is different from CLion’s default one, then it’s better to tune settings in CLion for you.

Leave a Reply

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