Run any Skill in Manus with one click

configure-build-options

Stars21

Forks1

UpdatedMay 7, 2026 at 11:10

Creates Polyspace build options files from build commands or compilation databases. Use when the user asks to "configure build options", "create build options file", "set up Polyspace build", or needs to configure compiler settings for Polyspace analysis.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mathworks

mathworks/polyspace-agentic-toolkit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	configure-build-options
description	Creates Polyspace build options files from build commands or compilation databases. Use when the user asks to "configure build options", "create build options file", "set up Polyspace build", or needs to configure compiler settings for Polyspace analysis.
license	MathWorks BSD-3-Clause
metadata	{"version":"1.0"}

How to Configure Build Options for Polyspace

Create a Polyspace build options file from either a build command (sniffing) or a compilation database (compile_commands.json). Exactly one source must be provided.

Using the MCP tool

If the Polyspace MCP Server is available, use the configure_build_options_for_polyspace tool:

build_options_file_path (required): absolute path to the output file to create
build_command (optional): the project build command to sniff
ccdb_file_path (optional): absolute path to compile_commands.json
extra_polyspace_configure_options_file_path (optional): extra polyspace-configure options

Exactly one of build_command or ccdb_file_path must be provided.

macOS: Build command sniffing (build_command) is not supported on macOS because System Integrity Protection (SIP) blocks polyspace-configure from tracing processes. Use ccdb_file_path with a compile_commands.json instead.

Otherwise using the binary directly

If the Polyspace MCP Server is NOT available, read cli-usage.md in this folder for direct command-line usage with polyspace-configure.

Finding a compilation database

CMake: add -DCMAKE_EXPORT_COMPILE_COMMANDS=ON to your CMake configure command
Bear: run bear -- make (or your build command) to generate compile_commands.json
Other build systems: check if your build system has native support for generating compile_commands.json

Common issues

Wrong compiler detected — specify the compiler explicitly in the extra options file
Missing include paths — ensure the build command or compilation database is complete
To see all available polyspace-configure options, run polyspace-configure -help

More from this repository

same repository

polyspace-agentic-toolkit-setup

mathworks/polyspace-agentic-toolkit

Sets up the Polyspace Agentic Toolkit for any supported AI agent. Use when the user asks to "set up Polyspace", "set up the Polyspace Agentic Toolkit", "install the Polyspace MCP Server", "configure Polyspace for my agent", or wants to get Polyspace working with their AI application.

2026-05-0721

configure-checkers

mathworks/polyspace-agentic-toolkit

Creates or modifies Polyspace checkers configuration files. Use when the user asks to "configure checkers", "set up MISRA checking", "enable CWE", "create checkers file", or needs to select coding standards for Polyspace analysis.

2026-05-0721

documentation-entry-points

mathworks/polyspace-agentic-toolkit

Provides Polyspace documentation entry points and links. Use when the user asks about "Polyspace documentation", "where is the Polyspace docs", "documentation links", or needs to find general Polyspace documentation.

2026-05-0721

find-checker-documentation

mathworks/polyspace-agentic-toolkit

Finds documentation for Polyspace checkers and coding rules. Use when the user asks "what does this checker do", "find checker documentation", "explain this Polyspace rule", or wants to understand a specific Polyspace finding.

2026-05-0721

find-option-documentation

mathworks/polyspace-agentic-toolkit

REQUIRED before searching for any Polyspace option documentation page. Use when the user asks about a Polyspace option (-c, -target, -sources, -boolean-types, -misra3, etc.), wants to find an option's doc page, or asks 'what does this option do'. This skill contains the only reliable method to locate option reference pages — URLs cannot be guessed from the flag name.

2026-05-0721

fix-findings

mathworks/polyspace-agentic-toolkit

Fixes or justifies Polyspace findings after analysis. Use when the user asks to "fix this finding", "fix these defects", "fix violations", "address Polyspace results", or wants to resolve static analysis findings.

2026-05-0721

name	configure-build-options
description	Creates Polyspace build options files from build commands or compilation databases. Use when the user asks to "configure build options", "create build options file", "set up Polyspace build", or needs to configure compiler settings for Polyspace analysis.
license	MathWorks BSD-3-Clause
metadata	{"version":"1.0"}

How to Configure Build Options for Polyspace

Create a Polyspace build options file from either a build command (sniffing) or a compilation database (compile_commands.json). Exactly one source must be provided.

Using the MCP tool

If the Polyspace MCP Server is available, use the configure_build_options_for_polyspace tool:

build_options_file_path (required): absolute path to the output file to create
build_command (optional): the project build command to sniff
ccdb_file_path (optional): absolute path to compile_commands.json
extra_polyspace_configure_options_file_path (optional): extra polyspace-configure options

Exactly one of build_command or ccdb_file_path must be provided.

Otherwise using the binary directly

If the Polyspace MCP Server is NOT available, read cli-usage.md in this folder for direct command-line usage with polyspace-configure.

Finding a compilation database

CMake: add -DCMAKE_EXPORT_COMPILE_COMMANDS=ON to your CMake configure command
Bear: run bear -- make (or your build command) to generate compile_commands.json
Other build systems: check if your build system has native support for generating compile_commands.json

Common issues

Wrong compiler detected — specify the compiler explicitly in the extra options file
Missing include paths — ensure the build command or compilation database is complete
To see all available polyspace-configure options, run polyspace-configure -help