mbuild :: Troubleshooting (MATLAB Compiler)

MATLAB Compiler

mbuild

This section identifies some of the more common problems that might occur when configuring mbuild to create stand-alone applications.

Options File Not Writeable. When you run mbuild -setup, mbuild makes a copy of the appropriate options file and writes some information to it. If the options file is not writeable, you are asked if you want to overwrite the existing options file. If you choose to do so, the existing options file is copied to a new location and a new options file is created.

Directory or File Not Writeable. If a destination directory or file is not writeable, ensure that the permissions are properly set. In certain cases, make sure that the file is not in use.

mbuild Generates Errors. If you run mbuild filename and get errors, it may be because you are not using the proper options file. Run mbuild -setup to ensure proper compiler and linker settings.

Compiler and/or Linker Not Found. On Windows, if you get errors such as unrecognized command or file not found, make sure the command line tools are installed and the path and other environment variables are set correctly in the options file. For MS Visual Studio, for example, make sure to run vcvars32.bat (MSVC 6.x and earlier) or vsvars32.bat (MSVC 7.x).

mbuild Not a Recognized Command. If mbuild is not recognized, verify that <matlabroot>\bin is on your path. On UNIX, it may be necessary to rehash.

mbuild Works from Shell But Not from MATLAB (UNIX). If the command

```
mcc -m hello
```

works from the UNIX command prompt but does not work from the MATLAB prompt, you may have a problem with your .cshrc file. When MATLAB launches a new C shell to perform compilations, it executes the .cshrc script. If this script causes unexpected changes to the PATH environment variable, an error may occur. You can test this by performing a

```
set SHELL=/bin/sh
```

prior to launching MATLAB. If this works correctly, then you should check your .cshrc file for problems setting the PATH environment variable.

Cannot Locate Your Compiler (Windows). If mbuild has difficulty locating your installed compilers, it is useful to know how it goes about finding compilers. mbuild automatically detects your installed compilers by first searching for locations specified in the following environment variables:

BORLAND for Borland C/C++, Version 5.3
MSVCDIR for Microsoft Visual C/C++, Version 6.0, 7.0, or 7.1

Next, mbuild searches the Windows registry for compiler entries.

Internal Error When Using mbuild -setup (Windows). Some antivirus software packages such as Cheyenne AntiVirus and Dr. Solomon may conflict with the mbuild -setup process. If you get an error message during mbuild -setup of the following form

mex.bat: internal error in sub get_compiler_info(): don't 
recognize <string>

then you need to disable your antivirus software temporarily and rerun mbuild -setup. After you have successfully run the setup option, you can reenable your antivirus software.

Verification of mbuild Fails. If none of the previous solutions addresses your difficulty with mbuild, contact Technical Support at The MathWorks at support@mathworks.com.

Troubleshooting MATLAB Compiler