CLion 2020.3.1 Bug-fix Update
In the beginning of December, we released CLion 2020.3 with lots of improvements to the debugging experience, enhanced unit testing integration, and support for MISRA checks and Qt code. And today we’ve got a CLion 2020.3.1 bug-fix update for you with the first set of notable fixes and enhancements.
Apple Silicon Support (M1 chip)
Great news for Apple fans! CLion 2020.3.1 now supports Apple Silicon. The previous CLion build was running on an M1 chip via Rosetta2 and the patch update to v2020.3.1 will keep that the same. A new build available from our website (download a separate installer for Apple Silicon) or via Toolbox App runs natively and also fixes an issue with launching LLDB on M1 (CPP-23065).
Fixes for remote development, project models, and code analysis
The most notable fixes in this update include:
For remote mode:
- Remote mode now works correctly with the remote machine that uses BusyBox (CPP-22753).
For Makefile projects:
- Configuring Makefile projects in some cases (like WSL) no longer takes an unexpectedly long time (CPP-23013).
- Fixed issues with loading QEMU Makefile-based source code (CPP-20618).
- CLion can now successfully import a Makefile project if there are multiple source files on a single command line (CPP-19895).
- Makefile projects that include assembly files can now be successfully loaded in CLion (CPP-19665).
For code analysis:
- Fixed the "Unable to execute Clang-tidy" error (CPP-23113).
- Other fixes for incorrect messages produced by the code analyzer.
- Addressed an issue with high memory consumption (CPP-21585).
Among other improvements in this build, we:
- Fixed duplication of Pull Request comments (IDEA-244965).
- Fixed the IDE to start correctly when checking out from GitHub using the JetBrains Toolbox browser extension (IDEA-253829).
- Fixed the Expand/Collapse All buttons in the TODO tool window (IDEA-254558).
- Fixed the problem preventing the IDE settings from being exported into a file (IDEA-252588).
You can find the full release notes here.
If you haven’t yet updated to v2020.3, now is definitely a good time to do so!
You are also welcome to read about our plans for 2021 and our roadmap for v2021.1 in this blog post.
Your CLion team
The Drive to Develop