MATLAB Compiler Dependency Log Changes in R2022b: Missing File Warnings Omitted

Resolving Missing File Warnings and Runtime Gaps

In MATLAB R2022b, the mcc compiler no longer emits explicit "File not found" warnings for files added via the -a flag in the main dependency log. To restore visibility into missing files, you must manually cross-reference your input list with the mccExcludedFiles.log, as there is currently no compiler flag to restore the legacy warning behavior.

Recovering Missing File Diagnostics

Because mccExcludedFiles.log lists all files the analyzer decided to omit—regardless of whether they were missing or intentionally excluded—use a pre-build verification step to isolate path errors:

• Pre-build Validation: Run a MATLAB script to assert the existence of all -a files before calling the compiler.
• Verification Logic: Use exist(filename, 'file') in a loop over your dependency list. If any return 0, the build should be aborted before mcc is invoked.
• Log Analysis: If a runtime failure occurs, compare the list of files passed to -a against the entries in mccExcludedFiles.log. Any file present in the latter that was not intentionally excluded is likely missing from the build path.

Correlating Builds with Production Server (MPS)

When the default correlation ID is not propagated, you must embed a unique identifier into the compiled artifact to link the mcc build to the MPS deployment:

1. Embed Versioning: Use the -W flag during compilation to include a version string (e.g., -W 'main:myApp,-v,1.2.3').
2. Runtime Identification: Configure the MPS logger to include this identifier by setting the MPS_DYNAMIC_PROPERTY for buildId or passing a custom property via -R "-DmyBuildID=...".

Capturing Early Runtime Initialization Failures

The -R "-logfile,runtime.log" option only activates after the MATLAB Runtime (MCR) has successfully initialized. To capture failures occurring before this point (such as missing MCR libraries or version mismatches), redirect the executable's standard error stream at the OS level:

# Linux/macOS
./myApp 2> init_err.log

# Windows (Cmd)
myApp.exe 2> init_err.log

This captures the low-level loader errors that the MCR logger cannot reach. Alternatively, set the MCR_LOG_FILE environment variable before launching the executable to capture initialization events.

Assumptions and Diagnostics

This guidance assumes the use of the mcc command-line tool in R2022b. If you are using the Application Compiler App, these flags correspond to the "Files required for your application to run" section. To provide a more specific correlation strategy for MPS, please specify if you are using a custom deployment script or the standard mcc -W workflow.