Files Generated After Packaging MATLAB Functions

When you create a deployable component using MATLAB^® Compiler™, files that correspond to the build target are generated in the output folder. Depending on which packaging method you use, files may be located in various subfolders in the output folder. For more details on the available packaging methods, see Choose Deployment Option (MATLAB Compiler SDK). For a list of files generated by MATLAB Compiler SDK™, see Files Generated After Packaging MATLAB Functions (MATLAB Compiler SDK).

The compiler.build family of functions place output files in a folder named after the main file and target type. For instance, magicsquareStandaloneApplication.

The Compiler apps generate an output folder and place output files in a subfolder named build. The apps optionally create a package subfolder if you create an installer. The installer installs all of the binary artifacts required for distributing a compiled component and optionally installs MATLAB Runtime. You can also generate an installer using the compiler.package.installer function. Distribute the installer to users who do not have MATLAB installed on their machines. If you do not create an installer, you can manually distribute the set of files required to integrate the component according to the component type.

Since R2025a: For information on files generated using a prior version of the Compiler apps, see Files Generated After Packaging MATLAB Functions (R2024b).

Files Generated by MATLAB Compiler

MATLAB Compiler generates the following files in the build output folder. The intermediate artifacts not listed here are generated as a result of packaging of the MATLAB files. They are not significant to the user.

All Targets

The following files are generated for all deployment targets.

File	Description
`buildresult.json`	JSON file containing information on runtime dependencies included in the package. The information corresponds to the `RuntimeDependencies` property of the `compiler.build.Results` object. (since R2025a)
`GettingStarted.html`	HTML file containing packaging information and next steps.
`includedSupportPackages.txt`	Lists all support files included in the package.
`mccExcludedFiles.log`	Log file that contains a list of any toolbox functions that were not included in the package. For information on excluding data files, see `%#exclude`.
`PackagingLog.html`	HTML file containing information on the `mcc` command used and output from the packaging process.
`readme.txt`	Contains information on deployment prerequisites and the list of files to package for deployment.
`requiredMCRProducts.txt`	Contains product IDs of products required to run the package. For more information on product IDs, see `matlab.codetools.requiredFilesAndProducts`. This file will be removed in a future release.
`unresolvedSymbols.txt`	Lists dependencies not found during packaging. If this file is not empty, you must locate the required dependencies and place them in the search path before recompiling.

Excel Add-in

File	Description
`_install.bat`	The file that registers the generated `dll` file.
`filename.bas`	VBA module file that can be imported into a VBA project.
`filename.xla`	Excel^® add-in that can be added directly to Excel. You do not need both `.bas` file and `.xla` file; one of them is sufficient.
`filename_2_0.dll`	The generated `dll` that needs to be registered using `mwregsvr.exe` or `regsvr32.exe`.

Standalone Application

File	Description
`filename.exe` (Windows^®) or `filename` (Linux^® or Mac)	Standalone executable file that contains your application.
`run_filename.sh` (Linux and Mac only)	Shell script file that sets the library path and executes the application. This file is only generated on Linux and Mac systems.
`splash.png`	File that is used as the splash screen image. When the executable starts, the file is read from the same folder where the executable is located, and the splash screen is displayed.

Web App

File	Description
`filename.ctf`	Deployable archive file that contains your web app.