Daniel Marjamäki
Daniel Marjamäki
> if you want Cppcheck to run on the whole project you will end up with 2 -I , and you wouldn't know which one to pick for which .c...
If you use a cppcheck build dir then the generated "filename.a1" files will contain all the error messages. You could extract all results from those. However the format of the...
I am very happy that I didn't scare you off with my comments. > Maybe we could just create a --cppcheck-output-dir option Sounds ok to me. So how do you...
> From a usage/user point of view, I don't see the point of just running the pre BUILD step alone (i.e. never running the file step). > For now, as...
That does not clarify it. Imagine a small project with 2 files source files: /foo/file.c /bar/file.c So if cppcheck will be executed like this: cppcheck --cppcheck-scope=file --cppcheck-output-folder=out/ /foo/file.c cppcheck --cppcheck-scope=file...
> when you run it again a second time when you run with -j2 it seems possible that both cppcheck will try to open the file for write at the...
there are CI failures you can look at.
It's quite a large PR. I would feel happier if split it up. I suggest that we only take the first "43d886bd70e0a8d6b7a59d38ec3f2f88a72ba2a1" to start with. I have a pretty good...
well I review it as a whole. I hope you can see the value in making it easy to review the PR. And if I have a review comment would...
The first sentence on that page says: "When the C preprocessor is used with the C, C++, or Objective-C compilers, it is integrated into the compiler and communicates a stream...