Robert WAKIM
Robert WAKIM
> hi sorry for late reply. I am not convinced about the use case. > > I believe you should run cppcheck on all the files to get the whole...
> First of all I am trying to have an open mind and I want cppcheck to work for everybody. I do not intend to insult you but I don't...
> > Using the option with value "uniq" for two files > > I would suggest that two result files was created then? I fear the scenario when somebody checks...
Sorry Daniel, I had to focus on other topics. I've had a deeper look at the build folder, the feature is very nice, but create new problems. The Build folder...
> I am very happy that I didn't scare you off with my comments. No worries. > > > Maybe we could just create a --cppcheck-output-dir option > > Sounds...
> > 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...
> That does not clarify it. Imagine a small project with 2 files source files: hum sorry :( > > ``` > /foo/file.c > /bar/file.c > ``` > > So...
> > 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...