Reports the MATLAB-installed functions used in the code that are (partially) MATLAB Coder-compatible or not. Three levels of support for C/C++ code generation can be reported: Fully supported, supported with limitations, and not supported. The violations in the report contain links to the documentation of the MATLAB-installed functions so that you can easily check the limitations (if any) or find alternatives that are (more) Coder-compatible.
SupportLevel (string): Allowed values are:
Supported: Reports calls to MATLAB-installed functions that are Coder-compatible without limitations or sidenotes. Using this setting makes it so that the check does not fail (since only supported features are reported). This means that in order to see the results for this check when this parameter value is used, you have to enable Include passed checks in the Report tab of the GUI.
Supported with limitations: Reports calls to MATLAB-installed functions that are Coder-compatible with limitations or sidenotes. The link to the documentation provided in the report can help you to quickly find these limitations and act accordingly.
Unsupported: Reports calls to MATLAB-installed functions without support for C/C++ code generation. The link to the documentation provided in the report may help you to find alternatives for these functions that are Coder-compatible.
Release (string): The MATLAB release for which you would like to check Coder-compatibility. Allowed values are
'MostRecent'option automatically applies the level of Coder-compatibility of the most recent MATLAB release supported by CC4M.
ViolationUniqueness(list): Specify if you want to see unique violations global, per file or all violations. By default, this parameter is set to
If you would like to see the level of Coder-compatibility for every MATLAB-installed function call, you can configure this check multiple times, but with different settings for the SupportLevel parameter. That way, the report generated after the check contains a separate table for each of the support levels. For more information on configuring the same check multiple times, see section Multiple configurations per check.
This check only reports known MATLAB-installed functions. This means
that if you use a MATLAB-installed function that was introduced in a
MATLAB release after the one you are using, it is not reported by this
check. You can use
checkBuiltinFunctionCompatibility for that. For
example if you set the Release parameter to R2020b and you are using
R2017b. Conversely, if you use a MATLAB-installed function that was
introduced in a MATLAB release after the one you have configured under
Release, but that is known in the MATLAB release you are using, the
function call will be reported. This is because the function is not
supported in the configured MATLAB release, so it is also not
Coder-compatible. For example, you set the Release parameter to
R2017b and you are using R2020b to run the check.