CLion EAP, what’s next?

Anton Makeev

Hey folks,

In the following days after the public EAP announcement we received tons of feedback, questions and bug reports from you, and let us tell you, it feels great to let CLion out in the wild at last! Despite some issues, the launch went really well and we are eager to hear more from you as we gradually shape the IDE.

While listening to you, we were also busy fixing and investigating critical problems some ran into, these are mostly compatibility and toolchains issues. Also, we are working to make it easier to open existing non-CMake projects in CLion. The current plan is to publish the first update in a week or two.

And here is a short overview of the most requested things in our tracker:
* the unrivaled leaders are support for Makefiles and Qt projects.
* MinGW 64-bit support.
* Cross-compilation/cross-debug.
* Google Test support.
* Improved CMake configuration.

These are really important features, but we would like to clarify how our plans correlate, to avoid confusion.

Until version 1.0 we will continue improving and polishing CMake support, C++ parsing/resolving, performance and overall experience. And, while we understand that you’d want to open your existing projects in CLion, we’ll only think about additional build systems after 1.0. So if you want to try CLion, there is no point in waiting for Makefiles/Qt/you-name-it support for now, but we hope that the next EAP will help opening your existing non-CMake projects easily so you can then give the IDE a try.

As you may have guessed, cross-compilation/cross-debug is also out of scope of version 1.0.

We will add MinGW 64 support shortly, no doubt, and also improve compatibility with various toolchains that are already supported. You can expect more options and flexibility when using CMake projects and improved debugger stability and performance.

Another major area we want to cover in 1.0 is better integration of refactorings and CMake files. Currently, most of the changes in project structure (e.g adding new files, deleting or moving) need to be manually reflected in CMakeLists files. We’ll try to make everything as transparent as possible, so that refactorings such as Move/Extract Class/etc automatically update CMakeLists.

Please keep voting and suggesting new ideas – your feedback is invaluable to us. And, of course, feel free to ask if you have any questions.

The CLion Team

Comments below can no longer be edited.

14 Responses to CLion EAP, what’s next?

  1. Daniel Clausen says:

    September 17, 2014

    Many thanks for the great EAP version! It’s amazing how many features the first public EAP version already supports – especially in respect to code refactorings!

    Can you tell us where on the CLion roadmap we can expect support for unit testing frameworks like Google Test? It is mentioned in the “most requested” list but was not mentioned below.

    • Anton Makeev says:

      September 17, 2014

      Daniel, while already have Google Test support engine (available in AppCode), we can’t promise it will make it’s way into 1.0. It’s a big feature that require lot of attention from developers and we would prefer to focus on core features first.

  2. Jérôme says:

    September 18, 2014


    Is it meant to be a commercial product once reached the official release?


    • Anastasia Kazakova says:

      September 18, 2014


      Yes, CLion will be a commercial product built on our own open-source IntelliJ Platform. As all other JetBrains products, CLion will most likely have a variety of licensing options, including free and paid ones. For an example, see our AppCode buy page (

  3. Kelvin says:

    September 19, 2014

    Can we expect to see CLion (C/C++ Support) appear as a plugin on IntelliJ IDEA?

    • Anton Makeev says:

      September 19, 2014

      Kelvin, in future we consider this option, but definitely not in 1.0; it’s not an easy task and we don’t have resources at the moment.

  4. Stephen Kelly says:

    September 20, 2014

    There is currently a discussion about CMake generating a file with extra 
    information for IDEs to consume about the buildsystem:

    If you have any feedback about what would be useful in that file to allow 
    implementing some clion features, now is the time to bring it up.

    • Anton Makeev says:

      September 22, 2014

      Thanks, Stephen, will certainly do that – there are currently quite a few obstacles in CMake that make integration harder than it could be.

  5. wl.nicholas says:

    September 22, 2014

    C++ parsing/resolving and performance are both painful problems for me.

    • Anastasia Kazakova says:

      September 22, 2014

      Do you mean in CLion or in general?

  6. armin says:

    September 22, 2014

    support for some c/c++ web framework like kore and CppCMS would be awesome

    • Anton Makeev says:

      September 22, 2014

      Armin, most of the frameworks should be supported on API level out of the box. That means completion, navigation etc.
      We’ll consider more advanced support for selected frameworks sometime in future.

  7. Netanel says:

    October 14, 2014

    Please add support for remote projects like in PyCharm.


Subscribe for updates