Hi Lukai, note that you have generated code for a MEX function (aka config:mex) as opposed to standalone (aka config:lib). I am guessing that the reason why you are compiling with Visual Studio is so that you can use Visual Studio debugger to step through your mex function in the debugger.
If that is the case, then you don't need to use Visual Studio. Instead, simply generate the mex function with debugging information by passing the "-g" flag to codegen command, and then attach Visual Studio debugger to MATLAB, open the source code of the generated MEX function and then place a breakpoint. Once you execute the mex function, your breakpoint should hit.
See this page:
https://www.mathworks.com/matlabcentral/answers/91908-how-do-i-debug-a-matlab-c-c-mex-file-in-microsoft-visual-studio-2005
but don't do the "mex -g" step, instead do "codegen ..... -g..." to produce a mex function.
All the above is related to getting mex function debugging to work.
If you want to build generated C code as a mex function for some other reason, the way I'd go about that is to use the "-v" option to mex (you'd need to add it to mex options in the autogenerated .mk file in codege/mex/yourpoject/) and then seeing what parameters does the mex command pass to the C compiler. Then you can replicate the same parameters (-I, -D etc) in your Visual Studio project.
All that being said, if your intent is different from just being able to debug your mex function, then please add a comment describing the use case, we'll go from there.
Thanks,
Denis
