Shared Libraries and Utility Code
You can generate libraries and utility code that can be shared between model
components. A shared library can be a Windows®
dynamic link library (
shared object (
.so), or Macintosh OS X dynamic library
.dylib). You or others can integrate a shared library
into an application that runs on a Windows, UNIX, or Macintosh OS X development
computer. Uses of shared libraries include:
Adding a software component to an application for system simulation
Reusing software modules among applications on a development computer
Hiding intellectual property associated with software that you share with vendors
You also have the option of setting up shared utility code, which are files that the code generator produces for blocks in a model that share functionality. Models with an identical shared utility checksum can reuse the code in the shared utility files.
- Package Generated Code as Shared Libraries
Generate a shared library version of model code for your development platform.
- Use S-Function Target for Model or Subsystem
Use a shared library generated from a model or subsystem that you can load dynamically into another application.
- Interface to a Development Computer Simulator by Using a Shared Library
Generate a shared library that you can load dynamically into another application.
- Generate Shared Library for Export to External Code Base
Build a shared library from a model component and export the library to an application for system simulation, software reuse, or intellectual property protection. Requires an Embedded Coder license.
Shared Utility Code
- Generate Shared Utility Code
Modularize and share common Model block functionality as helper functions.
- Generate Shared Utility Code for Fixed-Point Functions
Generate reusable code for fixed-point support functions.
- Generate Shared Utility Code for Custom Data Types
Generate reusable code for custom data types.