The time Cppcheck takes depends on how complex the code is. The more execution paths, variables, etc there are, the more analysis is made.In general the complexity grows much faster than the number of lines of code. Files with normal size are mostly much faster to analyse than big files.
OpenSuSe user can install Cppcheck using "1-click" installer - here
Recursively check the current folder. Print the progress on the screen and write errors in a file:
cppcheck . 2> err.txt
Recursively check ../myproject/ and print only most fatal errors:
cppcheck --quiet ../myproject/
Check only files one.cpp and two.cpp and give all information there is:
cppcheck -v -a -s one.cpp two.cpp
Check f.cpp and search include files from inc1/ and inc2/:
cppcheck -I inc1/ -I inc2/ f.cpp
Below is the example of tunning ccpcheck on Linux kernel source code 220.127.116.11
Output contains lots of warnings ....