> Maybe is there a way to provide our own cppcheck config file where we define
> what we need?
What a great idea, it's green!
https://github.com/geany/geany-plugins/pull/1197/checks
Thanks for the input, replacing the GTK library configuration with a custom one
with only a few macros, worked fi
Yeah, whatever works, I don't know cppcheck so I don't know all the options.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1196#issuecomment-1314989960
You are receiving this because you are subscribed to this thread.
Message ID:
Why not just a suppression file?
With a big comment `// fix Glib` :smiling_imp:
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1196#issuecomment-1314601231
You are receiving this because you are subscribed to this thread.
Message ID:
Maybe is there a way to provide our own cppcheck config file where we define
what we need?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1196#issuecomment-1314537984
You are receiving this because you are subscribed to this thread.
Message I
> However, I still don't understand why it always chokes on the argv array.
If you mean the one we talked about:
```
gchar **argv = NULL;
#ifndef G_OS_WIN32
/* run within shell so we can use pipes */
argv = g_new0(gchar *, 4);
argv[0] = g_strdup("/bin/sh");
Maybe merge #1201 and then sort out what still fails?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1196#issuecomment-1312860063
You are receiving this because you are subscribed to this thread.
Message ID:
Sigh, the old cppcheck version in the CI doesn't seem to respect the inline
suppressions :(.
In #1201 we switched the CI system to Ubuntu 20.04. Should I cherry-pick the
commit
https://github.com/geany/geany-plugins/pull/1201/commits/de6304c5d63a9b5902313695b56bc0b8d15f4510
into here?
--
Repl
> Either my testing is wrong or cppcheck ignores these macros.
cppcheck seems to test with different combinations of preprocessor macros. See
https://cppcheck.sourceforge.io/manual.html#preprocessor-settings. However, I
still don't understand why it always chokes on the `argv` array.
For now, I
