xymp
/
exiv2
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
v0.27.3
main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9ca161d1e5'
${ noResults }
exiv2/doc/readme-pvs-studio.md

1.1 KiB
Raw Blame History

How to integrate PVS-Studio

We obtained a free license of PVS-Studio due to the open source nature of Exiv2.

CMake integration

To check a project configured with CMake, such as Exiv2, we need to generate the JSON compilation database.

# Under an already configured "buildXXX" directory
cd buildXXX
cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON ...

# Once the CMake configuration is done, we should obtain a output file 'compile_commands.json'
# NOTE: This option is enabled by default inside our CMake configuration (see cmake/mainSetup.cmake)

The analysis starts by running the following commands:

export PVS_LICENSE=~/.config/PVS-Studio/PVS-Studio.lic
pvs-studio-analyzer analyze -l $PVS_LICENSE -o pvsStudio.log -j8
plog-converter -a GA:1,2 -t tasklist pvsStudio.log -o pvsStudio.tasks
plog-converter -a GA:1,2 -t fullhtml pvsStudio.log -o pvsReportHtml
plog-converter -a GA:1,2 -d V1042 -t fullhtml pvsStudio.log -o pvsReportHtml

CI

The PVS username & key are configured as secrets in the security settings of the project. Then we make use of such secrets in the Github workflow named special_pvsStudio.