0

I'm using Splint for a moderately large project. All is fine, but we are now trying to up the level from "weak" to "checks". Because we are checking files one by one, Splint complains about undefined functions. I seem to remember Splint had the option to analyse multiple files individually and then do a final analysis of all together (compile + link style).

I can't find any info on how to do this in the manual nor general Googling.

Is this possible?

Jongware
  • 22,200
  • 8
  • 54
  • 100
Toni Homedes i Saun
  • 638
  • 6
  • 15
  • Similar to [this question earlier today](http://stackoverflow.com/questions/30525472/static-analysis-tool-silence-tool-on-external-functions)? – Jongware May 29 '15 at 14:40
  • Thanks but no, Splint is a different tool from PC-lint, though they both do static checking for C programs. I have never used PC-lint (payware) but I'm guessing it's command line arguments and file's annotation will be entirely different to splint's. – Toni Homedes i Saun May 29 '15 at 15:16
  • I was referring to adding the proper *function prototypes*. Perhaps you are remembering wrong and that was the 'fix' - a static analyzer doesn't go as far as checking library paths. – Jongware May 30 '15 at 01:22
  • there needs to be a header file for each source file. each header file contains (amongst other things) the prototypes for the externally visible functions in the related source file. Then any file that wants to call a specific function that is in another file, must include the header that contains the prototype for that function. – user3629249 May 30 '15 at 05:36

0 Answers0