MATLAB: MATLAB Coder “Style” Options when Generating .mex-File

codegenmatlab codermex

When using the MATLAB Coder to create a .mex-file, the "Code Style" settings in the GUI settings menu are not available. They only appear to be available when generating a Static Library, Dynamic Library, or Executable.

My specific issue with this is that I not longer have access to the "Maximum Identifier Length" setting. Because I can't increase this from 31, some fields in structures in my code are being mangled, which means that the typedefs don't match external code that is trying to interface with those typedefs.

Is there any other way to change the maximum identifier length setting?

Best Answer

Using coder.cstructname is one means of integrating structs which are also used in external code. You could define the structure type in a header file, customDefs.h and then include the definition of that header in your MATLAB code like so:

function y = foom(x)
coder.cstructname(x, 'customImportedStruct', 'extern', 'HeaderFile', 'customDefs.h');
y = 2*x.fieldWithVeryVeryVeryVeryLongName;

and generate code:

str.fieldWithVeryVeryVeryVeryLongName = 12; codegen foom -args str -c -report

You will see that the field names are preserved and that the file foo_types.h includes customDefs.h.

This approach also lets you hand-tailor the typedef for your structure so that it is predictable and consistent across the generated code and your external code.

Related Solutions

MATLAB: Returning mxArray* as void* from a C shared library

Passing mxArrays via void pointers is likely to cause problems in your code (memory leaks and crashes). The calllib code has special handling for transferring ownership of mxArrays when needed but it can't do this when they are passed as a void pointer. If you whish to avoid including mex.h I suggest adding a forward deceleration for mxArray to your header file instead:

typedef struct mxArray mxArray;

MATLAB: Stack overflow using the generated C++ code

Finally I got the solution. The issue is not static variable. The issue is that the function variable size is too big.

Here is the solution: when generate the code. in the memory configuration, by default Stake usage max is 200,000. But for MSVC, the default is 100,000. So I reduce it to 50,000 (consider other functions use another 50,000). Also I enable "Variable-sizing". And change the dynamic memory allocation threshold to 4000 (by default,it is 65,536). I use 4000 because it has many variables with double[600] type (size of 4800), thus I enforce the tool to use static variable instead of regular variable. Once it is done. No stack overflow issue anymore.

Thanks for the help from Denis.

Best Answer

Related Solutions

MATLAB: Returning mxArray* as void* from a C shared library

MATLAB: Stack overflow using the generated C++ code

Related Question