See the full list of the currently supported checks on our Confluence page. In addition to Makefile changes, this EAP also brings: If options or option values passed to libtool and others are enclosed in single or double quotes, CLion’s parser currently can’t recognize them correctly.
There may be issues with parsing the options. Distcc is not yet supported ( CPP-19305).Projects with the automake macros are still not supported ( CPP-20126), so projects like curl or mono still can’t be loaded correctly. However, there are still a few small limitations we want to mention here: For example, here we open OpenZFS in CLion: Starting from this EAP build, if your Makefile project uses these tools you can still load it successfully in CLion and benefit from smart coding assistance.
CLION MAKEFILE PORTABLE
Libtool (and its alternative implementations like Dolt, slibtool, and jlibtool) is a tool that helps create portable compiled libraries by encapsulating both the platform-specific dependencies and the user interface.Ccache is a compiler cache that speeds up recompilation by caching previous compilations and detecting when the same compilation is being done again.If you’ve never used these tools before, here’s a brief overview: This made it impossible for CLion to correctly parse the make command’s output and load the project. Such tools made things worse by hiding the compilation flags and interfering with the Make’s output. Reading this list, you may notice that a large portion of projects remained unsupported because of their various wrappers. Support for projects with libtool and ccacheĪlong with the first iteration of Makefile projects support in CLion, we’ve also published a long list of projects that our team has tested this support on. One important thing to note here is that CLion doesn’t search project sub-directories for additional (nested) targets, only the top-level Makefile is analyzed. (Don’t forget to build with the debug symbols to be able to debug the application.) This means it’s now even easier to set up a Makefile project in CLion! Once the project is loaded you can build the configuration, and after pointing it to the created executable you can run and debug your application in CLion with no additional configuration required. Targets that end with unknown file extensions (e.g.d files). Targets that correspond to object files (.o files). Starting from this EAP build, the Run/Debug configurations are created automatically for the targets in the top-level Makefile when loading the project:Ĭonfigurations are not blindly created for all the targets. Run/Debug configurations in Makefile projectsĬLion has included support for Makefile projects since v2020.2. This action simply opens the Makefile settings – as quite often tuning the arguments or switching the toolchain helps. If loading the project fails, CLion now suggests a Check Settings quick-fix for all error messages in the log.
CLION MAKEFILE FREE
Meanwhile, feel free to vote for the corresponding request in our tracker. We’ve added some notifications to help users identify such cases:Ī UI notification about an unsupported toolchain is displayed when a remote toolchain is selected in Settings / Preferences | Build, Execution, Deployment | Makefile: Makefile project support is still in active development and there are still many things that are not yet supported or are simply not working correctly.
0 kommentar(er)
