Cppcheck doesn't provide a proper report when one of the files in the check list is broken.
If we run the analysis on a per-file basis, then Cppcheck will be able report at least defects
from valid source files.
* Update check tools to the latest versions
* Use language standard when exporting defines to check tools
* Buffer Cppcheck output to detect multiline messages
* Add new test for PIO Check
* Pass include paths to Clang-Tidy as individual compiler arguments
Clang-tidy doesn't support response files which can exceed command
length limitations on Windows
* Simplify tests for PIO Check
* Update history
* Sync changelog
* Add new option --skip-packages for check command
Check tools might fail if they're not able to preprocess source
files, for example, Cppcheck uses a custom preprocessor that is
not able to parse complex preprocessor code in zephyr framework).
Instead user can specify this option to skip headers included from
packages and only check project sources.
* Fix toolchain built-in include paths order
C++ and fixed directories should have higher priority
* Refactor check feature
The main purpose is to prepare a more comprehensive build environment.
It's crucial for cppcheck to be able to check complex frameworks like
zephyr, esp-idf, etc. Also detect a special case when cppcheck fails to check
the entire project (e.g. a syntax error due to custom preprocessor)
* Add new test for check feature
Tests ststm32 platform all tools and the main frameworks
* Update check tools to the latest available versions
* Test check tools and Zephyr framework only with Python 3
* Tidy up code
* Add history entry
* Add initial support for PVS-Studio check tool
* Enable all available PVS-Studio analyzers by default
* Add tests for PVS-Studio check tool
* Improve handling check tool extra flags that contain colon symbol
Ivan Kravets