Each application or shared library you produce using the compiler has an embedded deployable archive. The archive contains all the MATLAB® based content (MATLAB files, MEX-files, and so on). All MATLAB files in the deployable archive are encrypted using the Advanced Encryption Standard (AES) cryptosystem.
If you choose to extract the deployable archive as a separate file, the files remain encrypted. For more information on how to extract the deployable archive refer to the references in the following table.
Information on Deployable Archive Embedding/Extraction and Component Cache
|MATLAB Compiler SDK™ C/C++ integration||MATLAB Runtime Component Cache and Deployable Archive Embedding (MATLAB Compiler SDK)|
|MATLAB Compiler SDK .NET integration||MATLAB Runtime Component Cache and Deployable Archive Embedding (MATLAB Compiler SDK)|
|MATLAB Compiler SDK Java® integration||Define Embedding and Extraction Options for Deployable Java Archive (MATLAB Compiler SDK)|
|MATLAB Compiler™ Excel® integration||MATLAB Runtime Component Cache and Deployable Archive Embedding|
Multiple deployable archives, such as those generated with COM components, .NET assemblies, or Excel add-ins, can coexist in the same user application. You cannot, however, mix and match the MATLAB files they contain. You cannot combine encrypted and compressed MATLAB files from multiple deployable archives into another deployable archive and distribute them.
All the MATLAB files from a given deployable archive associate with a unique cryptographic key. MATLAB files with different keys, placed in the same deployable archive, do not execute. If you want to generate another application with a different mix of MATLAB files, recompile these MATLAB files into a new deployable archive.
The compiler deletes the deployable archive and generated binary
following a failed compilation, but only if these files did not exist
before compilation initiates. Run
help mcc -K for
Release Engineers and Software Configuration Managers: Do not use build procedures or processes that strip shared libraries on deployable archives. If you do, you can possibly strip the deployable archive from the binary, resulting in run-time errors for the driver application.