CLion 2019.3 EAP: Support for WSL 2 and LLDB 9

Posted on by Anastasia Kazakova

Hi,

A new CLion 2019.3 EAP (build 193.4099.17) is now available! Get it from our website, via the Toolbox App, or as a snap package (if you are using Ubuntu). A patch-update for those using the first EAP build will be available shortly.

DOWNLOAD CLION 2019.3 EAP

WSL 2

WSL (Windows Subsystem for Linux) is a compatibility layer for running Linux binary executables natively on Windows 10. CLion supports developing in a WSL environment, which is when you have your IDE launched on a Windows machine, but you target WSL/Linux in your development. This includes providing code assistance using the linked libraries from the WSL and, of course, building, running, debugging, and testing inside the WSL.

Not so long ago Microsoft introduced WSL v2. In a nutshell, its main difference from WSL v1 is that it has a lightweight virtual machine working inside with a Linux core on top. From the user’s perspective, things largely remain unchanged – check out the official Microsoft doc for more details. By the way, you can keep both WSL versions in parallel on your Windows machine.

From the perspective of CLion’s implementation, we had to support the new file system interaction protocol (interestingly, increasing the file system performance was the primary goal for WSL 2) and some networking configuration settings. Now, WSL 2 is enabled in CLion 2019.3 EAP. The great thing is that CLion’s configuration process is completely the same for WSL 1 and WSL 2!

A short configuration guide for you to start:

  1. WSL 2 installation instructions.
  2. See the official notes about placing files that your Linux apps will access in your Linux root file system, accessing network applications using an IP address, and not using localhost.
  3. Follow the CLion’s configuration instructions for WSL.

You are all set up now!
wsl

LLDB 9

The recent release of LLDB 9 is now bundled on macOS and Linux for debugging in CLion.

Faster startup

A few architectural changes in the IntelliJ Platform allowed to reduce startup times in all IDEs based on the platform. And CLion is no exception here! Check the details in this blog post.

The full release notes are available by the link.

Your CLion Team
JetBrains
The Drive to Develop

Comments below can no longer be edited.

9 Responses to CLion 2019.3 EAP: Support for WSL 2 and LLDB 9

  1. Taw says:

    October 3, 2019

    CPP-17509 did not make it into this release, unfortunetaly

    • Anastasia Kazakova says:

      October 4, 2019

      It’s in testing now. If all is fine, will be available next week.

      • Taw says:

        October 10, 2019

        I found a problem regarding this in 2013.2 also, please don’t release 2019.3 without this issue fixed. (CPP-17645)

        • Anastasia Kazakova says:

          October 10, 2019

          We’ll check it, thanks.

  2. Helge Penne says:

    October 7, 2019

    When are you planning to fix the LLDB bugs related to STL containers, like CPP-6671 etc.? This is an absolute must for LLDB users.

    • Anastasia Kazakova says:

      October 7, 2019

      We are currently on it. Hope to get LLDB pretty printers updated in one of the upcoming EAP build.

  3. Louis Thomas says:

    October 7, 2019

    Some of the base keymaps went away, which left me in the humorous situation where nothing but letters worked – ctrl-z, backspace, delete, and the arrow keys had no effect. Don’t make a mistake! 🙂

    Are they coming back, or should plan on rebuilding my keymap with its small handful of changes on one of the remaining keymaps (which was probably overdue anyway)?

    Also, has anyone else complained yet about the fact that the 2019.3 EAP (all three versions) spends 30 seconds resynchronizing VCS every time you type anything? Having to wait 30s for the gutter diff to appear, and another 30s before every commit has made the EAPs not really usable. I’d be happy to upvote or file a bug.

  4. Roman says:

    October 8, 2019

    Is it possible to disable internal parser for navigation and code completion? Both Clangd and Clion consume lots of memory. So I want to try how it will perform if I have only Clangd…

Subscribe

Subscribe for updates