Dave Ohlsson - 2025-09-09

When we run Cppcheck automatically, we run it in two phases:
1. with --check-config (disables normal code analysis)
2. code analysis per se

The first time Cppcheck is run, phases 2 dominates:
1. ~ 1-2 minutes
2. ~ 13 minutes

In subsequent runs, however, phase 2 is very fast, thanks to caching (--cppcheck-build-dir). If changes to the source code are small, phase 1 now dominates:
1. ~ 1-2 minutes
2. ~ 5-10 seconds

Is there a way to cache the results of --check-config?