User`s guide

MATLAB Compiler
when you run your standalone that was generated by MATLAB Compiler, you
should check the following:
• Do you have a
startup.m file that calls a ddp ath?Ifso,thiswillcause
run-time errors. As a workaround, use
isdeployed to have the addpath
command execute only from MATLAB. For example, use a construct such
as:
if ~isdeployed
addpath(path);
end
• Ve rify that the .ctf archive file self extracted and that y ou have write
permission to the directory.
• Ve rify that none of the files in the
<application name>_mc r directory
have been modified or removed. Modifying this d irectory is not supported,
and if you have modified it, you should delete i t and redeploy or restart
the application.
• If none of the above possible causes apply, then the error is likely caused
by a corruption. Delete the
<application name>_mc r directory and run
the application.
Missing Functi o ns in Callba cks. If your application includes a call to a
function in a callback string or in a string passed as an argument to the
feval function or an ODE solver, and this is the only place in your M-file this
function is called, MATLAB C ompiler will not compile th e function. MATLAB
Compiler does not look in these text strings for the names of functions to
compile. See“Fixing Callback Problems: Missing Functions” on page 12-3
for more information.
"MCRInstance not available" Message Appears. If you
receive the message
MCRInstance not available when you
try to run a standalone application that was generated with
MATLAB Compiler, it could be that the MCR is not located
properly on your path or the CTF file is not in the proper directory.
The UNIX verification process is the same, except you use the appropriate
UNIX path information.
8-5