Developing and Testing Components on a Development Machine

Packaging Your Software

To deploy your software to another development machine that does not have MATLAB installed or has a different version of MATLAB installed, use the GUI to package your software automatically. To do this, open the project and click the Package button in the Deployment Tool toolbar.

When you develop and test software created by MATLAB Compiler, set your path so that the system can support the compiled code at run time. To run the application on your development machine, make sure that you have your path set properly. See Directories Required for Development and Testing.

You cannot use the GUI to configure the development machine.

Replacement of MCRInstaller.zip and BUILDMCR Functionality

In past releases, you included MCRInstaller.zip in your packaged application (created by running the buildmcr command). Now, you run the following files, which trigger self-extracting archives, that replace the functionality previously provided by MCRInstaller.zip. These files ship with MATLAB Compiler:

PlatformFile Replacing MCRInstaller.zipFile Location
Windows 32-bitMCRInstaller.exematlabroot\toolbox\compiler\deploy\win32
Windows 64-bitMCRInstaller.exematlabroot\toolbox\compiler\deploy\win64
Linux (glnx86)MCRInstaller.binmatlabroot/toolbox/compiler/deploy/glnx86
Linux (glnxa64)MCRInstaller.binmatlabroot/toolbox/compiler/deploy/glnxa64
Mac®MCRInstaller.dmgmatlabroot/toolbox/compiler/deploy/mac
MaciMCRInstaller.dmgmatlabroot/toolbox/compiler/deploy/maci
Solaris (sol64)MCRInstaller.binmatlabroot/toolbox/compiler/deploy/sol64

Creating a Package

The package must include the following:

Configuring the Development Environment by Installing the MCR

To accurately produce the results of software compiled with MATLAB Compiler on a computer that doesn't have MATLAB installed, you must:

  1. Open the package created by you or the Deployment Tool.

  2. Run MCRInstaller once on the machine where you want to develop the application or library. MCRInstaller opens a command window and begins preparation for the installation.

  3. Add the required platform-specific directories to your dynamic library path. See Directories Required for Run-Time Deployment.

  


 © 1984-2008- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS