CLion 1.0.2 update

Posted on by Anastasia Kazakova

Hi everyone,

The second update, CLion 1.0.2, is available for download. You’ll also get an automatic notification about this update right in the IDE, or can do CLion | Check for Updates manually.

A long list of fixes and improvements can be found in our tracker. Here are a few worth mentioning:

  • Since this version CLion supports Cygwin 2.0.0 and MinGW-w64 4.0 toolchains.
  • Create new C++ class dialog now will try to evaluate and suggest you the correct CMake targets name even if add_executable or add_library commands contain variables and not the direct target name. This still can fail for some complicated cases when the variable value is set in some other file or in non-top level constructs.
  • Since now you can select to declare function parameter as const while extracting parameter in CLion:
    declare_const_param
  • The getter/setter generation (Alt+Insert on Linux/Win; ⌘N on OS X) was improved greatly with this build. First, setters are available for union members now. Second, we’ve fixed the behavior for arrays – the correct getters are generated for one-dimensional arrays (can be also static); incorrect code that was generated before in all other cases was removed. By the way, for static members CLion now reasonably suggests static setters.
  • Getters are now inlined correctly (CPP-374).
  • Taking about debug, we’ve fixed a couple of annoying problems: one with command timed out on Windows while stopping on a breakpoint (CPP-840); other is about program execution stop under debug that didn’t work in some cases (CPP-3235).
  • A PTY related failure was fixed for the case when path to CLion contains ‘+’ symbol.

Check the update and let us know what you think.

Your CLion Team

Comments below can no longer be edited.

19 Responses to CLion 1.0.2 update

  1. Xie Fei says:

    May 19, 2015

    In 1.0.1, when I write “bool ” in a c file, CLion popups a message suggesting include stdbool.h, which is sweet. This does not in 1.0.2.

    • Anastasia Kazakova says:

      May 19, 2015

      Do you have in Settings Editor | General | Auto Import C/C++ auto-import popup switched on or off?

      • Xie Fei says:

        May 20, 2015

        Yes. Just checked, it is on. And I never customized it and it worked just fine in 1.0.1 before updated to 1.0.2.

        • Anastasia Kazakova says:

          May 20, 2015

          So just to be sure:
          – you have a C project/file
          – you haven’t set smth like C++11 flag in CMakeList.txt
          – and the auto import popup option is turned on for you
          am I correct?

          • Xie Fei says:

            May 20, 2015

            I did add “set(CMAKE_CXX_FLAGS “${CMAKE_CXX_FLAGS} -std=c++11″)” to CMakeList.txt and this is a mixed project, contains both c and c++ sources.

            • Anastasia Kazakova says:

              May 20, 2015

              Could you maybe share some sample project to reproduce? You can send it to clion-support at jetbrains.com.

  2. Chetan Naik says:

    May 20, 2015

    Does it allow us to create project using existing code which has make files ?

    Does it support make as well apart from CMAKE ?Is there a add on ?

    • Anastasia Kazakova says:

      May 20, 2015

      CLion currently supports only CMake. However you can do Import project from existing sources to create a CMake files for your project automatically with the help of CLion.

      As for Makefiles we are going to support them later (https://youtrack.jetbrains.com/issue/CPP-494).

  3. Kirito says:

    May 20, 2015

    Is there possible to integrate basic Objective-C support inside CLion (like making AppCode a plugin for CLion or opposite)?
    CMake supports Objective-C(++) code but sadly CLion do not.
    I have few Objective-C++ code to do some stuff on OS X for a platform-dependent implementation for some component of my software.

    • Anastasia Kazakova says:

      May 20, 2015

      We don’t have such plans. Though one can make a plugin to CLion (the API is open).
      Do you use Objective-C++ with Xcode project?

      • Kirito says:

        May 20, 2015

        With Xcode project generated with CMake, it just works and I could write code.
        But I wish that it will be possible that I can edit Objective-C++ file with CLion for better experience writing code.

        • Anastasia Kazakova says:

          May 20, 2015

          Thanks. We can consider it for later. But now it’s not in the roadmap since we have AppCode.

  4. francesco says:

    May 20, 2015

    Can you create the interface option to rename files and folders?

    • Anastasia Kazakova says:

      May 20, 2015

      There is a rename refactoring that can be applied to files and folders. You can find it with the shortcut or just in the right click context menu. Will it work for you?

      • francesco says:

        May 24, 2015

        Yes, I found it. But it’s buggy. On second time that I rename file with another name it says that file already exist.It doesn’t change anything on define.. Sorry for bad english

        • Anastasia Kazakova says:

          May 25, 2015

          Could you please check it with 1.0.3 update?

  5. Konstantin Isakov says:

    May 20, 2015

    I’ll ping about https://youtrack.jetbrains.com/issue/CPP-1100 once more and will continue to do so until it’s fixed and I can actually buy your product. C++ ain’t Java, preprocessor is different from imports. For now Qt Creator, for all of its quirks, still makes a better job handling it. CLion promises a fundamentally more correct and cleaner approach to code model, but falls short with its limiting assumptions. I believe those will be widened in the future and look forward to that moment; good luck, JetBrains!

    • Anastasia Kazakova says:

      May 20, 2015

      Thanks for pinging and reminding!

    • Yury V. Zaytsev says:

      May 21, 2015

      I this case I’ll go ahead and plug in an ad for https://youtrack.jetbrains.com/issue/CPP-3089 “Editor inserts bogus semicolons at the end of the current block when typing {“. Hey Internets, please vote for this issue! This is a bad bug in basic editing functionality that makes it a pain to use C++11, because when your code is trashed all the time when you define a variable, you get a bit irritated to say the least.

Subscribe

Subscribe for updates