Documentation

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

libmwlapack: load error: stgsy2_.  This error occurs when a customer has both the R13 and the R14 version of MATLAB or MATLAB Runtime/MGL specified in the folder path and the R14 version fails to load because of a lapack incompatibility.

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

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

loadlibrary usage (MATLAB loadlibrary command).  The following are common error messages encountered when attempting to compile the MATLAB loadlibrary function or run an application that uses the MATLAB loadlibrary function with MATLAB Compiler:

• Output argument 'notfound' was not assigned during call to 'loadlibrary'.

• Warning: Function call testloadlibcompile 
  invokes inexact match
  d:\work\testLoadLibCompile_mcr\
  testLoadLibCompile\testLoadLibCompile.m.
  
  ??? Error using ==> loadlibrary
  Call to Perl failed. Possible error processing header file.
  Output of Perl command:
  Error using ==> perl
  All input arguments must be valid strings.
  
  Error in ==> testLoadLibCompile at 4 

• MATLAB:loadlibrary:cannotgeneratemfile
  There was an error running the loader mfile. 
  Use the mfilename option
  to produce a file that you can debug and fix. 
  Please report this
  error to the MathWorks so we can improve this 
  function.
  ??? Error using ==> feval
  Undefined function or variable 'GHlinkTest_proto'.
  
  Error in ==> loadtest at 6 

For information about how to properly invoke the MATLAB loadlibrary function with MATLAB Compiler, see MATLAB Libraries Using loadlibrary in the Deploying MATLAB Code section in your product user's guide.

MATLAB Compiler Does Not Generate the Application.  If you experience other problems with MATLAB Compiler, contact Technical Support at 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.

• 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 folder.

• Verify that none of the files in the <application name>_mcr folder have been modified or removed. Modifying this folder 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 folder 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 MATLAB file this function is called, MATLAB Compiler will not compile the function. MATLAB Compiler does not look in these text strings for the names of functions to compile. See Fixing 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 MATLAB Compiler, it can be that the MATLAB Runtime is not located properly on your path or the deployable archive is not in the proper folder (if you extracted it from your binary). The UNIX^® verification process is the same, except you use the appropriate UNIX path information.

To verify that the MATLAB Runtime is properly located on your path, from a development Windows^® machine, confirm that matlabroot\runtime\win32|win64, where matlabroot is your root MATLAB folder, appears on your system path ahead of any other MATLAB installations.

From a Windows target machine, verify that <mcr_root>\<ver>\runtime\win32|win64, where <mcr_root> is your root MATLAB Runtime folder, appears on your system path. To verify that the deployable archive that MATLAB Compiler generated in the build process resides in the same folder as your program's file, look at the folder containing the program's file and make sure the corresponding .ctf file is also there.

No Info.plist file in application bundle or no... .  On 64-bit Macintosh, indicates the application is not being executed through the bundle.