-
Notifications
You must be signed in to change notification settings - Fork 13
java.lang.NullPointerException: Could not initialize cppcheck for project lib-ltc #98
Comments
Could you describe what you were doing and how to replicate it? |
Using the latest Eclipse 2019-09 with the plug-in from the Marketplace, I get this exception every-time when I run the cppcheck from the source file (pull-down menu). I can reproduce it on Linux Ubuntu as well. |
You didn't specify what version of cpccheck. Try to use cppcheck v1.83 |
Second experiment you can do is install different build of cppcheclipse, what happens when you install this variant of the plugin? |
MacOS : Cppcheck 1.89 |
Also an exception.
|
Can you share what source it is (it shouldn't matter), but still. Or can you export a project for me to try to replicate it? Do you have some CDT plugin on top of Eclipse when you do the C coding? Is the C project configured correctly (building as managed project, not some external makefile)? |
https://github.com/vanvught/rpidmx512
Yes, CDT latest release.
All projects are correctly configured with using an external makefile. |
So then no, that's just external makefile project, The 'Managed' is CDT's term: And CDT is not optional: If you want to use marketplace version of the plugin then any cppcheck above v1.83 will not work even when you will have the project as a proper CDT project. If you really want just rogue makefiles then you can just run cppcheck from them, no need for this plugin. |
On top of CDT because your project is baremetal (cool project btw), you might want to use GNU MCU Eclipse plugin as well, if you have Olimex jtag then you should be able to do interactive debuging through the GME plugin (it helps orchestrating OpenOCD and configuring the right switches for the toolchain so then it generates correct makefiles for you) |
I've got CDT (of course). I just corrected my comment. |
Advantage of a plug-in is that the output is referenced to the source code. |
Thanks!
I am not that eager with auto generated make files. I want to have full control on my own build process. |
I imported it into my Eclipse and run check on your lib-tcnet and I didn't got any exceptions, see attachment. |
I had the same problem on some eclipse projects. Other projects worked just fine. The difference is, that the error occurs only in projects, where the source code is just linked to the eclipse workspace. |
@AntonKrug, Figured out it has to do with the 'Is a workspace path' checkmark of the includes. When I enable this with a 'basic' test.cpp file i will get the same kind of error. It seems it is cppcheck unrelated, because it does not even get to the point it executes cppcheck. |
@AntonKrug i mean it is not an issue of cppcheck.exe itself. It is an issue of the cppcheclipse plugin. So i ques it could only be closed if it is fixed. |
The text was updated successfully, but these errors were encountered: