Main Content

About theMATLABRuntime

TheMATLAB®Runtimeis a standalone set of shared libraries, MATLAB code, and other files that enables the execution of MATLAB files on computers without an installed version of MATLAB. Applications that use artifacts built withMATLAB Compiler SDK™require access to an appropriate version of theMATLAB Runtimeto run.

End-users of compiled artifacts without access to MATLAB must install theMATLAB Runtimeon their computers or know the location of a network-installedMATLAB Runtime. The installers generated by the compiler apps may include theMATLAB Runtimeinstaller. If you compiled your artifact usingmcc, you should direct your end-users to download theMATLAB Runtimeinstaller from the website//www.tianjin-qmedu.com/products/compiler/mcr.

SeeInstall and Configure MATLAB Runtimefor more information.

How is theMATLABRuntimeDifferent fromMATLAB?

TheMATLAB Runtimediffers from MATLAB in several important ways:

  • In theMATLAB Runtime, MATLAB files are encrypted and immutable.

  • MATLAB has a desktop graphical interface. TheMATLAB Runtimehas all the MATLAB functionality without the graphical interface.

  • TheMATLAB Runtimeis version-specific. You must run your applications with the version of theMATLAB Runtimeassociated with the version ofMATLAB Compiler SDKwith which it was created. For example, if you compiled an application using version 6.3 (R2016b) ofMATLAB Compiler™, users who do not have MATLAB installed must have version 9.1 of theMATLAB Runtimeinstalled. Usemcrversion返回的版本号MATLAB Runtime.

  • The MATLAB paths in aMATLAB Runtimeinstance are fixed and cannot be changed. To change them, you must first customize them within MATLAB.

Performance Considerations and theMATLABRuntime

MATLAB Compiler SDKwas designed to work with a large range of applications that use the MATLAB programming language. Because of this, run-time libraries are large.

Since theMATLAB Runtimetechnology provides full support for the MATLAB language, including the Java®programming language, starting a compiled application takes approximately the same amount of time as starting MATLAB. The amount of resources consumed by theMATLAB Runtimeis necessary in order to retain the power and functionality of a full version of MATLAB.

Calls into theMATLAB Runtimeare serialized so calls into theMATLAB Runtimeare threadsafe. This can impact performance.