third_party/exiv2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

cmake: export compile commands

Browse Source
This commit is contained in:
Luis Díaz Más 2022-02-05 11:25:51 +01:00
parent 87f0708bc7
commit 4746bb46af
2 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
cmake/mainSetup.cmake
View File

@ -8,6 +8,8 @@ include(CMakeDependentOption)
include(cmake/JoinPaths.cmake)
include(CTest)
set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)

8
doc/readme-pvs-studio.md
View File

@ -12,9 +12,10 @@ 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 with the following commands:
The analysis starts by running the following commands:
```bash
export PVS_LICENSE=~/.config/PVS-Studio/PVS-Studio.lic
@ -23,3 +24,8 @@ 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`.