Check undefined symbols
Specify whether to check for undefined symbols
Since R2023b
Description
This option specifies whether Polyspace® Test™ checks the code for undefined symbols during the build process. This option applies only to dynamic testing.
Set Option
In your Polyspace Platform project configuration, select this option on the Project tab.
Why Use This Option
By default, Polyspace Test checks your code for undefined symbols and exits the build process with an error if your code contains undefined symbols. Use this option to allow the build process to proceed without checking for undefined symbols.
This option can be useful if the undefined symbols in your code are defined in a dynamic runtime library, precompiled object file, or a static library. In such cases, the definitions of the symbols are not available when the code is parsed, but becomes available to the linker during the build process. If the undefined symbols in your code are available to the linker at build time, you can clear this option and allow Polyspace Test to proceed without checking for undefined symbols.
Settings
On (default)Polyspace Test checks for undefined symbols.
Off Polyspace Test does not check for undefined symbols.
Command-Line Information
The command-line workflow for setting this option depends on your workflow.
If you build your source and tests using a Polyspace Platform Project — Once you set this option in the project using the Polyspace Platform user interface, you cannot override or modify this option using the
polyspace-testcommand.If you build your sources and xUnit tests using your own toolchain — You can instruct your compiler to ignore undefined symbols. For instance, use the option
--unresolved-symbols=ignore-in-object-filesfor gcc or g++ compilers.
Version History
Introduced in R2023b
