MATLAB Runtime Component Cache and Deployable Archive Embedding
Deployable archive data is automatically embedded directly in .NET Assemblies by default and extracted to a temporary folder.
Automatic embedding enables usage of the MATLAB® Runtime component cache features through environment variables.
These variables allow you to specify the following:
Define the default location where you want the deployable archive to be automatically extracted
Add diagnostic error printing options that can be used when automatically extracting the deployable archive, for troubleshooting purposes
Tuning the MATLAB Runtime component cache size for performance reasons.
Use the following environment variables to change these settings.
|MCR_CACHE_ROOT||When set to the location of where you want the deployable archive to be extracted, this
variable overrides the default per-user component cache location. This is true
for embedded ||On macOS, this variable is ignored in MATLAB R2020a and later. The app bundle contains the files necessary for runtime.|
|MCR_CACHE_SIZE||When set, this variable overrides the default component cache size.||The initial limit for this variable is 32M (megabytes). This
may, however, be changed after you have set the variable the first
time. Edit the file |
If you run
mcc specifying conflicting wrapper and target types,
the archive will not be embedded into the generated component. For example, if you
mcc -W lib:myLib -T link:exe test.m test.c
test.exe will not have the archive embedded in it,
as if you had specified a
-C option to the command line.
Do not extract the files within the
.ctf file and place them
individually under version control. Since the
.ctf file contains
interdependent MATLAB functions and data, the files within it must be accessed only by accessing
.ctf file. For best results, place the entire
.ctf file under version control.