Configuration
To integrate Polyspace® Bug Finder™ effectively in a software development workflow, set appropriate analysis options for optimal results. In particular:
Emulate your source code build by creating a Polyspace project or options file using your build system, or by explicitly specifying compiler, sizes of data types, and other build-related options relevant for static analysis.
Specify checkers from coding standards such as MISRA C™ or CERT® C, or select from predefined defect checkers provided with Bug Finder. You can also create checkers for issues specific to your codebase, and package these checkers along with predefined checkers into your own coding standard.
Modify the default behavior of checkers by providing additional semantic information outside your source code.
You can configure Bug Finder by using a Polyspace Platform project, by using command-line flags, or by using an options file. See:
Categories
- Configure Sources and Build Options
Configure Polyspace to precisely mimic your build
- Configure Checks
Configure your analysis to detect various Polyspace Bug Finder defects and coding rules
- Improve Analysis Precision
Provide additional information about your code to improve precision of analysis results
- Create Your Own Coding Rules and Coding Standard
Check for issues specific to your code by creating user-defined coding rules and coding standards
- Configure Report Generation
Generate reports summarizing Polyspace Bug Finder analysis results
- Configure Review Information Import
Configure importing of review information from existing results
Related Information
- Configure Extension Settings (Polyspace as You Code)
- Configure Checkers (Polyspace as You Code)
