You can package deployable archives at the MATLAB® prompt or your system prompt using either of these commands.
deploytool command has two flags that invoke one of the compiler apps
to package an already existing project without opening a window.
-build — Invoke
the correct compiler app to build the project but not generate an installer.
Invoke the correct compiler app to build the project and generate
deploytool -package magicsquare generates
the binary files defined by the
and packages them into an installer that you can distribute to others.
mcc command invokes the MATLAB
Compiler and provides fine-level control over the packaging of the deployable
archive. It, however, cannot package the results in an installer.
To invoke the compiler to generate a deployable archive, use the
CTF: flag with
CTF: flag creates a
deployable archive called
For packaging deployable archives, you can also use the following options.
|Add any files on the path to the generated binary.|
|Specify the folder into which the results of packaging are written.|
|Specify that an additional class is generated that includes methods for the listed MATLAB files.|
You perform the same functions using the compiler apps, a
function, or the
mcc command-line interface. The interactive menus and
dialog boxes used in the compiler apps build
mcc commands that are
customized to your specification. As such, your MATLAB code is processed the same way as if you were packaging it using
If you know the commands for the type of application you want to deploy and do not require
an installer, it is faster to execute either
mcc than go through the compiler app workflow.
Compiler app advantages include:
You can perform related deployment tasks with a single intuitive interface.
You can maintain related information in a convenient project file.
Your project state persists between sessions.
You can load previously stored compiler projects from a prepopulated menu.
You can package applications for distribution.