After adding some configurations to the windows.cfg file i rescanned a project.
Although i have added noreturn configuration for functions that were reported to have none previously, cppcheck still reported the same function as having no noreturn configuration.
After verifying that the correct settings are used i saw that the according files for which the new configuration is relevant were not updated in the cppcheck-build-dir.
So i guess when using cppcheck-build-dir changes in the configuration files are ignored until a sourcefile is changed and rescanned. As a user i think i wouldn't expect that i have to delete the cppcheck-build-dir content when enhancing the library for my project.
Last edit: versat 2018-01-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After adding some configurations to the windows.cfg file i rescanned a project.
Although i have added noreturn configuration for functions that were reported to have none previously, cppcheck still reported the same function as having no noreturn configuration.
After verifying that the correct settings are used i saw that the according files for which the new configuration is relevant were not updated in the cppcheck-build-dir.
So i guess when using cppcheck-build-dir changes in the configuration files are ignored until a sourcefile is changed and rescanned. As a user i think i wouldn't expect that i have to delete the cppcheck-build-dir content when enhancing the library for my project.
Last edit: versat 2018-01-09
I agree. somehow that should be considered also.
Feel free to create a ticket. I would say that this is a "defect".
Ok, thank you.
I created ticket https://trac.cppcheck.net/ticket/8328