TOML Properties for Deployment Projects
R2026bThe matlab.toml
definition file type allows you to define and manage your entire project configuration in a
single TOML file. This format is easier to review and merge under source control, and you can
edit it directly in the MATLAB® editor. For more information, see MATLAB Projects TOML Format (.toml).
When you edit a Compiler Task using the user interface, the project logs this information
to the matlab.toml file. The following tables provide examples of the TOML syntax used in deployment projects,
where properties are grouped by deployment target. For the full list of properties defined in
the matlab.toml file, see matlab.toml.
The following TOML code configures the compiler task
StandaloneDesktopApp1 to create a standalone application and
installer.
Note
Properties that accept file or folder paths support paths relative to the project folder or absolute paths.
[compiler.standalone.build] Properties
This table shows the TOML properties for the compiler.build.standaloneApplication and compiler.build.standaloneWindowsApplication deployment targets.
| Property | Description | Default value |
|---|---|---|
| Name of the generated application. Names must begin with a letter or underscore character and contain only alphanumeric characters or underscores. |
|
| Path to a help file containing help text for the end user of the application. |
|
| Path to the icon image that serves as the icon for the executable.
Accepted image types are |
|
| Path to the splash screen image displayed when the application
starts. Accepted image types are |
|
| Path to the main file of the application. |
|
| Additional files and folders to include. |
|
| Name of the log file for MATLAB Runtime. |
|
| Flag to embed the deployable archive in the generated executable. |
|
| Flag to interpret command line inputs as numeric MATLAB doubles. |
|
| Flag to suppress the Windows® command shell when running the application. | True for standalone Windows applications; false otherwise |
| Version of the generated executable. Uses semantic versioning format. |
|
| Flag to automatically include data files discovered by dependency analysis. |
|
| Path to a file containing an external encryption key. |
|
| Flag to obfuscate folder structures and file names in the deployable
archive, place user code and data in |
|
| Path to a JSON manifest file specifying secret keys to embed in the deployable archive. |
|
| Support packages to include. Value can be
|
|
| Flag to display progress information during the build process. |
|
| Path to the output folder. |
|
[compiler.standalone.package] Properties
This table shows the TOML properties for the compiler.package.installer deployment target, which lets you create
application installers.
| Property | Description | Value |
|---|---|---|
| Additional files and folders to install with the application. |
|
| Path to an image that serves as the icon in the list of Windows applications in settings. |
|
| Name of the installed application. |
|
| Name of the company that created the application. |
|
| Email address of the application author. |
|
| Name of the application author. |
|
| Default folder where the installer installs the application. |
|
| Detailed description of the application. |
|
| Notes about additional requirements for using the application. |
|
| Path to an image file used as the icon for the installed application. |
|
| Path to an image file used as the installer logo. The installer resizes the logo to 112-by-290 pixels. |
|
| Name of the installer file. The extension is determined by the operating system. |
|
| Label and category for the installer splash screen image. |
|
| Path to the folder where the installer is saved. |
|
| Installer file type. Value can be |
|
| MATLAB Runtime delivery option. Value can be |
|
| Path to a file or folder for which the installer creates a shortcut at install time. |
|
| Summary description of the application. |
|
| Version number of the installed application. |
|
| Flag to display progress information during the packaging process. |
|
[compiler.webApp.build] Properties
This table shows the TOML properties for the compiler.build.webAppArchive deployment target.
| Property | Description | Default value |
|---|---|---|
| Path to the main file of the application. |
|
| Additional files and folders to include. |
|
| Name of the deployable archive. |
|
| Flag to automatically include data files discovered by dependency analysis. |
|
| Path to a file containing an external encryption key. |
|
| Flag to obfuscate folder structures and file names in the deployable
archive, place user code and data in |
|
| Path to the output folder. |
|
| Path to a JSON manifest file specifying secret keys to embed in the deployable archive. |
|
| Support packages to include. Value can be
|
|
| Flag to display progress information during the build process. |
|
[compiler.excelAddIn.build] Properties
This table shows the TOML properties for the compiler.build.excelAddIn deployment target.
| Property | Description | Default value |
|---|---|---|
| MATLAB function files to include in the build. |
|
| Name of the Excel add-in. The name must begin with a letter and contain only alphabetic characters and underscores. |
|
| Version of the generated add-in. |
|
| Additional files and folders to include. |
|
| Flag to automatically include data files discovered by dependency analysis. |
|
| Name of the class. Class names must meet Excel add-in class name requirements. |
|
| Flag to enable debug symbols. |
|
| Flag to embed the deployable archive. |
|
| Path to the external AES encryption key file. |
|
| Path to the MEX key loader file that retrieves the decryption key at run time. |
|
| Flag to generate a Visual Basic file ( |
|
| Name of the log file for MATLAB Runtime. |
|
| Flag to obfuscate folder structures and file names in the deployable
archive, place user code and data in |
|
| Path to the output folder. |
|
| Path to a JSON manifest file specifying secret keys to embed in the deployable archive. |
|
| Support packages to include. Value can be
|
|
| Flag to display progress information during the build process. |
|
[compiler.dotNETAssembly.build] Properties
This table shows the TOML properties for the compiler.build.dotNETAssembly (MATLAB Compiler SDK) deployment target.
| Property | Description | Default value |
|---|---|---|
| MATLAB function files to include in the build. |
|
| Additional files and folders to include. |
|
| Name of the .NET assembly as a namespace, which is a period-separated
list, for example, |
|
| Assembly version. This property applies only to the MWArray API. |
|
| Flag to automatically include data files discovered by dependency analysis. |
|
| Name of the class. |
|
| Flag to enable debug symbols. |
|
| Flag to embed the deployable archive. |
|
| Flag to enable .NET remoting for the assembly. |
|
| Path to the external AES encryption key file. |
|
| Path to the MEX key loader file that retrieves the decryption key at runtime. |
|
| Target .NET framework version. Specify
|
|
| Data API used for handling data exchange between the application and deployed MATLAB code. |
|
| Flag to obfuscate folder structures and file names in the deployable
archive, place user code and data in |
|
| Path to the output folder. |
|
| MATLAB sample files that generate sample driver files for functions
included in the build. Files must have a |
|
| Path to a JSON manifest file specifying secret keys to embed in the deployable archive. |
|
| Path to the encryption key file that signs the shared assembly. If the value is empty, a private assembly is created. |
|
| Support packages to include. Value can be
|
|
| Flag to display progress information during the build process. |
|
[compiler.cSharedLibrary.build] Properties
This table shows the TOML properties for the compiler.build.cSharedLibrary (MATLAB Compiler SDK) deployment target.
| Property | Description | Default value |
|---|---|---|
| MATLAB function files to include in the build. |
|
| Additional files and folders to include. |
|
| Flag to automatically include data files discovered by dependency analysis. |
|
| Flag to enable debug symbols. |
|
| Flag to embed the deployable archive. |
|
| Path to the external AES encryption key file. |
|
| Path to the MEX key loader file that retrieves the decryption key at runtime. |
|
| Name of the shared library. |
|
| Flag to obfuscate folder structures and file names in the deployable
archive, place user code and data in |
|
| Path to the output folder. |
|
| Path to a JSON manifest file specifying secret keys to embed in the deployable archive. |
|
| Support packages to include. Value can be
|
|
| Flag to display progress information during the build process. |
|
[compiler.cppSharedLibrary.build] Properties
This table shows the TOML properties for the compiler.build.cppSharedLibrary (MATLAB Compiler SDK) deployment target.
| Property | Description | Default value |
|---|---|---|
| MATLAB function files to include in the build. |
|
| Additional files and folders to include. |
|
| Flag to automatically include data files discovered by dependency analysis. |
|
| Flag to enable debug symbols. |
|
| Path to the external AES encryption key file. |
|
| Path to the MEX key loader file that retrieves the decryption key at runtime. |
|
| Data API used for handling data exchange between the application and deployed MATLAB code. |
|
| Name of the shared library. |
|
| Version of the shared library. Uses semantic versioning format. |
|
| Flag to obfuscate folder structures and file names in the deployable
archive, place user code and data in |
|
| Path to the output folder. |
|
| MATLAB sample files that generate sample driver files for functions
included in the build. Files must have a |
|
| Path to a JSON manifest file specifying secret keys to embed in the deployable archive. |
|
| Support packages to include. Value can be
|
|
| Flag to display progress information during the build process. |
|
[compiler.comComponent.build] Properties
This table shows the TOML properties for the compiler.build.comComponent (MATLAB Compiler SDK) deployment target.
| Property | Description | Default value |
|---|---|---|
| MATLAB function files to include in the build. |
|
| Additional files and folders to include. |
|
| Flag to automatically include data files discovered by dependency analysis. |
|
| Name of the class. |
|
| Name of the COM component. The name must begin with a letter and contain only alphabetic characters and periods. |
|
| Component version. |
|
| Flag to enable debug symbols. |
|
| Flag to embed the deployable archive. |
|
| Path to the external AES encryption key file. |
|
| Path to the MEX key loader file that retrieves the decryption key at runtime. |
|
| Flag to obfuscate folder structures and file names in the deployable
archive, place user code and data in |
|
| Path to the output folder. |
|
| Path to a JSON manifest file specifying secret keys to embed in the deployable archive. |
|
| Support packages to include. Value can be
|
|
| Flag to display progress information during the build process. |
|
[compiler.javaPackage.build] Properties
This table shows the TOML properties for the compiler.build.javaPackage (MATLAB Compiler SDK) deployment target.
| Property | Description | Default value |
|---|---|---|
| MATLAB function files to include in the build. |
|
| Additional files and folders to include. |
|
| Flag to automatically include data files discovered by dependency analysis. |
|
| Name of the class. |
|
| Flag to enable debug symbols. |
|
| Path to the external AES encryption key file. |
|
| Path to the MEX key loader file that retrieves the decryption key at runtime. |
|
| Data API used for handling data exchange between the application and deployed MATLAB code. |
|
| Flag to obfuscate folder structures and file names in the deployable
archive, place user code and data in |
|
| Path to the output folder. |
|
| Name of the package as a namespace, which is a period-separated list. The name must begin with a letter and contain only alphabetic characters and periods. |
|
| MATLAB sample files that generate sample driver files for functions
included in the build. Files must have a |
|
| Path to a JSON manifest file specifying secret keys to embed in the deployable archive. |
|
| Support packages to include. Value can be
|
|
| Flag to display progress information during the build process. |
|
[compiler.pythonPackage.build] Properties
This table shows the TOML properties for the compiler.build.pythonPackage (MATLAB Compiler SDK) deployment target.
| Property | Description | Default value |
|---|---|---|
| MATLAB function files to include in the build. |
|
| Additional files and folders to include. |
|
| Flag to automatically include data files discovered by dependency analysis. |
|
| Path to the external AES encryption key file. |
|
| Path to the MEX key loader file that retrieves the decryption key at runtime. |
|
| Name of the package as a namespace, which is a period-separated list. The name must begin with a letter and contain only alphabetic characters and periods. |
|
| MATLAB sample files that generate sample driver files for functions
included in the build. Files must have a |
|
| Path to a JSON manifest file specifying secret keys to embed in the deployable archive. |
|
| Flag to obfuscate folder structures and file names in the deployable
archive, place user code and data in |
|
| Path to the output folder. |
|
| Support packages to include. Value can be
|
|
| Flag to display progress information during the build process. |
|
See Also
Topics
- MATLAB Projects TOML Format (.toml)
- Choose Deployment Option
- Target-Specific Compiler Apps for MATLAB Code Deployment