CLion 2018.3 EAP: fixes for remote dev and more

Hi,

Please welcome a new CLion 2018.3 EAP (build 183.2940.13)!

As usual, a patch-update will be available shortly for those using the previous EAP build, and you can also use Toolbox app or snap packages (in the case of Ubuntu) to get this build. No license is required and the build is free to use, but it will expire within 30 days of the build date.

Download CLion 2018.3 EAP

Last week CLion 2018.3 Early Access Program started with the Initial Remote Development support. This week a new build is available and it addresses an issue with the symlinks used in header search paths (CPP-14211).

Talking about the header search paths, we’ve also fixed an issue with searching through the user and libraries header search paths:

  • #include <..> now looks for the header files in the libraries only.
  • #include ".." first looks in the user’s search path, then in the libraries

This fix actually means that the user header file shouldn’t hide a library header by mistake.

There are also several UI fixes across the whole IntelliJ platform, like for example drawing characters in Monospaced font was fixed (JRE-847).

Full release notes are available by the link.

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.3 EAP: fixes for remote dev and more

  1. Tano says:

    PLEASE PLEASE don’t break existing great things….CPP-14300 is very very silly and it’s a basic VCS feature, it worked perfectly until now since 2016.

  2. Andrew says:

    Is it planned to enable SSH remote debugging (without gdbserver) for local projects (or at least in the attach-to-process scenario) in 2018.3? I see that SSH remote debugging does work for remote projects, but it only works when the project is built and started with CLion. For projects that only build outside of CLion with a different build system, it appears that there is no option for SSH debugging. Only gdbserver-based remote debugging works (which requires transfer of gigabytes of symbols, making it useless).

    It seems like almost all of the work to support general-purpose SSH remote debugging is already done, so I’m assuming (maybe incorrectly) that it wouldn’t take much to support it for binaries built or started outside of CLion.

Leave a Reply

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