MATLAB: Do I need to include “matlab.h” in the driver application that uses MATLAB Compiler 4.0 (R14) generated C shared library

4.04.17.07.0.1compilerheaderincludelibraryMATLABMATLAB Compilermatlab.hmclmcr.hshared

I am trying to build a driver application that uses a MATLAB Compiler 4.0 (R14) generated C shared library with the MBUILD command. I am not sure if I have to include "matlab.h" header in the driver application, because I am used to include in driver applications that use C shared library target generated in previous versions.

Best Answer

The "matlab.h" header is no longer need to be included in the driver applications that use C shared libraries. To build an application that uses a MATLAB Compiler generated C shared library, include only the header file that gets generated along with the C shared library.

For additional information, see the link below for an example on C shared library target:

 <http://www.mathworks.com/help/toolbox/compiler/f2-972343.html>

Related Solutions

MATLAB: Are C++ shared library targets supported with MATLAB Compiler 3.0 (R13)

This has been verified as an error within the documentation for the MATLAB Compiler within the section for MCC. C++ shared library targets are not supported with MATLAB Compiler 3.0 (R13).

MATLAB: Do I receive a linking error about mclInitializeApplication_proxy and mclmcrInitialize_proxy when I compile the driver application that calls a C++ shared library compiled using MATLAB Compiler 4.10 (R2009a)

This error may occur only with MATLAB Compiler 4.8 (R2008a) or later versions because of changes that have been introduced in mclmcrrt.h and mclmcr.h, which impose the requirement that mclmcr.h always be included after mclmcrrt.h for the pre-processing stage.

In the attached driver application, the following code is found on Lines 1-2:

#include "mclcppclass.h"
#include "Test.h"

Here, mclcppclass.h (found in the <matlabroot>/extern/include directory) in turn includes mclmcr.h.

Also, in the generated Test.h file, the following code can be found:

#include "mclmcrrt.h"
#include "mclcppclass.h"

This results in mclcppclass.h being included before mclmcrrt.h, thus causing a symbol resolution issue for the identifiers mclInitializeApplication_proxy and mclmcrInitialize_proxy.

In order to resolve this issue, change the order of the header files in mydriver.cpp to the following:

#include "Test.h"
#include "mclcppclass.h"

Also, since Test.h already includes mclcppclass.h, you can entirely avoid including this header file in your driver application.

Best Answer

Related Solutions

MATLAB: Are C++ shared library targets supported with MATLAB Compiler 3.0 (R13)

MATLAB: Do I receive a linking error about mclInitial​izeApplica​tion_proxy and mclmcrInitialize_proxy when I compile the driver application that calls a C++ shared library compiled using MATLAB Compiler 4.10 (R2009a)

Related Question

MATLAB: Do I receive a linking error about mclInitializeApplication_proxy and mclmcrInitialize_proxy when I compile the driver application that calls a C++ shared library compiled using MATLAB Compiler 4.10 (R2009a)