David Daniel

I will show the configuration I used in neovim. I am using nvim-lint through lazy. nvim-lint comes with predefined settings for Cppcheck, I remember having issues with why I modified those a little. return { 'mfussenegger/nvim-lint', config = function () local lint_parser = require ('lint.parser') local lint = require ('lint') table.insert (lint.linters.cppcheck.args, '--enable=all') table.insert (lint.linters.cppcheck.args, '--project=compile_commands.json') lint.linters.cppcheck.parser = lint_parser.from_pattern...

I was using Cppcheck within my editor (neovim) within my projects building with cross compile builds. I therefore setup compile_commands.json files (I am also using for clangd) and using this with Cppcheck. That way I got the analysis results within the editor. This feature is broken, after the last update I get an error message that --project does not work with single files. This used to work and now it doesn't anymore. That way I cannot use Cppcheck anymore within my editor, so I ditched the usage...