Mixing compiled matlab shared libraries with mex code.

5 views (last 30 days)
Chris Volpe
Chris Volpe on 10 Jul 2015
Commented: Adam Callens on 5 Apr 2017
I have some matlab code that invokes mex code (compiled with VS2013). I have both Debug and Release builds of the mex code, and can adjust my system (windows) PATH prior to starting up Matlab so that when I invoke that mex function from Matlab, it invokes the desired build configuration.
Now, I want to bundle up the matlab code into a DLL with the matlab compiler. If I don't add the mex DLLs as additional files required in the .PRJ GUI, the compiled matlab code can't find it at runtime. But if I do add the mex code, the resulting compiled matlab library is "build configuration dependent" -- i.e. if I added the debug build of the mex code, the library won't work from a release build of an executable program client of the compiled matlab library, and vice versa. So, what I want to do is to get a compiled matlab library that doesn't know about the mex code, but which can find it at runtime using the normal PATH-related load procedure, since the desired mex DLL will be in the same folder (Debug or Release) as the executable program client of the compiled matlab library. But I don't seem to be able to find a way to accomplish this goal. Any thoughts?

Answers (2)

Dasharath Gulvady
Dasharath Gulvady on 21 Jul 2015
The best way to do this is to place the MEX file in a relative path to "ctfroot":
Normally, in Windows, "ctfroot" is %temp%\username\mcrCachexx.
Adam Callens
Adam Callens on 5 Apr 2017
What about the A.mexw64.auth file that is not generated if you don't include the mex file in the mcc build. How do you get around that?

Sign in to comment.

Chris Volpe
Chris Volpe on 18 Sep 2015
I solved my issue with a three-step process. First, I changed my VS2013 project settings for Project B such that it creates B_debug.dll and B_release.dll. Second, I added B_release.dll to the additional required files for the matlab compiler. Third, I changed my VS2013 project settings for A.mexw64 such that the target file gets built into the same folder as B.dll. I had previously set all my mex code to be built into a "MEX" subfolder so that I could add this subfolder to my Matlab path and non bog down Matlab with searching through a binaries folder that contained all sorts of 3rd-party DLLs. Putting them in the same folder ensures that when I add them both in the deploytool GUI, they'll end up in the same relative path off the expanded ctfroot temp folder at runtime, ensuring that B_release.dll can be found at runtime.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!