Main Content

Functions Not Supported for Compilation by MATLAB Compiler and MATLAB Compiler SDK

R2026b

When you compile MATLAB® code with MATLAB Compiler™ or MATLAB Compiler SDK™, some MATLAB functions and programs are not supported in deployed applications. These items typically require the MATLAB desktop, interactive development features, or Simulink® authoring workflows that are not available in deployed mode.

Caution

This page is not a complete list of all limitations. Support depends on your MATLAB release, the products you use, and your deployment target.

For the current supported products and functionality, see Support for MATLAB, Simulink, and Toolboxes.

If compilation fails or you see warnings about missing or unsupported symbols, see Diagnose and Fix Issues When Compiling MATLAB Code.

Interactive Debugger Functions

The MATLAB debugger is a desktop-only interactive tool. Deployed applications run without the MATLAB desktop and cannot pause execution for interactive inspection.

  • dbclear

  • dbcont

  • dbdown

  • dbquit

  • dbstack

  • dbstatus

  • dbstep

  • dbstop

  • dbtype

  • dbup

  • keyboard

Desktop Environment and Editor Functions

These functions require the MATLAB desktop, editor, or Command Window, none of which are present in deployed mode.

  • commandwindow

  • doc

  • echo

  • edit

  • help

  • home

  • inspect

  • more

  • open

  • type

Path and Session Management

Deployed applications use a fixed, encrypted file system. Functions that manipulate the MATLAB path or session state cannot operate as they do in MATLAB.

  • inmem

  • mislocked

  • mlock

  • munlock

  • pack

  • quit

  • rehash

  • restoredefaultpath

Source Code Analysis Tools

These functions require access to raw MATLAB source files. In deployed mode, source code is encrypted and not available for inspection.

  • checkcode

  • depfun

  • pcode

  • profile

  • profsave

  • publish

Interactive Graphics Tools

These functions open interactive desktop tools for editing plots or colormaps. They are not available in headless or deployed environments.

  • colormapeditor

  • export

  • linkdata

  • plotedit

Dynamic Script Execution

run executes a script by file path. In deployed mode, scripts must be included in the archive at build time. Dynamic discovery of MATLAB files at runtime is not supported.

  • run

Project-Based Unit Testing

fromProject requires a MATLAB project context, which is not available in deployed mode.

  • matlab.unittest.TestSuite.fromProject

Simulink Authoring and Debugging

Simulink model authoring, editing, and debugging require the Simulink desktop environment, which is not available in deployed mode.

  • add_block

  • add_line

  • close_system

  • delete_block

  • delete_line

  • get_param

  • linmod

  • load_system

  • new_system

  • open_system

  • segment

  • set_param

  • sldebug