MATLAB Compiler :: Troubleshooting (MATLAB Compiler)

MATLAB Compiler

MATLAB Compiler

Typically, problems that occur when building stand-alone C and C++ applications involve mbuild. However, it is possible that you may run into some difficulty with the MATLAB Compiler. A good source for additional troubleshooting information for the MATLAB Compiler is the MATLAB Compiler Product Support page at the MathWorks Web site.

Licensing Problem. If you do not have a valid license for the MATLAB Compiler, you will get an error message similar to the following when you try to access the Compiler.

Error: Could not check out a Compiler License:
No such feature exists.

If you have a licensing problem, contact The MathWorks. A list of contacts at The MathWorks is provided at the beginning of this manual.

Missing Functions In Callbacks. 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, the Compiler will not compile the function. The Compiler does not look in these text strings for the names of functions to compile. See Fixing Callback Problems: Missing Functions for more information.

Borland Compiler Does Not Work with the Builder Products. The only compiler that supports the building of COM objects is Microsoft Visual C/C++ (versions 6.0, 7.0, and 7.1).

"MCRInstance not available" Message Displays. If you receive the message MCRInstance not available when you try to run a stand-alone application that was generated with the 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.

To verify that the MCR is properly located on your path, from a development Windows machine, confirm that <matlabroot>\bin\win32, where <matlabroot> is your root MATLAB directory, appears on your system path ahead of any other MATLAB installations. From a Windows target machine, verify that <mcr_root>\<ver>\runtime\win32, where <mcr_root> is your root MCR directory, appears on your system path.

To verify that the CTF file that the MATLAB Compiler generated in the build process resides in the same directory as your program's executable file, look at the directory containing the program's executable file and make sure the corresponding .ctf file is also there.

The UNIX verification process is the same, except you use the appropriate UNIX path information.

"MATLAB file may be corrupt" Message Displays. If you receive the message

This MATLAB file does not have proper version information and may 
be corrupt. Please delete the extraction directory and rerun the 
application.

when you run your stand-alone executable that was generated by the MATLAB Compiler, you should check the following.

Do you have a startup.m file that calls addpath? If so, this will cause 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
```

Verify that the .ctf archive file self extracted and that you have write permission to the directory.
Verify that none of the files in the <application name>_mcr directory have been modified or removed. Modifying this directory is not supported, and if you have modified it, you should delete it 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>_mcr directory and run the application.

MATLAB Compiler Does Not Generate Application. If you experience other problems with the MATLAB Compiler, contact Technical Support at The MathWorks at support@mathworks.com.

mbuild C++ Utility Library Reference