Why does the MATLAB Add-in for Visual Studio fail when a project is created in folder with a long name?

Why does the MATLAB Add-in for Visual Studio fail when a project is created in folder with a long name?

My MATLAB Project within Visual Studio fails if I am trying to create an "Shared M-DLL" application type in a directory with a long name. The error occurs when building and the message is:

 Performing Custom Build Step on "T:\1551596\MatLabBug2\MatLabBug2\this_is_a_long_folder_name_to_confuse_and_befuddle_mcc\myOtherFunc.m"

 Compiler version: 3.0

 Error: The options specified will not generate any output files.

 Please use one of the following options to generate an executable output file:

   -x (generates a MEX-file executable using C)

   -m (generates a stand-alone executable using C)

   -p (generates a stand-alone executable using C++)

   -S (generates a Simulink MEX S-function using C)

   -B sgl (generates a stand-alone graphics library executable using C (requires the SGL))

   -B sglcpp (generates a stand-alone graphics library executable using C++ (requires the SGL))

   -B pcode (generates a MATLAB P-code file)

 Or type mcc -? for more usage information.

 Compiler version: 3.0

 Error: The options specified will not generate any output files.

 Please use one of the following options to generate an executable output file:

   -x (generates a MEX-file executable using C)

   -m (generates a stand-alone executable using C)

   -p (generates a stand-alone executable using C++)

   -S (generates a Simulink MEX S-function using C)

   -B sgl (generates a stand-alone graphics library executable using C (requires the SGL))

   -B sglcpp (generates a stand-alone graphics library executable using C++ (requires the SGL))

   -B pcode (generates a MATLAB P-code file)

 Or type mcc -? for more usage information.

 Error executing c:\winnt\system32\cmd.exe.

 testmdll.dll - 2 error(s), 0 warning(s)

Answer 1

[MathWorks Support Team]

This has been verified as a bug with the MATLAB Add-in for Visual Studio when creating a project in a folder with a long name.

Currently, to work around this issue, try running the mcc.mak using nmake.