948f822943
2.13: Update copyright year [ci skip] ( #5785 )
2023-12-20 21:41:58 +01:00
afcbe65e0b
GUI: Update translations ( #5784 )
2023-12-20 21:37:23 +01:00
5aa1710dd0
Fix #12071 (Add safety mode that makes cppcheck more strict about critical errors) ( #5777 )
2023-12-18 18:26:23 +01:00
2932ab7592
Revert "Fixed #12071 (suppressing critical error, no indication to user that analysis of file fails) ( #5771 )" ( #5775 )
...
This reverts commit 7c316fb76d
2023-12-17 19:13:14 +01:00
7c316fb76d
Fixed #12071 (suppressing critical error, no indication to user that analysis of file fails) ( #5771 )
2023-12-17 15:42:17 +01:00
1bdb7133e8
Fix #9684 New check: find unnecessary copy in range loop ( #5738 )
2023-12-08 16:58:43 +01:00
3fc62ce10b
fixed #12227 - properly load addons from `cppcheck.cfg` in GUI ( #5716 )
...
The GUI was asserting when addons were specified in the `cppcheck.cfg`
since we did not generate the info for them.
2023-12-06 19:45:30 +01:00
347b188726
gui/mainwindow.cpp: use picojson to generate JSON / updated picojson to latest dev version ( #5710 )
...
The lastest release of picojson does not support creation of JSONs, so
we need to switch to the current dev version.
2023-12-05 19:02:18 +01:00
3272a2bbe7
greatly improved `Settings::loadCppcheckCfg()` error handling ( #5712 )
...
This also fixes the issue that `cppcheck.cfg` is no longer being loaded
from executable path. That was introduced by #5704 .
2023-12-01 16:34:14 +01:00
4182f943aa
use more granular suppressions in selfcheck and prefer inline suppressions ( #5703 )
2023-12-01 15:59:01 +01:00
9dd729e9be
Fixed #12228 (GUI: Compliance report for Misra C 2012 is not working properly) ( #5709 )
2023-11-29 16:13:01 +01:00
f2461781fd
added `xml.h` wrapper for TinyXML2 / cleaned up suppressions of Clang compiler warnings ( #5700 )
2023-11-26 14:04:35 +01:00
86bb7c98e4
enabled and mitigated `readability-const-return-type` clang-tidy warnings ( #5644 )
2023-11-24 18:45:48 +01:00
3bafe164a3
enabled some clang-tidy warnings for non-GUI code ( #5679 )
...
There are some clang-tidy warnings which cannot properly handle the
extensions used in the Qt code so the produce lots of false positives
and were previously enabled. With clang-tidy now offering the
possibility to inherit the parent configuration we can enable these
across the project and simply disable them for the GUI code.
No additional warnings were found as they were already fixed in earlier
commits without enabling the checks in question.
2023-11-20 10:06:46 +01:00
92c089d4ad
fixed some "Parameter can be made pointer/reference to const" Rider warnings ( #5680 )
2023-11-20 07:23:45 +01:00
e47300016b
moved some classes/structs into anonymous namespace ( #5669 )
2023-11-16 15:49:41 +01:00
ae3f7bd800
Fixed #12187 (Windows build GUI with cmake) ( #5662 )
2023-11-15 16:56:46 +01:00
d3a8eb1ae2
config.h: improved and cleaned up some preprocessor checks ( #5663 )
2023-11-15 15:31:12 +01:00
bc174c502a
fixed #12145 - provided order of source files is not preserved ( #5625 )
2023-11-07 21:21:24 +01:00
ca6d1aafdb
moved `fileSettings` out of `Settings` ( #5608 )
...
Moved the `FileSettings` out of the `Settings` and pass them around
explicitly. They can never be specified at the same time and are used
exclusively. The code hasn't been fully adjusted to reflect this as this
is only the refactoring without any functional changes.
2023-11-03 23:24:04 +01:00
63e00ea918
fixed some "Variable can be made constexpr" Rider warnings ( #5615 )
2023-11-03 09:55:44 +01:00
e6d15b17ff
extracted `FileSettings` from `ImportProject` to `filesettings.h` ( #5604 )
2023-11-02 17:42:41 +01:00
dd627a2b1d
moved `ImportProject` out of `Settings` and only store `fileSettings` ( #5603 )
...
`ImportProject` is not needed outside of the command-line parsing so we
do not need it inside the `Settings` at all. We only use the
`fileSettings` in the executors.
2023-11-01 21:08:30 +01:00
bbaa7be901
Fix #12118 FP passedByValue for callbacks ( #5591 )
2023-10-31 12:06:31 +01:00
fdb3de708e
fixed #12042 - deprecated building with Qt5 / build with Qt6 in CI / updated latest Qt in CI to 6.5.3 ( #4957 )
...
Qt 5.15 will be EOL on May 26 so we should start switching away from it.
We already have issues with many of the previous versions and qmake on
legacy distros so we should cut that off.
I will add a Qt6 release build for Windows in another PR so it can be
tested. We should switch to it as the delivered build after the next
release and stop using Qt5 altogether in the CI in the release
afterwards (that would get rid of several build steps). We could leave
it so you could still try to build it but no longer support it so it is
up to the user to get it to work before removing it completely later on.
2023-10-26 14:55:59 +02:00
bfe19af6b2
fixed some "Declaration and assignment can be joined" Rider warnings ( #5569 )
2023-10-18 10:06:17 +02:00
85fe627c68
fixed some typos ( #5562 )
2023-10-17 18:32:07 +02:00
3811d01498
fixed "Redundant dereferencing and tasking address expression" Rider warnings ( #5563 )
2023-10-16 14:09:03 +02:00
5e89eb05a6
iwyu.yml: made `include-what-you-use` output more verbose / cleaned up includes ( #5540 )
2023-10-16 12:57:49 +02:00
ebb877adcc
gui/platforms.h: renamed `Platform` to `PlatformData` / Platform: removed unnecessary `cppcheck` namespace ( #5545 )
2023-10-13 16:02:04 +02:00
8c0d43d928
removed unnecessary encapsulation of severity enum and made it an `enum class` ( #5541 )
2023-10-12 11:58:39 +02:00
e4028f6820
fixed some "Declarator is never used" Rider warnings ( #5535 )
2023-10-09 18:06:35 +02:00
06b5ef1e4d
cleaned up includes based on include-what-you-use ( #5532 )
2023-10-09 10:07:20 +02:00
0f28f3e493
generate `AddonInfo` only once ( #4958 )
...
Currently the `AddonInfo` is generated and discarded on each addon
invocation. This leads to an unnecessary process invocation for each
addon on each file.
Also if an addon is completely broken we will still perform the whole
analysis only for it to be failed at the end so we should bail out early
if we know it doesn't work at all.
2023-10-08 21:28:57 +02:00
a22c181553
fixed "Redundant elaborated type specifier" Rider warnings ( #5517 )
2023-10-08 09:10:17 +02:00
723ba16eb6
fixed some "Parameter can be made pointer/reference to const" Rider warnings ( #5516 )
2023-10-06 09:57:16 +02:00
5a52fa80fb
refs #12022 - disallow multiple `--project` options ( #5499 )
2023-10-05 21:36:44 +02:00
a43b55a0ca
Improved addon execution errorhandling ( #5451 )
2023-09-20 10:40:57 +02:00
02b836baad
do not pass POD types by reference (based on clazy `function-args-by-value` check) ( #5388 )
2023-09-11 20:40:39 +02:00
639a4131c4
changed `bool_to_string()` to return `const char*` instead and use it in more cases ( #5385 )
2023-09-11 11:34:22 +02:00
bdbd886fc3
Add Japanese for Sep 6th 2023 [skip ci] ( #5422 )
...
Add Japanese translation only
2023-09-09 22:09:48 +02:00
91070ca794
utils.h: added `startsWith()` and started using it ( #5381 )
...
This makes the code much more readable. It also makes it less prone to
errors because we do not need to specify the length of the string to
match and the returnvalue is clear.
The code with the bad returnvalue check was never executed and I added a
test to show that.
2023-09-08 19:30:25 +02:00
4739ac8416
Update copyright year
2023-09-06 15:51:05 +02:00
6cfe33492f
GUI: run lupdate to update translations
2023-09-06 15:51:05 +02:00
3ac89468ea
Fix #11911 (GUI: provide suppressions when creating the compliance report) ( #5401 )
2023-09-04 10:58:48 +02:00
44c149e51b
Fix #11897 (Safety: show what checks are enabled/disabled) ( #5378 )
...
This primarily adds the corresponding report in the GUI that we have in
the command line already
2023-08-31 18:28:47 +02:00
276f017fbe
Partial fix for #11897 (Safety: show what checks are enabled/disabled) ( #5372 )
...
Example output on stdout:
```
$ ./cppcheck m1.cpp
Checking m1.cpp ...
Active checkers: 59/177
```
2023-08-29 12:00:52 +02:00
74ad7243ce
Partial fix #11892 (Safety: status message when checkers are skipped) ( #5368 )
2023-08-25 13:38:27 +02:00
e35d5d3ceb
Fix #11882 (add --premium=misra-c-2023 option) ( #5363 )
2023-08-23 10:28:02 +02:00
f91df64fec
fixed some Clazy `level0` warnings ( #5344 )
...
Regarding the "normalized signatures" see
https://github.com/KDE/clazy/blob/master/docs/checks/README-connect-not-normalized.md
and https://doc.qt.io/qt-6/qmetaobject.html#normalizedSignature .
2023-08-22 12:01:30 +02:00
Daniel Marjamäki
chrchr-github
Oliver Stöneberg
Tomo Dote