You can run and debug your application or unit tests on a remote machine from the locally running CLion.
The CLion instance runs locally and synchronizes the source code to the remote machine, where it performs compilation using host compilers.
Like before, you can work on a macOS, Linux, or Windows desktop targeting a remote Linux machine connected via SSH, and the project source code should be located on the local machine. But starting with this 2021.1 EAP build, CLion can handle remote Makefile projects! There are still a few limitations for it, so read on before giving it a try.
They previously didn’t work together, as the full remote mode was only supported for CMake projects. Thank you! Initial support for Remote Makefile projectsĬLion now comes with support for Makefile projects with remote toolchains. If you endeavor to comply with MISRA C or MISRA C++ guidelines in your project, please let us know if you find the CLion checks helpful.
For example, given an if statement, it can tell you if both the true and false branches have been executed. It takes into account all the branches of each control structure. It showed how many lines/statements in your code (in %) were executed while running the tests.īut now, starting with this 2021.1 build, CLion can also show Branch Coverage. Previously, CLion was only able to measure Line Coverage (for GCC and gcov) and Statement Coverage ( LLVM and llvm-cov ).
When you measure your code coverage, there are several criteria and approaches to how to do it. Code coverage integration in CLion is available on all three platforms (Linux, macOS, and Windows) and with any toolchain (local, remote, or WSL), but only for CMake projects. If you ever ask yourself how well your code is covered with tests, code coverage tools may help answer the question. Note that if you are on macOS, there is a separate build for Apple Silicon (M1 chip).
Move execution point in disassembly view.