What Polyspace files should I archive along with source code, etc.?

At release time I archive all source code (*.cpp, *.h, etc.), make files (*.mak), final executable (*.exe), release notes, etc. into a code management system (e.g. ClearCase, git, etc.) I don't archive compiler intermediate files (*.bin, *.map, etc.) because they'd all be regenerated anyway. The idea is to create a complete but minimal snapshot of what I did that can be used to reconstruct the release from scratch.

What is the minimum file set I should archive for Bug Finder and Code Prover scripts? e.g. *.psprj, *.pscp, *.log, *.pdf (test reports from final run), etc.? That saves me from recreating the test setup and matches reports to version.

Answer 1

[Alexandre De Barros]

Hello,

if the context is "to reconstruct the release from scratch" then the files required to launch a verification, source and includes files excepted, are the project file (.psprj) and all the files that may be used by this project, like : a post-preprocessing-command, include files used by the option Include (-include), the constraint setup (DRS) file, custom coding rule definition files, etc...

The other files (the log, the reports...) are created during the verification.

Best regards,

Alexandre