I was thinking a cppcheck cache in the way that ccache ( https://ccache.dev/ ) works for compliers. Where it would check the cppcheck argumanets used, the files location and timestamp or hash of a file and see if it needs to run again on it. I had attemped a bash version a few years back one weekend when my wife and kids where out of town. I just stumbbled appon it when I was cleaning up some diskspace. I went a head and posted my source to git hub a few minutes ago https://github.com/amishscientist/cppcheckcache I'm pretty sure it's in a broken state. I'm sure an interanl approuch could do far more than my naive approache could with fewer edge cases. Who knows it might even be a feature people are willing to kick start. I know I would be willing to put some money for the feature.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
that is more or less what --cppcheck-build-dir gives you. After preprocessing, the hash is compared. If the hash match the old result then the file is not rechecked.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for being so kind to me in your reposes. It has been sometime since I have gone through the manual. I should probably go through it again and see what other gems I have been missing out on for many years.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was thinking a cppcheck cache in the way that ccache ( https://ccache.dev/ ) works for compliers. Where it would check the cppcheck argumanets used, the files location and timestamp or hash of a file and see if it needs to run again on it. I had attemped a bash version a few years back one weekend when my wife and kids where out of town. I just stumbbled appon it when I was cleaning up some diskspace. I went a head and posted my source to git hub a few minutes ago https://github.com/amishscientist/cppcheckcache I'm pretty sure it's in a broken state. I'm sure an interanl approuch could do far more than my naive approache could with fewer edge cases. Who knows it might even be a feature people are willing to kick start. I know I would be willing to put some money for the feature.
that is more or less what
--cppcheck-build-dirgives you. After preprocessing, the hash is compared. If the hash match the old result then the file is not rechecked.Thanks for being so kind to me in your reposes. It has been sometime since I have gone through the manual. I should probably go through it again and see what other gems I have been missing out on for many years.