CppCheck Report on vm140 Not Running

[Maarten Hoes]

Now that I think of it,

On Thu, Apr 22, 2021 at 2:51 PM Luke Benes <lukebenes at hotmail.com> wrote:

> > I'm more interested in running such tools locally
>
> Depending on the configuration, cppcheck scans can take 8+ hours to run.
>
>
That may be true when running cppcheck on the entire codebase, but I now
assume (please correct me if I'm wrong here) that this is not how people
use the tool. Instead, cppcheck is likely to be run on a single file which
has just been modified, which takes second(s) at most.


- Maarten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20210422/66aba84a/attachment.htm>