Daniel Marjamäki

Cppcheck-2.19.0

I am releasing cppcheck-2.19.0 if there will be some more fixes that should be released we can release 2.19.1

cppcheck.xml: 123MB It's not obvious that this is better. Are the results good?

It's quite usual that the compilation database will be slower, as all the include paths are provided all the headers will be included in the analysis. Sometimes it's better to provide the paths and sometimes it's better to provide compilation database (if missing macros cause problems for instance). I don't know what is better for you but I like that you try out both approaches..

It's quite usual that the compilation database will be slower, as all the include paths are provided all the headers will be included in the analysis. Sometimes it's better to provide the paths and sometimes it's better to provide compilation database (if missing macros cause problems for instance).

I would prefer it not be reverted but if it has to be reverted, I would like all other cmake changes put on pause until it gets merged in with a priority that it will be merged in the next release as I dont want to have to maintain a fork of cppcheck. that sounds reasonable to me.

No idea where we are at in terms of the CMake stuff. I don't actually understand the details of the changes nor your objections. But I think your objections was ignored too quickly when you were not able to participate. There was a sense of urgency as there is a lot of flux and therefore hard to keep the PR up-to-date. In my opinion it can be reverted there was suggestion about reimplementing the goodies in smaller PRs.

I would like to release soon. Customers are waiting for some of the bug fixes. What more do you feel we need to fix before the release? Imho getting latest simplecpp fixes into cppcheck should be pretty high prio. I can help out and I can ask ludvig, oleksandr and swasti to work on some tasks if there are suggestions..