MATLAB: Using MCR in C++ project: undefined reference to `mclInitializeComponentInstanceWithEmbeddedCTF_proxy’

cMATLAB Compilermclmcrmclmcrrtmcr

I am getting an undefined reference to a MCR function `mclInitializeComponentInstanceWithEmbeddedCTF_proxy' when trying to build a C++ application in Eclipse. This function is defined in mclmcr.h and mclmcrrt.h as part of MCR, which are both included in the project. I am using the most recent version of MCR.

When I build the project: (omitted most .o files for clarity)

make all Building target: MYPROJECT Invoking: GCC C++ Linker g++ -L"/sandbox/path/to/my/lib" -L/usr/include/boost -L/opt/matlab/MATLAB_Compiler_Runtime/v717/runtime/glnx86 ./all/my/files.o -lboost_thread-mt -lboost_system -lboost_filesystem -lpthread -lmwmclmcrrt

/sandbox/path/to/my/lib/mylib.so: undefined reference to `mclInitializeComponentInstanceWithEmbeddedCTF_proxy' collect2: ld returned 1 exit status make: * [MYPROJECT] Error 1

Best Answer

According to this solution, you may be linking against the wrong version of mclmcrrt.lib. You appear to be linking against the library corresponding to R2012a, but you need to get the one corresponding to the version of the MATLAB that you library was compiled with.

Related Solutions

MATLAB: Do I receive the LNK2001 error when trying to compile a simple MATLAB program using MATLAB Compiler 4.8 (R2008b)

The LNK2001 error message indicates that the compiler is trying to link against the incorrect version of “mclmcrrt.lib” file.

For example, if the selected compiler is LCC and there exists a copy of the “mclmcrrt.lib” file belonging to some other compiler in the current working directory, then the LNK2001 error will occur due to conflicting compiler symbols.

Verify whether there exists a “mclmcrrt.lib” file in the current directory. If so, you can remove the file since it is not necessary to have this file in the current working directory. The MATLAB Compiler will automatically pick up the correct “mclmcrrt.lib” file depending on the selected compiler during compile time.

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: Do I receive the LNK2001 error when trying to compile a simple MATLAB program using MATLAB Compiler 4.8 (R2008b)

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)