User`s guide

1 Getting Star ted
Developing and Testing Components on a Development
Machine
In this section...
“Packaging Your Software” on p age 1-12
“Replacement of MCRI n s ta ll er.zip and BUI L DMCR Functio nality” on pa ge
1-12
“Creating a Package for Windows Users” on p age 1 -13
“Creating a Package for Users Who D o Not Use Windows” on page 1-13
“Configuring the Development Environment by Installing the MCR” on
page 1-14
Packaging Yo
ur Software
To de ploy you
r software to another development machine that does not
have MATLAB
installed (including a machine that has MATLAB but it
is a differe
nt version of MATLAB), you can use the G UI to package your
software automatically. (Open the project and click the Package icon
in
the Deployment Tool toolbar.)
Also, when y ou develop and test software created by MATLAB C ompiler you
must 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 you
have your path set properly. See “Directories Required for Development and
Testing” on page 9-2.
You cannot use the G UI to configure the development machine.
Replacement of MCRInstaller.zip and BUILDMCR
Functionality
In past releases, you needed to include MCRInstall er.zip in your packaged
application (created by running the
buildmcr command). Now you m us t run
the following f ile s, w h ich trigger self-extracting archives, that replace the
functionality p reviously provided b y
MCRInstaller.zip. These files ship with
MATLAB Compiler:
1-12