CLion 2017.3 EAP: code generation improvements, JUCE support and more

Hi,

CLion 2017.3 EAP (build 173.3622.10) is now available for download.

This build brings the following changes and improvements:

Download CLion 2017.3 EAP

Gutter icons to run main functions

To simplify the process of running your application in CLion, this EAP adds special icons to the left gutter for every main function in your project. It only requires a CMake target for the file containing this main function. The Run/Debug configuration is not mandatory, CLion will create it if missing:
modernize
Run, Debug and Run Valgrind Memcheck actions are available in the list when clicking on the icon.

Generate Definitions for templated functions

When function implementation is missing, you can easily create one via Generate Definitions (Ctrl+Shift+D on Linux/Windows, ⇧⌘D on macOS). This now works correctly for cases with templated functions:
modernize
There is still a problem with friend functions and templates, but it’s in our roadmap.

Develop audio applications with CLion

2017.3 version has already got some fixes for better JUCE support, a library widely used in the audio development. This build brings another portion of fixes for the incorrect code analysis issues.
And if you get a fresh JUCE 5.2 release with the latest Projucer, you can now find CLion/CMake exporter! The demo below shows how one can use CLion to develop/debug audio plugins:

We continue with parser improvements for JUCE. In the meantime, if you want to see more, come to our booth at Audio Developer Conference in London next week!

Support for Kotlin/Native in CLion

Kotlin/Native is a brand new technology that compiles Kotlin directly to machine code and produces executables that can run without a virtual machine. The list of currently supported target platforms includes Windows (x86_64), Linux, MacOS, iOS (arm64), Android (arm32 and arm64) and WebAssembly (wasm32). It uses an LLVM-based backend and supports Clang and LLDB. IDE support for Kotlin/Native is now available as plugins for CLion. If you are interested, check Kotlin blog for more details.
DOGyqhLWkAAHkSl.jpg-large

That’s it! Full release notes are available by the link.
Here is a quick reminder of the changes we’ve already made to CLion 2017.3 EAP:

Download CLion 2017.3 EAP

Your CLion Team
The Drive to Develop

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

12 Responses to CLion 2017.3 EAP: code generation improvements, JUCE support and more

  1. Cyr Sap says:

    Huh. Qt example is just Qt example or does it mean that we will see some surprises in 2017.3?

    • Anastasia Kazakova says:

      If you mean any specialities for Qt, nothing is planned for 2017.3. You still can use though Qt libs within your CMake project and benefit from CLion.

  2. Strus says:

    Do I assume properly that 2017.3 will have not only plugin for Kotlin/Native, but for “regular” Kotlin also, just like IntelliJ IDEA?

    • Anastasia Kazakova says:

      Regular Kotlin is not available in CLion, two plugins are the implementation details for Kotlin/Native support.

  3. Stephane says:

    This build seems to have broken the indexing (building symbols process) as it never completes and freezes the UI while doing its thing. Searching the forums, I did the recommended steps (increased heap allocation, invalidated cache…). The process will use as much memory I will give it, 12.5GB in my case and never completes.
    Uninstalling, deleting .c:\users\uname\CLion2017.3 folder and re-installing this EAP produces the same problem.
    Uninstalling, deleting .c:\users\uname\CLion2017.3 folder and re-installing 2017.2.3 works fine.
    I am using Windows 10, MinGW w64-3.3.
    My test project consist of 5 .c files and two include files, project size is not the issue.

  4. Roman says:

    Good news! Generate definition is probably the most used generator.

  5. Tarun Elankath says:

    Kotlin native samples use Gradle, but the Kotlin native support in this preview build appears to use CMake. What will be the officially recommended build tech for Kotlin native ?

    • Alexander Podkhalyuzin says:

      Currently CMake is necessary to get CLion working. I don’t think CMake is going to be standard option for Kotlin/Native, however we are going to simplify and generify Gradle and CMake scripts, so migration will be quite easy. One more possibility is Gradle plugin, which will be able to generate CMake script. What’s also going to be available in future is Gradle support in CLion.
      Kotlin/Native is preview technology and it’s hard to give you concrete answer to your question as it’s under design right now and we are experimenting with different build systems.

Leave a Reply

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