If your integrated development environment (IDE) has a MATLAB®-supported compiler, you can use the IDE to build engine applications. For an up-to-date list of supported compilers, see the Supported and Compatible Compilers website.
Engine applications require the Engine Library
the Matrix Library
libmx, and supporting include
files. When you build using the
mex command, MATLAB is
configured to locate these files. When you build in your IDE, you
must configure the IDE to locate them. Where these settings are depends
on your IDE. Refer to your product documentation.
Header files contain function declarations with prototypes for
the routines you access in the API libraries. These files are in the
and are the same for Windows®, Mac, and Linux® systems.
Engine applications use:
engine.h — function prototypes
for engine routines.
matrix.h — definition of
mxArray structure and function prototypes for
matrix access routines.
In your IDE, set the pre-processor include path to the value returned by the following MATLAB command:
You need the
libraries. The name of the file is platform-specific, as shown in
the following table.
Library File Names by Operating System
files are located in the folder
Add these library names to your IDE configuration. Set the library path to the value returned by the following MATLAB command:
Refer to your IDE product documentation for instructions.
libeng library requires additional third-party
library files. MATLAB uses these libraries to support Unicode® character
encoding and data compression in MAT-files.
These library files must reside in the same folder as the
You can determine what these libraries are using the platform-specific
commands shown in the following table. Once you identify these files,
update your IDE.
Library Dependency Commands
See the following instructions for Dependency Walker
On Windows systems, to find library dependencies, use the
third-party product Dependency Walker. Dependency Walker is a free
utility that scans Windows modules and builds a hierarchical tree diagram
of all dependent modules. For each module found, it lists all the
functions exported by that module, and which of those functions are
called by other modules. Download the Dependency Walker utility from
information on using the Dependency Walker.
Drag and drop the
libeng.dll file into the
Depends window. Identify the dependent libraries and add them to your