CLion 2019.1.1 Bug-fix Update

Hi,

With CLion 2019.1 released just a couple of weeks ago, it’s already time for the first bug-fix update. Build 191.6707.62 is now available to download from our website, via the Toolbox App, or via snap (for Ubuntu). A patch-update will be available shortly.

DOWNLOAD CLION

This update includes a few major fixes and enhancements:

  • This update fixes an annoying issue with the false redefinition errors shown by the clangd-based engine in several cases (CPP-15464).
  • For remote toolchains, the Cannot get compiler information error is now fixed (CPP-14477).
  • Move refactoring dialog (notifying about escalating the visibility) no longer hangs (CPP-15655).
  • In the newly added naming convention settings (Settings/Preferences | Editor | Code Style | C/C++ | Naming Convention), Upper_Snake_Case is now available as one of the options.
  • Bundled CMake was updated to v3.14.2.
  • Custom build targets and run/debug configuration are useful for compilation database projects, especially when using them to workaround Makefiles and other project models not natively supported in CLion. In this update we made the configuration process even more friendly – CLion now allows you to configure Custom Build Target right from the Run/Debug configuration settings dialog:
    custom_build_application

The full release notes are available here.

Want to know what’s next? See our roadmap for CLion 2019.2.

Your CLion Team
JetBrains
The Drive to Develop

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

9 Responses to CLion 2019.1.1 Bug-fix Update

  1. Alexander says:

    Time to time I try to use Clion for embedded develpment. Targeting to start JTAG debugging only using OpenOCD is an ugly solution. For example, to debug CPU code on Xilinx UltraScale+, it is ability to debug code on ARM Cortex A53, R5 and on the Soft CPU MicroBlaze. Xilinx provides SDK and hw_server that can be accessible via GDB interface (ports 3000-3002 for each types of CPU). Clion provide remote debuggin GDB but does not provide way to point startup script. For example, most of the time I need to run load command and continue after, but sometimes other initialization commands is needed (CPU reset, for example using monitor xxx commands). Currently, I can run GDB remote debug, stop board, run load command manually and continue debugging.

    BTW, currently Clion more usable for MicroBlaze development. microblaze-xilinx-elf triplet/target is not supported by LLVM/CLANG and cause clang parser fails on Qt Creator, so, there is no auto completion and there is no semantic highlighting. But, BareMetal integration on QtC at least 8 from 10 (Clion… hmm. 2-3, max 4 from 10) and CMake run options editor is a killer feature of QtC. But, interface of CMake file adding in Clion so beautiful.

    • Elmot says:

      OpenOCD is the very first step. Support for 3rd party gdbservers is a must, it is in our roadmap for 2019.2. GDB startup scripts and monitor reset are going to be implemented too.

      You can create several CMake profiles with customized environment, command line and make switches via Settings->Build, Execution, Deployment ->CMake. Is something important missing there?

  2. Taw says:

    Hi Anastasia, any news on CPP-15515? CMake editing is very painful because of this, at the moment I am using Eclipse for CMake files, CLion keeps trolling my indentation and it’s not usable.

    • Anastasia Kazakova says:

      We’ve managed to reproduce and we’ll discuss with the responsible developer before the end of the week to provide you some estimation on this.

  3. Kira Backes says:

    Thanks for the Upper_Snake_Case, although it is not the one we need.

    We need the style of Bjarne Stroustroup himself:

    struct User_repository {
    };

    User_repository user_repository;

    This means *only* the very first letter of Upper_snake_case would be upper case, and the rest would be lower case.

    We would be very grateful here if you added this, currently we need to deactivate the inspection 😉

    rgds, Kira

  4. Alexander says:

    It would be nice to have the ability to disable individual cmake profiles. I set up quite a few – different gcc / clang version and cmake build type combinations, plus clazy, etc…
    Re-running cmake each time for each profile slows everything down considerably. I only need the rarely used profiles maybe once every few months.

Leave a Reply

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