| Contents | Index |
| On this page… |
|---|
Steps by the developer to Deploy to Developers |
Note If you are programming on the same machine where you created the component, you can skip the steps described here. |
Create a package that contains the software necessary to support the compiled MATLAB code. It is frequently helpful to install the MCR on development machines, for testing purposes. See What Software Does a Developer Need?
Note You can use the Deployment Tool to create a package for developers. For Windows platforms, the package created by the Deployment Tool is a self-extracting executable. For UNIX platforms, the package created by the Deployment Tool is a zip file that must be decompressed and installed manually. See Getting Started to get started using the Deployment Tool. |
Write instructions for how to use the package.
If your package was created with the Deployment Tool, Windows developers can just run the self-extracting executable created by the Deployment Tool. UNIX developers must unzip and install manually.
All developers must set path environment variables properly. See Set MCR Paths for Development and Testing.
Distribute the package and instructions.
The software that you provide to a developer who wants to use compiled MATLAB code depends on which of the following kinds of software the developer will be using:
To distribute a standalone application created with MATLAB Compiler to a development machine, create a package that includes the following files.
| Software Module | Description |
|---|---|
| MCR Installer (Windows) | The MCR Installer is a self-extracting executable that installs the necessary components to develop your application. This file is included with MATLAB Compiler. Run mcrinstaller function to obtain name of executable. |
| MCR Installer (Linux) | The MCR Installer is a self-extracting executable that installs the necessary components to develop your application on UNIX machines (other than Mac). This file is included with MATLAB Compiler. Run mcrinstaller function to obtain name of binary. |
| MCR Installer (Mac) | Run mcrinstaller function to obtain name of binary. |
| application_name.exe (Windows) | Application created by MATLAB Compiler. Maci64 must include the bundle directory hierarchy. |
| application_name (UNIX) | |
| application_name.app (Maci64) |
Note If you are using a non-Windows operating system, "console applications" are referred to as "standalone applications". |
To distribute a shared library created with MATLAB Compiler to a development machine, create a package that includes the following files.
Software Module | Description |
|---|---|
| MCR Installer (Windows) | MATLAB Compiler Runtime library archive; platform-dependent file that must correspond to the end user's platform. Run mcrinstaller function to obtain name of executable. |
| MCR Installer (Mac) | The MCR Installer is a self-extracting executable that installs the necessary components to develop your application on Mac machines. This file is included with MATLAB Compiler. Run mcrinstaller function to obtain name of binary. |
| MCR Installer (Linux) | Self-extracting MATLAB Compiler Runtime library utility; platform-dependent file that must correspond to the end user's platform. Run mcrinstaller function to obtain name of binary. |
libmatrix | Shared library; extension varies by platform, for example, DLL on Windows |
libmatrix.h | Library header file |
libmatrix.lib | Application library file needed to create the driver application for the shared library. |
To distribute a .NET component to a development machine, create a package that includes the following files.
| Software Module | Description |
|---|---|
| componentName.xml | Documentation files |
| componentName.pdb (if Debug option is selected) | Program Database File, which contains debugging information |
| componentName.dll | Component assembly file |
| MCR Installer | MCR Installer (if not already installed on the target machine). Run mcrinstaller function to obtain name of executable. |
To distribute a COM component to a development machine, create a package that includes the following files.
| Software Module | Description |
|---|---|
| mwcomutil.dll | Utilities required for array processing. Provides type definitions used in data conversion. |
| componentname_ version.dll | Component that contains compiled MATLAB code. |
| MCR Installer | Self-extracting MATLAB Compiler Runtime library utility; platform-dependent file that must correspond to the end user's platform. The MCR Installer installs MATLAB Compiler Runtime (MCR), which users of your component need to install on the target machine once per release. Run mcrinstaller function to obtain name of executable. |
To distribute a Java component to a development machine, create a package that includes the componentname.jar file, a Java package containing the Java interface to MATLAB code.
Note For more information, see the MWArray Javadoc, which is searchable from the Help or from the MathWorks Web site. |
To distribute a COM component for Excel to a development machine, create a package that includes the following files.
| Software Module | Description |
|---|---|
| componentname_projectversion.dll | Compiled component. |
| MCR Installer | Self-extracting MATLAB Compiler Runtime library utility; platform-dependent file that must correspond to the end user's platform. The MCR Installer installs the MATLAB Compiler Runtime (MCR), which users of your component need to install on the target machine once per release. Run mcrinstaller function to obtain name of executable. |
| *.xla | Any user-created Excel add-in files found in the <projectdir>\distrib folder |
If you are having trouble obtaining memory for your deployed application, use MATLAB Memory Shielding for deployed applications to ensure a maximum amount of contiguous allocated memory. See Reserving Memory for Deployed Applications with MATLAB Memory Shielding for more information.
![]() | Overview | Deploying to End Users | ![]() |

Learn how to build standalone executables and C/C++ shared libraries from MATLAB code.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |