Specify whether or not to parse available custom code variables and functions and compile custom code into its own simulation target. This option affects the C Caller block, the MATLAB Function block, the MATLAB System block, and Stateflow® charts.
Category: Simulation Target
Enables parsing of custom code to report unresolved symbols in C charts of your model. When this option is on, Simulink®:
Uses the same custom code for simulation with the C Caller block, the MATLAB Function block, the MATLAB System block, and Stateflow charts. When using the C Caller block or the C Function block, this option must be turned on.
Automatically rebuilds the custom code simulation target when specified custom code dependencies change.
Automatically rebuilds simulation targets for blocks using custom code when custom code changes.
Enables Just-In-Time (JIT) compilation of the C Caller block, the MATLAB Function block, the MATLAB System block, and Stateflow charts.
Allows the Enable custom code analysis option to enable Simulink Coverage and Simulink Design Verifier support for custom code.
Disables importing of custom code. Turn off Import custom code to allow Simulink to:
Split custom code dependencies between
Simulation Target and other means of specifying
custom code dependencies
Stateflow charts that use MATLAB® as the action language, the
MATLAB Function block, or the MATLAB System block.
Allow functions without C interfaces, and support overloaded C++ functions from custom code.
Permit custom code dependencies to contain declared but undefined function symbols. Otherwise Simulink creates a version of the symbol that returns a zero value.
In Stateflow charts that use MATLAB as the action language, you can
access C++ class members with the
-> operator, access members in
a structure containing a pointer to itself with a
-> operator, and access members
in a union type.
You cannot split custom code dependencies by specifying the path and the source files at different locations.