MATLAB: Am I not able to successfully build applications that use MATLAB Compiler generated C++ code that includes ODE routines

cdllfunctionlibrarymathMATLAB C/C++ Math Libraryodeshared

I have a MATLAB application, which uses the ODE functions. When I compile this MATLAB application to C++ code and include it in my own C++ project, I get the following linking errors when building:

 callode15.obj : error LNK2001: unresolved external symbol "class mwArray  __cdecl Node15s(int,class mwVarargout,class mwArray,class mwArray,class mwArray,class mwArray,class mwVarargin)" (?Node15s@@YA?AVmwArray@@HVmwVarargout@@V1@111VmwVarargin@@@Z) 
 callode15.obj : error LNK2001: unresolved external symbol "class mwArray  __cdecl Nodeset(int,class mwVarargin)" (?Nodeset@@YA?AVmwArray@@HVmwVarargin@@@Z) 
 cppcall.exe : fatal error LNK1120: 2 unresolved externals

I noticed that a couple of header files are generated for the ODE15s (which is the specific function I am using) and the ODESET functions, however there are no C++ source files generated.

Best Answer

At this time, the only workaround would be to compile your application to a C shared library, which you can call from your project.

For information on doing this, see the Related Solution listed below.

Related Solutions

MATLAB: What libraries should I link against when creating a managed application which calls a MATLAB Compiler 4.5 (R2006b) generated shared library

The only MathWorks libraries which you should link against when calling a C/C++ shared library are the appropriate mclmcrrt library for your platform and version and the shared library which was generated by MATLAB Compiler. This is because all access to the MATLAB Compiler Runtime (MCR) (including the creation and access of mxArrays) must be marshaled through the mclmcrrt library for thread safety reasons.

For example on 32-bit Windows for MATLAB Compiler 4.6 (R2007a) this means linking against mwmclmcrrt76.dll. If you are implicitly linking (using load time dynamic linking) this means linking against the import library mclmcrrt.lib.

On a 32-bit Linux platform for MATLAB Compiler 4.6 (R2007a) this means linking against libmwmcrmcrrtso.7.6.

For explicit linking (run-time dynamic linking) the situation is more complicated because of a compatibility layer introduced in the mxArray API in MATLAB 7.3 (R2006b) for support of large arrays. The changes to the API required creation of two sets of functions *_700 and *_730 (for example mxCreateDoubleMatrix_700 and mxCreateDoubleMatrix_730). In general, you should use the *_730 functions for all applications which call MATLAB Compiler generated shared libraries. The *_700 functions are for backward compatibility.

In the previous example, where explicit linking is used from C#, with MATLAB Compiler 4.6 (R2007a) the import statement should read

 [DllImport("mclmcrrt76.dll")]
 private static extern IntPtr mxCreateDoubleMatrix_730([In]Int32 numRows, [In]Int32 numCols, [In]Int32 mxComplexity);

MATLAB: Do I receive link errors (LNK2019) when compiling in Microsoft Visual C++ 2005

These are the linking errors caused when the compiler tries to link your application with the appropriate libraries that define all the symbols. Just providing the path to these libraries (lib files) is not enough. You will need to add them manually to your Visual Studio project in order to resolve all the symbols.

In order to include the required libraries, you will need to add them under Project -> Properties -> Linker -> Input -> Additional dependencies:

For example: mclmcrrt.lib, mclmcr.lib, libmatrixp.lib (see included screen shot).

So when getting this type of linking errors, try to identify the function (symbol) that cannot be resolved and see which library it belongs to, then add the library to the linker list as explained above. To identify the function, search your source code for its name, for example mclTerminateApplication. Then right click on the function and click on "Go To Definition". If all path settings are set right, this will open the file mclmcrrt.h, this will tell you that you need to add the mclmcrrt.lib file to the linker list.

If you are compiling using the MATLAB MBUILD command and get this type of error, try to identify the library that contains the missing symbols as explained above and add the library to the MBUILD command.

Best Answer

Related Solutions

MATLAB: What libraries should I link against when creating a managed application which calls a MATLAB Compiler 4.5 (R2006b) generated shared library

MATLAB: Do I receive link errors (LNK2019) when compiling in Microsoft Visual C++ 2005

Related Question