How do I make sure that all the dependencies of shared libraries are included in a compiler build?

I'm trying to make an executable of my MATLAB app which uses some shared libraries (camera drivers). The way I deal with handling libraries, I created a prototype *.m file and then use it when loading a library (all using the loadlibrary function).

The code runs fine from MATLAB but as soon as I build it using the MATLAB Compiler it throws an error:

Error using loadlibrary (line 419)
The specified module could not be found.

All that even though I've specified that the additional include and header folders in the build preferences.

I suspect that it has to do with the fact that somehow not all of the files in the shared library folders are included in the build.

Does anyone know the proper way to do shared libraries with MATLAB and its compiler?

[Adam]

Are you including the dll or lib or whatever the library is? Depending exactly what form your 3rd party code is in you should just need to include a built dll from the compiler. You shouldn't need headers and other code files if that is the case.

[Kuba]

The drivers have an include folder with some header files and a bin folder with a bunch of dll's and one .lib file. Normally I just call loadlibrary with the name of the main thing in the folder, without extension (the loadlibrary finds it fine when I run it with Matlab). When I specified it should take the .lib it didn't work so I assume it usually takes the dll.

[Image Analyst]

Like I said below I think you need the full filename. Put it in some known place on the target computer because of MATLAB's quirky way of putting stuff you include with their deploytool in some weird secret hidden folder. I assume you tried the -a option of mcc/deploytool to include all the files you need (though you don't need to do that if you put them in a known location like I suggested).

Answer 1

[Image Analyst]

Make sure you specify the full path (folder + base file name) of your DLL to loadlibrary(). Call exist(DLLFileName, 'file') before you call loadlibrary to see that it's actually there before you call loadlibrary().

Please see my attached file where I read a Measurement Computing device's digital I/O pin via load library and a DLL call. Also attached is how I make the prototype file.

[Kuba]

Sorry it took me so long to respond - the thing takes centuries to compile (btw, is there no way of forcing matlab compiler to use more than one core? It would be so much faster if it used all 16 I have available...)

I changed all paths to full ones instead of relative and the problem still persists. The file does't even run properly on the same machine I compiled it.

[Image Analyst]

The compiler costs a fortune so I suggest you call them and get advice for why it takes so long. Might as well get your money's worth.

I have programs that are 5-10 thousand lines long and they compile in 1.5 to 3 minutes. Of course that's half of what it used to be now that I have SSDs (solid state drives) instead of HDDs.

[Adam]

Which version of Matlab do you have? I certainly noticed that Matlab Compiler took forever to compile even a simple UI with one button calling a single function in 2013b (I'm not sure which version the Compiler Toolbox was), but in 2014a it is a lot faster.