How do I tell lint where to find my compiler headers?
Use the -i option or the INCLUDE Environment Variable to designate a search path for files not found in the current directory.
How do I tell lint not to complain about my compiler headers?
Lint uses the label of "library" header to designate those headers over which a programmer has no control (such as compiler headers). By default all #includes from a foreign directory, or enclosed within < > , are considered "library." This can be modified through the use of the +libclass option, and further fine-tuned with the +/-libdir and +/-libh options. You can then use the -wlib and -elib options to control just those messages being emitted from library headers. Compiler options files distributed with PC-lint usually contain a -wlib(1) option which limits lint output from library headers to errors only (suppressing warning and informational messages).
How do I run PC-lint from inside Microsoft Visual Studio?
You can set up PC-lint as a tool. Follow the instructions from the appropriate env-vc?.lnt file. The latest files for Version 8.00 are available from Version 8.00 Patches
What is a library header?
Lint uses the designation "library" for those headers over which the programmer normally has no control -- such as compiler and third-party headers. Use the options +libclass, +/-libdir, and +/-libh to specify which headers are library. You can then use the options -wlib, -elib, and -elibsym to control lint messages caused by "library headers", without affecting the checking of your own code.