The MATLAB® Compiler™ Product :: Troubleshooting (MATLAB® Compiler™)

MATLAB® Compiler™

The MATLAB^® Compiler™ Product

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

libmwlapack: load error: stgsy2_. This error occurs when a customer has both R13 and R14 version of MATLAB^® or MCR/MGL specified in the directory path and the R14 version fails to load because of a lapack incompatability.

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

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.

MATLAB Compiler Does Not Generate Application. If you experience other problems with the MATLAB Compiler product, contact Technical Support at The MathWorks at http://www.mathworks.com/contact_TS.html.

"MATLAB file may be corrupt" Message Appears. 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 standalone that was generated by the MATLAB Compiler product, 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.

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 MATLAB Compiler product will not compile the function. The MATLAB Compiler product does not look in these text strings for the names of functions to compile. SeeFixing Callback Problems: Missing Functions 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 the MATLAB Compiler product, 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.

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 product generated in the build process resides in the same directory as your program's file, look at the directory containing the program's file and make sure the corresponding .ctf file is also there.

Unable to Run MCRInstaller.exe on a Target Windows Machine. If you receive the message

This advertised application would not be installed because it 
might be Unsafe. Contact your administrator to change the 
installation user interface option of the package to basic.

when you try to install the MATLAB Compiler Runtime (MCR) using MCRInstaller.exe on a Windows machine, you need to log in as an administrator. If this is not possible and you have no objection to installing the MCR in the default location, try the following command from a DOS window:

msiexec /qb /I MCRInstaller.msi

MCRInstaller.msi should have been placed in the installation directory after your first attempt to install the MCR. This command will start the installer using the basic UI configuration, which will execute at a lower security level.

warning LNK4248: unresolved typeref token (01000028) for 'mxArray_tag'; image may not run test3.obj. If you receive this message while compiling an MSVC application that calls a MATLAB Compiler generated shared library, you can safely ignore it. The message is due to changes in Visual C++^® 2005 compiler and will not interfere with successful running of your application. If you desire, you can suppress the message by including an empty definition for mxArray_tag inside your .cpp file (test3.cpp, in this case). For example, if you add the line:

struct mxArray_tag {};

at the beginning of your code and after the include statements, the warning will not recur.

mbuild

Deployed Applications