Dave Ohlsson

We use Cppcheck 2.20.0 (Windows version) to analyze our Qt project. The sources of our project are located under two directories: 1) C:/path/to/sources - contains the sources proper 2) C:/path/to/build - contains header files (ui_*.h) generated by Qt Cppcheck 2.20 has a useful warning: functionStatic. This warning, however, is generated for many of our ui_*.h headers: The member function 'Ui_FooDialog::retranslateUi' can be static. Since these headers are generated, the proper fix would be to instruct...

Thanks! I can see that version 2.18.2 had been available for 2 days when I posted my message, but I had not found it. Is there a page which lists the versions X.Y.Z with Z != 0?

Could anyone please tell when a version with this fix: https://trac.cppcheck.net/ticket/14064 is going to be available?

I noticed from https://trac.cppcheck.net/ticket/14064 that this is now fixed. Thank you! Do you know when the next version (which I presume will include this fix) will be available?

Cppcheck has a very useful option: --cppcheck-build-dir. According to --help, one advantage of this option is: faster analysis; Cppcheck will reuse the results if the hash for a file is unchanged. And indeed, when we run Cppcheck 2.14.2 on our whole project with --cppcheck-build-dir, the first time takes about 14 minutes, but if we run Cppcheck again with --cppcheck-build-dir without making any changes to the code to be analyzed, it now takes only about 1 minute. With Cppcheck 2.18.0, however, we...

My environment: Ubuntu 18.04 Cppcheck 2.4.1 FYI: I have experienced the following error in a header generated by Qt's tool uic: <error msg="There is an unknown macro here somewhere. Configuration is required. If QT_END_NAMESPACE is a macro then please configure it." verbose="There is an unknown macro here somewhere. Configuration is required. If QT_END_NAMESPACE is a macro then please configure it." id="unknownMacro" severity="error"></error> I solved the problem by adding the following two lines...

I have a very similar problem, and I just created this ticket: https://trac.cppcheck.net/ticket/10268#ticket Can you reproduce the problem described in that ticket?

My environment: Ubuntu 18.04 Cppcheck 2.4.1 * I use options --library=microsoft_atl and --library=windows The comments in the file below explain my problem. How can I get rid of "returnDanglingLifetime" in foo3()? I created file /usr/local/cppcheck/cfg/my_own_atl.cfg: <?xml version ="1.0"?> <def> <type-checks> <returnDanglingLifetime> <suppress>CComBSTR</suppress> </returnDanglingLifetime> </type-checks> </def> and I added option '--library=my_own_atl', but that did not help. Here is the file: #include...