| --help |
display this help |
| --version |
display version |
| --config <config-name> (-c) |
specify build configuration to use when generating build specification. Note that if the configuration of dependent projects does not match the specified configuration, Visual Studio uses the first listed configuration for a project. As a result, kwdspparser and kwvcprojparser do not enforce the configuration name. For example, a solution file contains projects A and B, where A is the main project and depends on B. Project A has the configuration Foo, and Project B has the configurations Debug and Release. When parsing the solution file, the Klocwork parser picks the Debug configuration for Project B (since Foo was not found), and Foo for Project A. |
| -lc |
display a list of possible build configurations in a clean form, with no other output, one configuration per line |
| --list-vars (-lv) |
list all environment variables used in the project or solution (besides the Visual Studio built-in macros); clean output, one variable per line |
| --list-configs |
display a list of possible build configurations. |
| --output <output-file> (-o) |
specify the name and location of the build specification file. By default, it is named <file>.out, where <file> is the name of your Visual Studio file, and is saved in the current working directory. The suffix .out is appended by default. |
| --useenv |
allows you to use PATH, INCLUDE, LIBPATH and LIB environment variables instead of Visual Studio variables. |
