You typically compile your MATLAB® code on a development machine, test the resulting executable on that machine, and deploy the executable and MATLAB Runtime to a test or customer machine without MATLAB. The compilation process performs dependency analysis on your MATLAB code, creates an encrypted archive of your code and required toolbox code, generates wrapper code, and compiles the wrapper code into an executable. If your application fails to build an executable, the following questions may help you isolate the problem.
After you have successfully compiled your application, the next step is to test it on a development machine and deploy it on a target machine. Typically the target machine does not have a MATLAB installation and requires that the MATLAB Runtime be installed. A distribution includes all of the files that are required by your application to run, which include the executable, deployable archive and the MATLAB Runtime.
After the application is working on the test machine, failures can be isolated in end-user deployment. The end users of your application need to install the MATLAB Runtime on their machines. The MATLAB Runtime includes a set of shared libraries that provides support for all features of MATLAB. If your application fails during end-user deployment, the following questions in the column to the right may help you isolate the problem.
Solutions to problems when files cannot be found
Solutions to problems when classes cannot be found
Diagnostic messages with suggestions about their cause
Common MATLAB Compiler SDK™ error messages and associated workarounds.
In some circumstances, the XLA file cannot be generated. When that happens, the add-in can be installed as a Visual Basic project.
Excel can automatically disable the Server Configuration add-in, but you can manually reenable it
Add-ins that interact with MATLAB Production Server™