MATLAB: Does the standalone application not load a shared library built using the MATLAB Compiler

2003corruptdllerrorfatalfileinvalidlcclibrarylnk1136loadMATLAB Compilermsvc

I use the following MCC command to build a shared library using the MATLAB Compiler:

mcc -C -G -W lib:MCCviewerClient -T link:lib client_multical360.m client_feature_list_export.m get_feature_data.m handle_external_request.m

where, the last four parameters are the interfaces I want to make available to an external application.

I then create a standalone application using the Microsoft Visual Studio .NET 2003 IDE that implicitly links against the MATLAB Compiler generated library. However, when this application is executed, the library generated by the MATLAB Compiler is not loaded into the process.

Best Answer

This change has been incorporated into the documentation in Release 2011a (R2011a). For previous releases, read below for any additional information:

This issue is caused by an incompatibility between the import libraries of different compilers.

The MATLAB Compiler generated shared library was built using the LCC compiler, while the standalone application uses the Microsoft Visual Studio .NET 2003 compiler.

There are two possible workarounds to this issue:

1. Use the same compiler to create the shared library, and to compile/link the standalone application.

2. If there is a need to use different compilers in the different stages, then compiler-specific tools can be used to generate import libraries for other compilers.

For instance, LCC provides a tool called lcc_implib.exe in the MATLABROOT\sys\lcc\bin folder, where MATLABROOT is the output of typing the following command at the MATLAB prompt:

matlabroot

This tool can generate an LCC-compatible import library for a DLL built with any compiler.

Related Solutions

MATLAB: Does the C++ MFC application crash upon termination when the application uses the MATLAB Component Runtime in MATLAB 7.1 (R14SP3)

You can avoid this problem by linking your MFC project to mclmcrrt.lib instead of linking to mclmcr.lib. The mclmcrrt library is located in the following directory:

 $MATLABROOT\extern\lib\win32\microsoft\msvc71

where $MATLABROOT is the MATLAB installation directory as returned by typing

 matlabroot

at the MATLAB command prompt.

When using MS Visual Studio you can typically specify the llbrary to link to by right-clicking your project in the Solution Explorer and selecting "Properties" from the context menu and navigating to "Linker", "Input," and "Additional Dependencies."

The dependencies for the project are mclmcrrt.lib as well as the the library you generated with MATLAB Compiler, which also has a ".lib" extension.

MATLAB: Do I get an error mentioning “ntstatus 0xc0150002” when deploying a driver application that calls a shared library created with the MATLAB Compiler 4.9 (R2008b) using a MSVC compiler

Side-by-Side errors are usually caused by the MSVC Runtime Libraries being missing on the deployment machine. If you installed the MSVC Runtime Libraries, a possible cause for this error message is that you are distributing the debug version of your driver application.

The debug version of the MSVC Runtime Libraries is only included by the MSVC development environment. To work around this issue, make sure you distribute the "Release" version of your driver application and make sure that the MSVC Runtime Libraries are installed.

Best Answer

Related Solutions

MATLAB: Does the C++ MFC application crash upon termination when the application uses the MATLAB Component Runtime in MATLAB 7.1 (R14SP3)

MATLAB: Do I get an error mentioning “ntstatus 0xc0150002” when deploying a driver application that calls a shared library created with the MATLAB Compiler 4.9 (R2008b) using a MSVC compiler

Related Question