f286325cec
* MISRA: Allow printing of the suppressed rules to the console --show-suppressed-rules will print rules in the suppression rule list to the console sorted by rule number. * MISRA: Correct rule suppression for entire file scope The entire file scope suppression check was checking for the rule item list to be None instead of looking for None as an entry into the list. Correct this check and modify the documentation to explicitly state that an entry of None in the rule item list will set the scope for that suppression to be the entire file. * MISRA: Tests for checking per-file rule suppressions To run: ../../cppcheck --suppressions-list=suppressions.txt --dump misra-suppressions*-test.c python ../misra.py misra-suppressions*-test.c.dump There should be no violations reported * MISRA: Allow ignoring a prefix from file paths when suppression matching For environments that run cppcheck from the build system cppcheck may be passed a filename that is a complete path. Often this path will include a portion that is specific to the developer or to the environment where the project is located. The per-file suppression rules do filename matching based on the filename passed to cppcheck. To match any path information also has to be included into the suppressions file provided to cppcheck via the --suppressions-list= option. This limits the usefulness of the per-file based suppressions because it requires the suppression to be customized on a per instance basis. Add a option "--file-prefix" that allows a prefix to be excluded from the file path when doing the suppression filename matching. Example. Given the following structure: /test/path1/misra-suppressions1-test.c /test/path1/misra-suppressions2-test.c specifying --file-prefix /test/path1 will allow the use of misra-suppressions1-test.c and misra-suppressions2-test.c as filenames in the suppressions file without leading patch information but still match the suppression rule. * MISRA: Tests for --file-prefix option To run: ../../cppcheck --suppressions-list=suppressions.txt \ --dump misra-suppressions*-test.c \ path1/misra-suppressions*-test.c python ../misra.py misra-suppressions*-test.c.dump \ path1/misra-suppressions*-test.c There should be no violations reported |
||
---|---|---|
Cppcheck.xcodeproj | ||
addons | ||
cfg | ||
cli | ||
cmake | ||
cve-test-suite | ||
democlient | ||
externals | ||
gui | ||
htmlreport | ||
lib | ||
man | ||
platforms | ||
rules | ||
samples | ||
snap | ||
test | ||
tools | ||
triage | ||
win_installer | ||
.codacy.yml | ||
.gitignore | ||
.mailmap | ||
.travis.yml | ||
.travis_llvmcheck_suppressions | ||
.travis_suppressions | ||
AUTHORS | ||
CMakeLists.txt | ||
COPYING | ||
Makefile | ||
appveyor.yml | ||
benchmarks.txt | ||
build-pcre.txt | ||
build.bat | ||
console_common.pri | ||
cppcheck-errors.rng | ||
cppcheck.cbp | ||
cppcheck.cppcheck | ||
cppcheck.sln | ||
createrelease | ||
doxyfile | ||
generate_coverage_report | ||
philosophy.md | ||
readme.md | ||
readme.txt | ||
runastyle | ||
runastyle.bat | ||
webreport.sh |
readme.md
Cppcheck
Linux Build Status | Windows Build Status | Coverity Scan Build Status |
---|---|---|
Donations
If you find Cppcheck useful for you, feel free to make a donation.
About the name
The original name of this program was "C++check", but it was later changed to "Cppcheck".
Despite the name, Cppcheck is designed for both C and C++.
Manual
A manual is available online.
Compiling
Any C++11 compiler should work. For compilers with partial C++11 support it may work. If your compiler has the C++11 features that are available in Visual Studio 2013 / GCC 4.6 then it will work.
To build the GUI, you need Qt.
When building the command line tool, PCRE is optional. It is used if you build with rules.
There are multiple compilation choices:
- qmake - cross platform build tool
- cmake - cross platform build tool
- Windows: Visual Studio (VS 2010 and above)
- Windows: Qt Creator + mingw
- gnu make
- g++ 4.6 (or later)
- clang++
qmake
You can use the gui/gui.pro file to build the GUI.
cd gui
qmake
make
Visual Studio
Use the cppcheck.sln file. The file is configured for Visual Studio 2015, but the platform toolset can be changed easily to older or newer versions. The solution contains platform targets for both x86 and x64.
To compile with rules, select "Release-PCRE" or "Debug-PCRE" configuration. pcre.lib (pcre64.lib for x64 builds) and pcre.h are expected to be in /externals then.
Qt Creator + MinGW
The PCRE dll is needed to build the CLI. It can be downloaded here: http://software-download.name/pcre-library-windows/
GNU make
Simple, unoptimized build (no dependencies):
make
The recommended release build is:
make SRCDIR=build CFGDIR=cfg HAVE_RULES=yes CXXFLAGS="-O2 -DNDEBUG -Wall -Wno-sign-compare -Wno-unused-function"
Flags:
-
SRCDIR=build
Python is used to optimise cppcheck -
CFGDIR=cfg
Specify folder where .cfg files are found -
HAVE_RULES=yes
Enable rules (PCRE is required if this is used) -
CXXFLAGS="-O2 -DNDEBUG -Wall -Wno-sign-compare -Wno-unused-function"
Enables most compiler optimizations, disables cppcheck-internal debugging code and enables basic compiler warnings.
g++ (for experts)
If you just want to build Cppcheck without dependencies then you can use this command:
g++ -o cppcheck -std=c++11 -Iexternals/simplecpp -Iexternals/tinyxml -Ilib cli/*.cpp lib/*.cpp externals/simplecpp/simplecpp.cpp externals/tinyxml/*.cpp
If you want to use --rule
and --rule-file
then dependencies are needed:
g++ -o cppcheck -std=c++11 -lpcre -DHAVE_RULES -Ilib -Iexternals/simplecpp -Iexternals/tinyxml cli/*.cpp lib/*.cpp externals/simplecpp/simplecpp.cpp externals/tinyxml/*.cpp
MinGW
mingw32-make LDFLAGS=-lshlwapi
Other Compiler/IDE
- Create a empty project file / makefile.
- Add all cpp files in the cppcheck cli and lib folders to the project file / makefile.
- Add all cpp files in the externals folders to the project file / makefile.
- Compile.
Cross compiling Win32 (CLI) version of Cppcheck in Linux
sudo apt-get install mingw32
make CXX=i586-mingw32msvc-g++ LDFLAGS="-lshlwapi" RDYNAMIC=""
mv cppcheck cppcheck.exe