coder.ReportInfo - Code generation report information - MATLAB (original) (raw)

coder.ReportInfo Properties

Code generation report information

The coder.ReportInfo properties contain information about code generation settings, input files, generated files, code generation messages, code insights, and build logs. Allcoder.ReportInfo properties are read-only. You can use dot notation to query these properties.

You do not directly create a coder.ReportInfo object. When you export code generation report information to a variable in your base MATLAB® workspace, a coder.ReportInfo object is automatically created that contains this information. See Access Code Generation Report Information Programmatically.

Note

Your MATLAB source code is included in the properties of thecoder.ReportInfo object.

Summary — Summary of code generation

coder.Summary object

This property is read-only.

A summary of code generation including information about code generation success, path to the code generation output, toolbox licenses checked out during code generation, toolchain, and build configuration, specified as a coder.Summary object. See coder.Summary Properties.

InputFiles — Input files for code generation

array of coder.CodeFile objects | array of coder.File objects

This property is read-only.

Heterogeneous array containing descriptions of input files for code generation. Each element of the array contains a description of one input file.

• If an input file contains text, the corresponding array element is acoder.CodeFile object. See coder.CodeFile Properties.
• If an input file does not contain text (for example, a P-coded file), the corresponding array element is a coder.File object. See coder.File Properties.

GeneratedFiles — Generated files

array of coder.CodeFile objects | array of coder.File objects

This property is read-only.

Heterogeneous array containing descriptions of generated files. Each element of the array contains a description of one generated file.

• If the generated file contains text, the corresponding array element is acoder.CodeFile object. See coder.CodeFile Properties.
• If the generated file does not contain text (for example, a P-coded file or a precompiled library), the corresponding array element is acoder.File object. See coder.File Properties.

Functions — MATLAB functions and methods used in code generation

array of coder.Function objects | array of coder.Method objects

This property is read-only.

Heterogeneous array containing descriptions of MATLAB functions and methods that are used in code generation. Each element of the array contains a description of one function or method.

• Array elements containing descriptions of functions arecoder.Function objects. See coder.Function Properties.
• Array elements containing descriptions of methods arecoder.Method objects. See coder.Method Properties.

Messages — Code generation error, warning, and informational messages

array of coder.Message objects

This property is read-only.

Array containing descriptions of error, warning, and informational messages produced during code generation. Each element of the array is a coder.Message object that contains a description of one message. See coder.Message Properties.

CodeInsights — Messages about potential issues with the generated code

array of coder.Message objects

This property is read-only.

Array containing descriptions of messages about potential issues with the generated code. Each element of the array is a coder.Message object that contains a description of one message. These messages also appear in the code generation reportCode Insights tab. See coder.Message Properties.

BuildLogs — Build logs produced during code generation

array of coder.BuildLog objects

Array containing build logs produced during code generation. The build logs contain compilation and linking errors and warnings. Each element of the array is acoder.BuildLog object that contains the type and text of one build log. These messages also appear in the code generation report Build Logs tab. See coder.BuildLog Properties.

Version History

Introduced in R2019a