polyspace-configure

(System Command) Create Polyspace Platform project, workspace, or options file from build command or compilation database

Syntax

polyspace-configure [-output-platform-project|-update-platform-project] psPlatformProject [options] buildCommand

polyspace-configure [-output-platform-project|-update-platform-project] psPlatformProject -compilation-database jsonFile [options]

polyspace-configure -module [-output-platform-project|-update-platform-project] psPlatformWorkspace [options] buildCommand

polyspace-configure -modules-list fileWithModulesList [-project-root commonRootFolder] [-output-platform-project|-update-platform-project] psPlatformWorkspace [options] buildCommand

polyspace-configure -module-output-pattern regexPattern [-output-platform-project|-update-platform-project] psPlatformWorkspace [options] buildCommand

polyspace-configure -modules-list fileWithModulesList [-project-root commonRootFolder] [-output-platform-project|-update-platform-project] psPlatformWorkspace -compilation-database jsonFile [options]

polyspace-configure -module-output-pattern regexPattern [-output-platform-project|-update-platform-project] psPlatformWorkspace -compilation-database jsonFile [options]

polyspace-configure -output-options-file optionsFile [options] buildCommand

polyspace-configure -output-options-file optionsFile -compilation-database jsonFile [options]

polyspace-configure -module -output-options-path optionsFolder [options] buildCommand

polyspace-configure -modules-list fileWithModulesList [-project-root commonRootFolder] -output-options-path optionsFolder [options] buildCommand

polyspace-configure -module-output-pattern regexPattern -output-options-path optionsFolder [options] buildCommand

polyspace-configure -modules-list fileWithModulesList [-project-root commonRootFolder] -output-options-path optionsFolder -compilation-database jsonFile [options]

polyspace-configure -module-output-pattern regexPattern -output-options-path optionsFolder -compilation-database jsonFile [options]

Description

The polyspace-configure system command creates a Polyspace^® Platform project or options file from a build command or compilation database.

Create Project

polyspace-configure [-output-platform-project|-update-platform-project] psPlatformProject [options] buildCommand creates a Polyspace Platform project (.psprjx file) using information gathered from executing the command buildCommand.

• If you use the option -output-platform-project, the command creates a new project.

• If you use the option -update-platform-project, the command updates an existing project by overwriting auto-generated information such as automatically added sources and build configuration, and retaining manually added information such as static analysis configuration and tests.

If you create a project from a build command using polyspace-configure, the build command must be the last entry. Any option following the build command is considered as an option for the build command and not a polyspace-configure option.

polyspace-configure [-output-platform-project|-update-platform-project] psPlatformProject -compilation-database jsonFile [options] creates a Polyspace Platform project using information gathered from the JSON compilation database file specified by jsonFile.

Create Workspace with Multiple Projects for Multiple Components

polyspace-configure -module [-output-platform-project|-update-platform-project] psPlatformWorkspace [options] buildCommand creates or updates a Polyspace Platform workspace (.pswks file) using information from buildCommand. Each project in the workspace corresponds to one binary created by the build command and includes sources directly involved in creating the binary. The option -module is supported only if your build command uses GNU^® or Visual C++^® linkers.

polyspace-configure -modules-list fileWithModulesList [-project-root commonRootFolder] [-output-platform-project|-update-platform-project] psPlatformWorkspace [options] buildCommand creates or updates a Polyspace Platform workspace (.pswks file) using information from buildCommand. If the file fileWithModulesList lists multiple root folders with one folder per line, each project in the workspace includes all sources residing under one such root folder. If the folder paths are not absolute, they are resolved with respect to the current folder unless you use the option -project-root.

polyspace-configure -module-output-pattern regexPattern [-output-platform-project|-update-platform-project] psPlatformWorkspace [options] buildCommand creates or updates a Polyspace Platform workspace (.pswks file) using information from buildCommand. If the regular expression regexPattern contains a capturing group capturing multiple root folders, each project in the workspace includes all sources residing under one such root folder. If the folder paths are not absolute, they are resolved with respect to the current folder.

polyspace-configure -modules-list fileWithModulesList [-project-root commonRootFolder] [-output-platform-project|-update-platform-project] psPlatformWorkspace -compilation-database jsonFile [options] creates or updates a Polyspace Platform workspace (.pswks file) using information from a compilation database jsonFile. If the file fileWithModulesList lists multiple root folders with one folder per line, each project in the workspace includes all sources residing under one such root folder. If the folder paths are not absolute, they are resolved with respect to the current folder unless you use the option -project-root.

polyspace-configure -module-output-pattern regexPattern [-output-platform-project|-update-platform-project] psPlatformWorkspace -compilation-database jsonFile [options] creates or updates a Polyspace Platform workspace (.pswks file) using information from a compilation database jsonFile. If the regular expression regexPattern contains a capturing group capturing multiple root folders, each project in the workspace includes all sources residing under one such root folder. If the folder paths are not absolute, they are resolved with respect to the directory entry in the compilation database.

Create Options File

polyspace-configure -output-options-file optionsFile [options] buildCommand creates an options file for Polyspace static analysis using information gathered from executing the command buildCommand.

polyspace-configure -output-options-file optionsFile -compilation-database jsonFile [options] creates an options file for Polyspace static analysis using information gathered from the JSON compilation database file specified by jsonFile.

Create Multiple Options Files for Multiple Components

polyspace-configure -module -output-options-path optionsFolder [options] buildCommand creates multiple options files for static analysis in optionsFolder using information from buildCommand. Each options file corresponds to one binary created by the build command and lists sources directly involved in creating the binary. The option -module is supported only if your build command uses GNU or Visual C++ linkers.

polyspace-configure -modules-list fileWithModulesList [-project-root commonRootFolder] -output-options-path optionsFolder [options] buildCommand creates multiple options files for static analysis in optionsFolder using information from buildCommand. If the file fileWithModulesList lists multiple root folders with one folder per line, each generated options file lists sources residing under one such root folder. If the folder paths are not absolute, they are resolved with respect to the current working folder unless you use the option -project-root.

polyspace-configure -module-output-pattern regexPattern -output-options-path optionsFolder [options] buildCommand creates multiple options files for static analysis in optionsFolder using information from buildCommand. If the regular expression regexPattern contains a capturing group capturing multiple root folders, each generated options file lists sources residing under one such root folder. If the folder paths are not absolute, they are resolved with respect to the current folder.

polyspace-configure -modules-list fileWithModulesList [-project-root commonRootFolder] -output-options-path optionsFolder -compilation-database jsonFile [options] creates multiple options files for static analysis in optionsFolder using information from a compilation database jsonFile. If the file fileWithModulesList lists multiple root folders with one folder per line, each project in the workspace includes all sources residing under one such root folder. If the folder paths are not absolute, they are resolved with respect to the current folder unless you use the option -project-root.

polyspace-configure -module-output-pattern regexPattern -output-options-path optionsFolder -compilation-database jsonFile [options] creates multiple options files for static analysis in optionsFolder using information from a compilation database jsonFile. If the regular expression regexPattern contains a capturing group capturing multiple root folders, each generated options file lists sources residing under one such root folder. If the folder paths are not absolute, they are resolved with respect to the directory entry in the compilation database.

Examples

Create Polyspace Platform Project Using Compile Command (gcc, cl, etc.)

This example shows how to use a compile command to create a Polyspace Platform project. The simplest way to run polyspace-configure is to run it directly on the compile command used to build your source code. This example uses the GCC compiler and the compile command gcc. GCC is a standard compiler suite included with Linux^® based systems. For Windows^® based systems, MinGW can be installed to support the GCC compiler.

To create a Polyspace Platform project from a gcc compilation:

1. Open a terminal and run the gcc command to ensure that your source code compiles without errors.

   gcc myFilename.c otherFile.c

   After confirming that your source code compiles without errors, remove the object files before continuing.

   rm myFilename.o otherFile.o

2. Create a Polyspace Platform project specifying a unique project name. Run polyspace-configure on the compile command as previously tested.

   polyspace-configure -output-platform-project myProject gcc myFilename.c otherFile.c

3. Open the Polyspace Platform project in the Polyspace Platform user interface.

   If you use Visual Studio^® to compile your sources, you can replace gcc in the above example with cl. You can also run polyspace-configure on a full build of your Visual Studio project. See Create Polyspace Platform Projects From IDE Builds.

Create Polyspace Platform Project from Makefile

Typically, in real applications, you do not invoke the compiler directly to build your source code. Your build command runs several commands, one of which is compilation. For instance, you might be running a makefile to build your source code. This example shows how to create a Polyspace project if you use the command make targetName buildOptions to build your source code.

To create a Polyspace Platform project from a make command:

1. Open a terminal and run the make command to ensure that your source code builds without errors:

   make -B targetName
   

2. Create a Polyspace project specifying a unique project name.

   polyspace-configure  -output-platform-project myProject make -B targetName
   

   When running polyspace-configure on a make command:

   • Use the -B option with make so that all the prerequisite targets in the makefile are remade.

   • Use the exact options you otherwise use with make so that the Polyspace Platform project accurately reflects your build. For instance, suppose that when you run make, you append to a makefile variable CMD_OPTIONS as follows to exclude certain files from the build:

     make all "CMD_OPTIONS+=-DAPP_HAS_DEBUG -DNOT_UNIT_TEST"

     When running polyspace-configure, make sure to retain the same variable definition so that the same files are excluded from your Polyspace Platform project:

     polyspace-configure  -output-platform-project myProject make all -B "CMD_OPTIONS+=-DAPP_HAS_DEBUG -DNOT_UNIT_TEST"

   For an example using makefiles, see Create Polyspace Platform Projects from Builds That Use Makefiles.

3. Open the Polyspace project in the Polyspace user interface.

Create Polyspace Options File from JSON Compilation Database

This example shows how to create a Polyspace options file for static analysis from a JSON compilation database that you generate with the CMake build system generator. CMake generates build instructions for the build tool you specify, such as a UNIX^® Makefiles for make or project files for Microsoft^® Visual Studio. CMake supports the generation of a JSON compilation database only for Makefile generators and Ninja generator. For more information, see makefile generators.

To create a Polyspace Platform options file from a CMake compilation database:

1. First, generate the compilation database in JSON form for your CMake project. Open a terminal and navigate to the folder polyspaceroot\polyspace\examples\doc_ps_setup\compilation_database. Here, polyspaceroot is your Polyspace installation folder.

   This folder contains the file CMakeLists.txt which CMake uses as an input to generate build instructions.

2. Run these commands:

   mkdir JSON_cdb
   cd JSON_cdb
   cmake -G "Unix Makefiles" -DCMAKE_EXPORT_COMPILE_COMMANDS=1 ../

   The last command generates a UNIX makefile with build instructions for the make build tool. The command also outputs file compile_commands.json. This file lists the compiler calls for every translation unit in your project.

3. Generate a Polyspace options file from the compilation database that you generated in the previous step.

   polyspace-configure -compilation-database compile_commands.json -output-options-file options.txt

   You do not need to specify a build command and polyspace-configure does not trace your build. Polyspace extracts information about your build system from the JSON compilation database.

4. Pass the options file to Polyspace to run an analysis, for instance:

   polyspace-code-prover -options-file options.txt

Create Projects That Have Different Source Files from Same Build Trace

This example shows how to create different Polyspace Platform projects from the same trace of your build system. You can specify which source files to include for each project.

To create a Polyspace Platform project that only refers to a subset of sources from a build:

1. Trace your build system without creating a Polyspace project by specifying the option -no-project. To ensure that all the prerequisite targets in your makefile are remade, use the appropriate make build command option, for instance -B.

   polyspace-configure -no-project make -B
   

   polyspace-configure stores the cache information and the build trace in default locations inside the current folder. To store the cache information and build trace in a different location, specify the options -cache-path and -build-trace.

2. Generate Polyspace projects by using the build trace information from the previous step. Specify a project name and use the -include-sources or -exclude-sources option to select which files to include for each project.

   polyspace-configure -no-build -output-platform-project myProject -include-sources "<glob_pattern>"
   

   <glob_pattern> is a glob pattern that corresponds to folders or files you filter in or out of your project. To ensure the shell does not expand the glob patterns you pass to polyspace-configure, enclose them in double quotes. For more information on the supported syntax for glob patterns, see Select Files for Polyspace Project Using Pattern Matching.

   If you specified the options -build-trace and -cache-path in the previous step, specify them again.

3. Delete the trace file and cache folder.

   rm -r polyspace_configure_cache polyspace_configure_build_trace
    
   

   If you used the options -build-trace and -cache-path, use the paths and file names from those options.

Input Arguments

buildCommand — Command for full build of source code

string

Build command specified exactly as you use to build your source code. polyspace-configure supports tracing of a build command only if the build command meets certain requirements. See Requirements for Polyspace Project Creation from Build Systems.

The build command must perform a full build of your sources and not an incremental build. Typically, build commands such as make are set up to only build sources that have changed since the previous build. However, polyspace-configure requires a full build to determine which sources to add to a Polyspace project or options file. Add appropriate options to your build command to force a full build. For instance, when using a makefile, append the option -B to make.

Example: make -B, make -B -W makefileName

jsonFile — Name and path of compilation database JSON file

string

Name and path to JSON compilation database, specified as a string. The extracted compiler paths in the JSON CDB must be accessible from the path where you run polyspace-configure.

These build systems and compilers support the generation of a JSON CDB:

• CMake

• Bazel

• Clang

• Ninja

• Qbs

• waf

For more on JSON compilation databases, see JSON Compilation Database.

psPlatformProject — Name and path of generated Polyspace Platform project

string

Name and path of generated Polyspace Platform project, specified as a string.

• If you omit the path and specify a name only, a project file with this name and extension .psprjx is generated in the current folder.

  For instance, -output-platform-project newProject creates a project newProject.psprjx in the current folder.

• If you specify a name and path, a project file with this name and extension .psprjx is generated in the specified folder.

  For instance, -output-platform-project ../myProjects/newProject creates a project newProject.psprjx in the folder with the relative path ../myProjects/.

psPlatformWorkspace — Name and path of generated Polyspace Platform workspace

string

Name and path of generated Polyspace Platform workspace, specified as a string.

• If you omit the path and specify a name only, a workspace file with this name and extension .pswks is generated in the current folder.

  For instance, -output-platform-project newWorkspace creates a project newWorkspace.pswks in the current folder.

• If you specify a name and path, a workspace file with this name and extension .pswks is generated in the specified folder.

  For instance, -output-platform-project ../myWorkspaces/newWorkspace creates a project newWorkspace.pswks in the folder with the relative path ../myWorkspaces/.

optionsFile — Name and path of generated Polyspace options file

string

Name and path of generated options file, specified as a string.

• If you omit the path and specify a name only, an options file with this name is generated in the current folder.

  For instance, -output-options-file newOptsFile creates a file newOptsFile in the current folder.

• If you specify a name and path, an options file with this name is generated in the specified folder.

  For instance, -output-options-file ../myPolyspaceFiles/newOptsFile creates an options file newOptsFile in the folder with the relative path ../myPolyspaceFiles/.

Note that a Polyspace options file is useful only for static analysis using one of these commands:

• polyspace-bug-finder

• polyspace-code-prover

• polyspace-bug-finder-server

• polyspace-code-prover-server

optionsFolder — Path to folder containing generated options files

string

Path to folder, specified as a string. All generated options files are stored in this folder.

commonRootFolder — Path to folder with respect to which all relative paths must be resolved

string

Path to folder with respect to which all relative paths must be resolved, specified as a string.

fileWithModulesList — Path to file listing root folders

string

Path to file listing root folders, specified as a string. The file must contain one root folder per line. All source files in a root folder are considered as part of a single component.

regexPattern — Regular expression with capturing group

string

Regular expression with capturing group, specified as a string. If the capturing group captures multiple root folders, all source files in one root folder are considered as part of a single component.

options — Options for changing default operation of polyspace-configure

single option starting with -, followed by argument | multiple space-separated option-argument pairs

Basic Options — Options for output and debugging

string

Option	Description
-author authorName	Name of project author. Example: -author jsmith
-allow-build-error	Option to create a Polyspace project even if an error occurs in the build process. If an error occurs, the build trace log shows the following message: polyspace-configure (polyspaceConfigure) ERROR: build command command_name fail [status=status_value] command_name is the build command name that you use and status_value is the non-zero exit status or error level that indicates which error occurred in your build process. This option can create a useful project if your build command builds the source files but exits with a non-zero exit status. If your source files do not compile and the build fails, resolve your build failure before using polyspace-configure (polyspaceConfigure) again. This option is ignored when you use -compilation-database.
-allow-overwrite	Option to overwrite a project with the same name, if it exists. By default, polyspace-configure (polyspaceConfigure) throws an error if a project with the same name already exists in the output folder. Use this option to overwrite the project.
-no-console-output -silent (default) -verbose	Option to suppress or display additional messages from running polyspace-configure (polyspaceConfigure). -no-console-output – Suppress all outputs including errors and warnings. -silent (default) – Show only errors and warnings. -verbose – Show all messages. If you specify more than one of these options, the most verbose option is applied. Polyspace ignores these options when you use them in combination with -easy-debug.
-help	Option to display the full list of polyspace-configure (polyspaceConfigure) commands.
-debug	Option to store debug information for use by MathWorks® technical support. This option has been superseded by the option -easy-debug.
-easy-debug folderPath	Path of folder where Polyspace stores debug information for use by MathWorks technical support. After a polyspace-configure (polyspaceConfigure) run, the folder folderPath contains a zipped file ending with pscfg-output.zip. If the run fails to create a complete Polyspace project or options file, send this zipped file to MathWorks Technical Support for further debugging. The zipped file does not contain source files traced in the build. See also Errors in Project Creation from Build Systems.

Project Build and Testing Options — Options relevant to project build and testing

string

Option	Description
-categorization-config filePath	Path to file categorization XML file for distinguishing sources from tests in a Polyspace Platform project. Note that you do not need to use this XML file for test files using the following testing frameworks because the files are automatically identified as tests based on their inclusion of specific headers: Polyspace Test™ xUnit framework: The test files are identified by their inclusion of the header pstunit.h. GoogleTest: The test files are identified by their inclusion of the header gtest.h. Catch2: The test files are identified by their inclusion of the header catch2.h. The file classification XML is required only to enable support for other testing frameworks or to extend the support for the above testing frameworks. You can start creating the file categorization XML from this template: <categories> <category name="test"> <directories> <dir>myPSTestXUnitTestDir</dir> </directories> <headers> <include>myPSTestXUnitTestHeader</include> </headers> </category> <category name="external_test"> <directories> <dir>myExternalTestDir</dir> </directories> <headers> <include>myExternalTestHeader</include> </headers> </category> </categories> Any folder you specify in place of myExternalTestDir is considered as a folder containing external tests and any folder you specify in place of myPSTestXUnitTestHeader is considered as a folder containing Polyspace Test xUnit tests (you typically do not need this since files using the Polyspace Test xUnit API are automatically detected). Likewise, any header you specify in place of myExternalTestHeader is treated as an external test header. If a file indirectly includes a test header via another header, depending on how you generate the project, you might have to specify the second header in your file categorization XML. If you generate a project from a build command, the indirect inclusion of the test header is automatically detected. If you generate a project from a compilation database, explicitly specify the intermediate header in your file categorization XML as a test header. Example: -categorization-config test_classification.xml
-toolchain toolchainName	Toolchain to set in the Polyspace Platform project. The toolchain must have been registered previously using a custom target registration file and must be a valid value for the option Compilation toolchain (Testing) (Polyspace Test). To see the currently registered toolchains: In the Polyspace Platform user interface, open the configuration of a project. Check the values for the option Compilation toolchain (Testing). At the command line, list registered toolchains using the command: polyspace-test -manage-target-package -list Toolchain For more information, see polyspace-test -manage-target-package (Polyspace Test). Note that if you do not specify this option, the polyspace-configure command tries to assign a compilation toolchain for testing based on the compiler command invoked in your build. The polyspace-configure command tries to match the compiler command invoked in your build with the compiler command set in the currently registered toolchains. The compiler command can be set in a toolchain in several ways. For example, in a GMake-based toolchain, a compiler command is typically included in the toolchain using this syntax: toolchain = target.create('Toolchain', ... 'MakeToolType', 'GMake', ... 'Name', toolchainName, ... 'CCompiler', compileCommand) For more information, see target.Toolchain (Embedded Coder).

Advanced Options — Advanced configuration options

string

Option	Description
-compiler-config filePath	Path to compiler configuration XML file. The file must be in a specific format. For guidance, see the existing configuration files in polyspaceroot\polyspace\configure\compiler_configuration\. For information on the contents of the file, see Create Polyspace Projects from Build Systems That Use Unsupported Compilers. Example: -compiler-config myCompiler.xml
-no-project	Option to trace your build system without creating a Polyspace project and save the build trace information. Use this option to save your build trace information for a later run of polyspace-configure (polyspaceConfigure) with the -no-build option. This option is not compatible with -compilation-database.
-no-build	Option to create a Polyspace project using previously saved build trace information. To use this option, you must have the build trace information saved from an earlier run of polyspace-configure (polyspaceConfigure) with the -no-project option. If you use this option, you do not need to specify the buildCommand argument. This option is ignored when you use -compilation-database.
-no-sources	Option to create a Polyspace options file that does not contain the source file specifications. Use this option when you intend to specify the source files by other means. For instance, you can use this option when: Running Polyspace on AUTOSAR-specific code. You want to create an options file that traces your build command for the compiler options: -output-options-file options.txt -no-sources You later append this options file when extracting source file names from ARXML specifications and running the subsequent Code Prover analysis with polyspace-autosar -extra-options-file options.txt See also Run Polyspace on AUTOSAR Code Using Build Command. Running Polyspace in Eclipse™. Your source files are already specified in your Eclipse project. When running a Polyspace analysis, you want to specify an options file that has the compilation options only.
-extra-project-options polyspaceAnalysisOpts	Options that are used for subsequent Polyspace analysis. Once a Polyspace project is created, you can change some of the default options in the project. Alternatively, you can pass these options when tracing your build command. The flag -extra-project-options allows you to pass additional options. Specify multiple options in a space separated list, for instance "-allow-negative-operand-in-shift -stubbed-pointers-are-unsafe". Suppose you have to set the option -stubbed-pointers-are-unsafe for every Polyspace project created. Instead of opening each project and setting the option, you can use this flag when creating the Polyspace project: -extra-project-options "-stubbed-pointers-are-unsafe" For the list of options available, see: Configuration Configuration If you are creating an options file instead of a Polyspace project from your build command, do not use this flag. Instead, add the extra analysis options manually in the generated options file, in a separate options file, or at the command-line when you start the analysis.
-tmp-path folderPath	Path of folder where temporary files are stored.
-build-trace filePath	Path of file where build information is stored. The default is ./polyspace_configure_build_trace.log. Example: -build-trace ../build_info/trace.log
-log filePath	Path of log file where the output of the polyspace-configure (polyspaceConfigure) command is stored. The use of this option does not suppress the console output.
-include-sources glob pattern -exclude-sources glob pattern	Option to specify which source files polyspace-configure (polyspaceConfigure) includes in, or excludes from, the generated project. You can combine both options together. A source file is included if the file path matches the glob pattern that you pass to -include-sources. A source file is excluded if the file path matches the glob pattern that you pass to -exclude-sources.
-print-included-sources -print-excluded-sources	Option to print the list of source files that polyspace-configure (polyspaceConfigure) includes in, or excludes from, the generated project. You can combine both options together. The output displays the full path of each file on a separate line. Use this option to troubleshoot the glob patterns that you pass to -include-sources or -exclude-sources. You can see which files match the pattern that you pass to -include-sources or -exclude-sources.
-compiler-cache-path folderPath	Specify a folder path where polyspace-configure (polyspaceConfigure) looks for or stores the compiler cache files. If the folder does not exist, polyspace-configure (polyspaceConfigure) creates it. By default, Polyspace looks for and stores compiler caches under these folder paths: Windows %appdata%\Mathworks\R2026a\Polyspace Linux ~/.matlab/R2026a/Polyspace Mac ~/Library/Application Support/MathWorks/MATLAB/R2026a/Polyspace
-no-compiler-cache	Use this option if you do not want Polyspace to cache your compiler configuration information or to use an existing cache for your compiler configuration. By default, the first time you run polyspace-configure (polyspaceConfigure) with a particular compiler configuration, Polyspace queries your compiler for the size of fundamental types, compiler macro definitions, and other compiler configuration information then caches this information. Polyspace reuses the cached information in subsequent runs of polyspace-configure (polyspaceConfigure) for builds that use the same compiler configuration.
-reset-compiler-cache-entry	Use this option to query the compiler for the current configuration and to refresh the entry in the cache file that corresponds to this configuration. Other compiler configuration entries in the cache are not updated.
-clear-compiler-cache	Use this option to delete all compiler configurations stored in the cache file. If you also specify a build command or -compilation-database, polyspace-configure (polyspaceConfigure) computes and caches the compiler configuration information of the current run, except if you specify -no-project or -no-compiler-cache.
-import-macro-definitions none | from-allowlist | from-source-tokens | from-compiler	Typically, you do not need to specify this option. Polyspace attempts to automatically determine the best strategy to query your compiler for macro definitions in this order of priority: from-compiler — Polyspace uses native compiler options, such as gcc -dm -E, to obtain the compiler macro definitions. This strategy does not require Polyspace to trace your build and is available only for compilers that support listing macro definitions. from-source-tokens — Polyspace uses every non-keyword token in your source code to query your compiler for macro definitions. This strategy is available only if Polyspace can trace your build. The strategy is not available if you use option -compilation-database. from-allowlist — Polyspace uses an internal allow list to query the compiler for macro definitions. If you prefer to specify macro definitions manually, use this option with the none flag and use option Preprocessor definitions (-D) to specify the macro definitions. If the macro import strategy that Polyspace uses is not the one that you expect, try specifying this option manually to troubleshoot the issue.
-options-for-sources-delimiter delimCharacter	Specify the character to use as a separator between analysis options when Polyspace generates an options file associated with one source file using the option -options-for-sources. Typically, the option -options-for-sources uses the ; character (semicolon) as a separator between analysis options in the generated file. See also -options-for-sources.

Cache Control Options — Generate cache options for debugging

string

These options are primarily useful for debugging. Use the options if polyspace-configure (polyspaceConfigure) fails and MathWorks Technical Support asks you to use the option and provide the cached files. Starting R2020a, the option -easy-debug provides an easier way to provide debug information. See Contact Technical Support About Issues with Running Polyspace.

Polyspace ignores these options when you use -compilation-database.

Option	Description
-no-cache -cache-sources (default) -cache-all-text -cache-all-files	Option to perform one of the following: -no-cache: Not create a cache -cache-sources: Cache text files temporarily created during build for later use by polyspace-configure (polyspaceConfigure). -cache-all-text: Cache all text files including sources and headers. -cache-all-files: Cache all files including binaries. Typically, you cache temporary files created by your build command to debug issues in tracing the command.
-cache-path folderPath	Path of folder where cache information is stored. When tracing a Visual Studio build (devenv.exe), if you see the error: path is too long try using a shorter path for this option to work around the error. Example: -cache-path ../cache
-keep-cache -no-keep-cache (default)	Option to preserve or clean up cache information after polyspace-configure (polyspaceConfigure) completes execution. If polyspace-configure (polyspaceConfigure) fails, you can provide this cache information to technical support for debugging purposes.

Algorithms

The polyspace-configure command creates a Polyspace project or options file from a build command such as make using roughly these steps:

1. The build command is first executed. polyspace-configure keeps track of the commands that run during this build and the files read or written. One or more of these commands would be the compiler invocation. For instance, if the build command uses a GCC compiler, one or more of these commands would exercise the gcc, g++, or related executable. Based on the presence of a known compiler executable, polyspace-configure picks out the compiler invocation commands from amidst all the commands executed during build.

2. Each compiler invocation command contains these three parts: the compiler executable, some source files and some compiler options. For instance, the following command exercises the GCC compiler on the file myFile.c with a compiler option -std that triggers C++11-based compilation:

   gcc -std=c++11 myFile.c

   polyspace-configure reads the source file names from these commands and directly uses them in the Polyspace project or options file. The compiler executable and compiler options are translated to Polyspace analysis options.

   To determine Polyspace options such as the ones corresponding to sizes of basic types or underlying type of size_t, polyspace-configure runs the previously read compiler executable plus compiler options on some small source files. Depending on whether a source file compiles successfully or shows errors, polyspace-configure can set an appropriate Polyspace option. To determine compiler macro definitions and include paths, polyspace-configure also reinvokes the compiler on small sources but thereafter uses a slightly different strategy.

   For a simple example of a source file that can help determine a Polyspace option, see the reference page for the option Management of size_t (-size-t-type-is).

Instead of a build command, polyspace-configure can also create a project or options file from a JSON compilation database. When the polyspace-configure command runs on a compilation database, the first step above is omitted. A compilation database directly states the compiler invocation command in entries such as this:

{
"directory": "/proj/files/
"command": "/usr/local/bin/gcc -std=c++11 -c /proj/files/myFile.c",
"file" : "/proj/files/myFile.c"
}

polyspace-configure can simply read these compiler invocation commands and continue with the remaining step of reinvoking the compiler on small source files. Since the build command execution step is skipped, running polyspace-configure on a compilation database is much faster than running polyspace-configure on a build command. However, it is your responsibility to make sure that the compilation database you provide accurately reflects a full build of your source code.

Version History

Introduced in R2013b

R2026a: Default output format will change and option -output-project will be removed in a future release

The default output format of the polyspace-configure command will change in a future release. In addition, the option -output-project will also be removed.

Currently, the polyspace-configure command – by default or when used with the -output-project option – generates a project file in the .psprj format. This format is intended for the classic Polyspace user interface, which has been replaced with the Polyspace Platform user interface. For more information, see Using Polyspace Platform as Default User Interface for Static Analysis.

To generate Polyspace Platform projects in the new .psprjx format using polyspace-configure, use the -output-platform-project option. This new format will become the default format in a future release.