Deployable archive data is automatically embedded directly in compiled components and extracted to a temporary folder.
Automatic embedding enables usage of 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 |
You can override this automatic embedding and extraction behavior by compiling with the Overriding Default Behavior option.
If you run
mcc specifying conflicting wrapper
and target types, the deployable archive will not be embedded into
the generated component. For example, if you run:
mcc -W lib:myLib -T link:exe test.m test.c
test.exewill not have the deployable archive embedded in it, as if you had specified a
-Coption to the command line.
To extract the deployable archive in a manner prior to R2008b,
alongside the compiled .NET assembly, compile using the
You might want to use this option to troubleshoot problems with the deployable archive, for example, as the log and diagnostic messages are much more visible.
For more information about the deployable archive, see Deployable Archive.