How to debug generated mex codes
95 views (last 30 days)
I am trying to build an application in C++ using Visual Studio 2017. I have added paths in the directory as recommended https://www.youtube.com/watch?reload=9&v=vQ5aIxCX3To. Somehow I get an error - libmx.dll not found. I tried following - I copied this dll from bin\win64 and pasted it in the solution directory. After this I got error saying a different dll is missing. Then I tried to copy entire bin\win64 in a different location and added that path. Still the same error. Please help me resolve the issue.
When I generate mex from my code it works just fine, but I can't run the code in Visual Studio-17. Thanks
Ryan Livingston on 26 Oct 2018
Moved from comment To debug generated MEX code, just pass the -g option to codegen and that will compile a debug MEX file. You can then debug that MEX code by following the same process you'd use for debugging hand-written MEX files:
In short, you compile and run the MEX in MATLAB and attach Visual Studio to MATLAB, stopping when the MEX code is executed.
Note that the -g option is the same as the Coder config setting EnableDebugging:
More Answers (1)
Ryan Livingston on 23 Oct 2018
It sounds like you are generating MEX code. MEX code assumes that MATLAB is present and as a result it may have a large number of dependencies. For this reason, MEX code should be compiled in MATLAB with MATLAB Coder or the MEX command. Compiling it with Visual Studio outside of MATLAB is not recommended.
Instead you can choose one of the standalone code generation options to use inside of Visual Studio. You can do that with:
cfg = coder.config('lib'); % or 'dll'
codegen -config cfg myFunction.m -args ...
and then use that code in Visual Studio. More info on generating standalone code:
Here's an example of using the generated code in Visual Studio:
Finally, the Deployment category in the documentation may be of interest: