Merged #1309 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1309#event-11990221578
You are receiving this because you are subscribed to this thread.
Message ID:
See also #1310 for an improved CI build with using the current "cppcheck"
version instead of the dated version from the CI runner image.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1309#issuecomment-1950041403
You are receiving this because
I tested the `--template=gcc` format locally with the latest cppcheck version
and it works.
The idea by using the specific "gcc" template was probably that the output can
be parsed by Geany out of the box using the default error message regex for
C/C++ files. But this is just a guess.
I
@eht16 pushed 1 commit.
146abc696b2d40ba6178328df4184794e40ce106 Add more custom macro definitions for
recent cppcheck versions
--
View it on GitHub:
https://github.com/geany/geany-plugins/pull/1309/files/fa2975229932c9b4eadbf0c7a249d4d8d541cdbb..146abc696b2d40ba6178328df4184794e40ce106
You
@eht16, To perhaps be more clear, I don't have a new enough cppcheck to test
this, but if it works for you approved although I'm not sure why the output
format needs to be forced to some specific format.
--
Reply to this email directly or view it on GitHub:
@elextr approved this pull request.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1309#pullrequestreview-1882616168
You are receiving this because you are subscribed to this thread.
Message ID:
I just RTFineM for cppcheck, but I don't use it, so thats why I referred it to
@b4n who wrote it originally or anybody else who has a new enough version that
`--template` is an official option, not UU (undocumented unofficial).
--
Reply to this email directly or view it on GitHub:
@elextr I couldn't resist to credit this great and very sophisticated change to
you as you already solved the mystery in
https://github.com/geany/geany-plugins/issues/1304#issuecomment-1912600670!
--
Reply to this email directly or view it on GitHub:
