CLion 2016.3 Release Candidate

Posted on by Anastasia Kazakova

Hi everyone,

We are approaching the final steps towards the CLion 2016.3 release and today we are glad to announce Release Candidate build (163.7743.15).


Download CLion 2016.3 Release Candidate

If you develop in plain C, you’ll be glad to know that CLion now supports gcc atomic builtins, thus no false-positives are shown in the editor in that case.

Find the full list of fixes in the release notes.

We appreciate your feedback and comments, and if you find any bug at all, please file an issue in our tracker. Note, that this build doesn’t require an active subscription.

Your CLion Team

JetBrains
The Drive to Develop

Comments below can no longer be edited.

15 Responses to CLion 2016.3 Release Candidate

  1. Olof says:

    November 9, 2016

    Nice.

    Question though, does this mean no more major features planned for 2016.3?

    • Anastasia Kazakova says:

      November 9, 2016

      There are some that will make it way to 2016.3.x updates

      • Olof says:

        November 9, 2016

        Which ones can one hope for?

  2. Sebastian says:

    November 10, 2016

    Just curious, what happen to the disassemble view? Did I miss the announcement or has it been postponed too?

    • Anastasia Kazakova says:

      November 10, 2016

      We have to postponed it for later updates. You can track this ticket to get the notifications about changes: https://youtrack.jetbrains.com/issue/CPP-1748

      • Sebastian says:

        November 10, 2016

        Ok, I see. Anyway, great that the gcc atomics are supported now. That has annoyed me for a long time πŸ™‚

        Now I am really looking forward to see better preprocessor support that will be able to handle # and ## operators (e.g. https://youtrack.jetbrains.com/issue/CPP-2268).

        In the mean time I will enjoy using this great IDE. Thumbs up πŸ™‚

        • Anastasia Kazakova says:

          November 10, 2016

          Thanks. We need to think about this one, it seems it requires big rework. We’ll discuss when planning next versions anyway. Thank you for pointing!

  3. mbalabin says:

    November 14, 2016

    Are there any plans for fixing Release/Debug switching broken in EAP 163.6957.27? I have looked through the bugtracker and I could not even find an issue for that problem (I only saw some complaints as comments in Clion blog). Did I overlook the issue or it really does not exist yet?

    • Anastasia Kazakova says:

      November 14, 2016

      What exactly do you mean? Could you please specify the problem?

      • Nickolay Polyarniy says:

        November 15, 2016

        I think he is about this problem: https://youtrack.jetbrains.com/issue/CPP-8154

        • Anastasia Kazakova says:

          November 15, 2016

          Ah, I see. This is actually a behaviour by design at least for now. Please check more information here: https://blog.jetbrains.com/clion/2016/10/clion-2016-3-eap-cmake-overload-resolution/#cmake. So CLion now builds only one configuration at a time to save time and memory. In future we are planning to address the issue and give users the ability to build several configurations.

          • Nickolay Polyarniy says:

            November 15, 2016

            Thanks!

            In many workflows old behaviour was very useful: I use Release (in fact RelWithDebInfo) not for final building (we use Buildbot), but also to test features, because in most cases Debug is not very useful because of slow execution without release optimizations. But sometimes I need to fallback to Debug and so on. And I think this case is actual not only to me.

            “Switching in Settings” workaround works well enough – loading CMake project takes only five seconds for me.

            • Anastasia Kazakova says:

              November 15, 2016

              Thanks. We’ll consider the changes.

Subscribe

Subscribe for updates