Simulink Compiler Error when Visual Studio 2015 Pro is installed

After I started to use Visual Studio 2015 Pro as my compiler, I encountered problem in running my .slx file. This file consists of mostly the basic simulink blocks and a stateflow chart. The error I had receivied can be seen below.

### Linking ... link.exe /nologo /dll /MANIFEST /OPT:NOREF /export:mexFunction /export:mexfilerequiredapiversion /OUT:MCL_sfun.mexw64 /map:"MCL_sfun.map" @MCL_sfun.mol LINK : fatal error LNK1181: cannot open input file 'Files\MATLAB\R2020b\extern\lib\win64\microsoft.obj' NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\Bin\amd64\link.exe"' : return code '0x49d' Stop.

From the error message, I sense that it is related to compiling s functions, however there is no s-function on my model. Furthermore, this error is not gotten when the MinGW64 is the compiler. What can be the cause of this error? Also, I am sure that I had installed C/C++ programming language in Visual Studio 2015 Pro. Thank you in advcance.

Kind Regards,

İlkay

Answer 1

[surya venu]

Hi,

This error is related to compiling s-functions, which are used in Simulink to implement custom functionality. Even though you mentioned that there are no s-functions in your model, the error message suggests that there might be a dependency on an s-function or a library that contains s-function code.

The fact that this error does not occur when using MinGW64 as the compiler suggests that the issue might be related to the configuration of Visual Studio 2015 Pro. It is possible that there is a missing or incorrectly configured component in the Visual Studio installation that is required for compiling s-functions.

One possible solution is to update Visual Studio 2015 Pro to the latest version, which includes bug fixes and improvements to the compiler and linker. Additionally, you may want to check the configuration of the Visual Studio project and ensure that all required libraries and dependencies are correctly specified.

Another possible solution is to use a different version of Visual Studio or a different compiler, such as MinGW64, which you mentioned works without issues. This may require modifying the Simulink model or the Visual Studio project to ensure compatibility with the new compiler.

Hope it helps.