Package Deployable Archives from Command Line

You can package deployable archives at the MATLAB^® prompt or your system prompt using either of these commands.

deploytool invokes the Application Compiler app to execute a saved compiler project.
mcc invokes the MATLAB Compiler™ to create a deployable application at the command prompt.

Execute Compiler Projects with `deploytool`

The deploytool command has two flags that invoke one of the compiler apps to package an already existing project without opening a window.

-build project_name — Invoke the correct compiler app to build the project but not generate an installer.
-package project_name — Invoke the correct compiler app to build the project and generate an installer.

For example, deploytool -package magicsquare generates the binary files defined by the magicsquare project and packages them into an installer that you can distribute to others.

Package a Deployable Archive with `mcc`

The 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 -W CTF:component_name flag with mcc. The -W CTF:component_name flag creates a deployable archive called component_name.ctf.

For packaging deployable archives, you can also use the following options.

Option	Description
`-a filePath`	Add any files on the path to the generated binary.
`-d outFolder`	Specify the folder into which the results of packaging are written.
`class{className:mfilename...}`	Specify that an additional class is generated that includes methods for the listed MATLAB files.

Differences Between Compiler Apps and Command Line

You perform the same functions using the compiler apps, a compiler.build 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 mcc.

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 compiler.build or 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.