You can integrate generated C code from previous releases (R2010a and later) with generated code from the current release when the source models are single-rate and the generated C code is from:
Top-model or subsystem build processes that use the nonreusable function code interface.
Single or multiple instance model reference build processes that suppress error status monitoring.
Use a protected model (single-rate or multirate) from a previous release (R2018b and later) to test numerical equivalence between the protected model and its previously generated code. Generate new code in the current release.
Reduce verification cost by reusing shared utility code from a previous release.
|Import generated model code from a previous release as SIL or PIL blocks|
|Replace block in model with block from another model|
|Manage MATLAB versions for cross-release code integration|
|Add new shared code source files to existing shared code folder|
- Cross-Release Code Integration
Integrate generated code from previous releases with generated code from current release.
- Integrate Generated Code by Using Cross-Release Workflow
Reuse previously generated code by using a cross-release SIL block in an integration model.
- Use Protected Models from Previous Releases to Perform SIL Testing and Generate Code
Integrate generated code from protected models created in previous releases.
- Integration of Code from Multiple Folders
Integrate separately generated code.
- Cross-Release Shared Utility Code Reuse
Reuse shared utility or external code across releases.