In our project we create standalone executables from M files using the Matlab compiler. The executables are created by our automated build server using MSBuild . To do this, MSBuild calls MCC from the windows commandline. It took some time to get this up & running, but now this actually works very nicely.
The issue that we encounter is that sometimes the executables cannot perform certain functions (eg. image processing) because files needed for this are missing from the CTF file. Detailed analysis shows that the cause of this is a failing license checkout for e.g. the image processing toolbox during the MCC build (in our company we have a large set of floating licenses, but sometimes we can run out of them).
In this case, I would expect MCC to fail. But instead it outputs a detailed error message (error -4) to the command prompt and continues building like nothing ever happened: result is an application that appears to built correctly, but lacks certain functionality.
The call to MCC includes the following flags:
-v [Main File]
-a [Included M files]
As you can see, all known warnings are already returned as error.
Is there a way to also have license checkout failures return as an error? Or is there another way (eg. return value?) through which we can detect this?