Maximum allowable MATLAB Runtime version for applications compiled with MATLAB R2023b
27.5K reputation · 10 Apr 2022, 07:12 UTC
Goal: Reduce the download size of a low‑traffic standalone application by distributing a newer MATLAB Runtime (MCR) version instead of the exact MCR that matches the MATLAB release used for compilation.
Constraint: The MATLAB Compiler documentation states that the MCR is not guaranteed to be forward‑compatible; running code with an MCR from a different release may produce undefined behavior or startup errors, especially when toolbox‑specific functions are involved. Licensing terms also require that the distributed MCR be the version authorized for the compiled application.
Uncertainty: It is unclear whether using a newer MCR is permissible under the license and whether the risk of incompatibility is acceptable for low‑traffic workloads.
Is it allowed by the MATLAB Runtime license to ship an MCR version newer than the one matching the compiler release?
What specific failures have been observed when an application compiled with MATLAB R2023b is executed with MCR R2024a?
Does MathWorks provide any official guidance on forward‑compatible MCR usage for low‑traffic deployments?