Customize Code Generation Environment
If you are responsible for customizing the code generation environment for a deployment project or for code deployment across an organization, consider these options.
Customization Goal | Description | More Information |
---|---|---|
Data representation | Customize how the code generator stores data, including matrices and arrays. Control the naming and placement of data types in generated code. | Data Representation in Generated Code |
Code interface configurations | Create code interface configurations for standardization and software architecture conformance. | Code Interface Definitions |
Code replacement | Create and maintain code replacement libraries that control how and when the code generator replaces code that it generates for functions and operators. | Code Replacement Customization |
Model configuration settings | Establish standard model configuration parameter settings that define how the code generator produces and compiles code from models. | Model Configuration Set Customization |
Custom blocks | Define code generation behavior for custom blocks by developing S-functions. | Code Generation for Custom Blocks |
Target Language Compiler | Use the Target Language Compiler to customize generated code, inline code generated for S-function blocks, and generate additional or different types of files. | Target Language Compiler |
Target platform devices | For a target platform device, select a system target file that specifies required
target platform environment and code features, use the target
namespace to extend the range of hardware that the code generator supports, and
configure the code generator to use code replacement libraries. | Target Platform Device Customization |
Code compilation | Customize the compilation stage of the build process by using a toolchain or template makefile approach. | Code Compilation Customization |
Custom software for target hardware | Create software that supports the deployment of MATLAB® and Simulink® designs to hardware platforms. Register custom toolchains for the build
process, customize XCP server software for target hardware, and create a target
hardware application that checks the validity of code generation assumptions. Use the
target namespace to extend the range of supported hardware and
provide connectivity between Simulink and your target hardware for external mode and processor-in-the-loop
(PIL) simulations. | Custom Software for Target Hardware |