Files Generated After Packaging MATLAB Functions

When the packaging process is complete, three folders are generated in the target folder location: for_redistribution, for_redistribution_files_only, and for_testing.

The file PackagingLog.html generated in the target folder location contains information on the mcc command used and output from the packaging process.

`for_redistribution` Folder

Distribute the for_redistribution folder to users who do not have MATLAB^® installed on their machines.

The folder contains the file MyAppInstaller_web.exe that installs the packaged application, MATLAB Runtime, and all the files that enable use of the application on the target platform with the target language in the target folder. It downloads MATLAB Runtime from the Internet if it is not included in the installer at the time of packaging.

`for_redistribution_files_only` Folder

Distribute the for_redistribution_files_only folder to users who do not have MATLAB installed on their machines. This folder contains specific files that enable use of the packaged application on the target platform with the target language.

Standalone Applications

File	Description
`filename.exe` (Windows^®) or `filename` (Linux^® or Mac)	Standalone executable file.
`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.
`GettingStarted.html`	HTML file containing packaging information.
`splash.png`	When the executable starts, the file is read from the same folder where the executable is located, and the splash screen is displayed.

Excel Add-Ins

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`.
`GettingStarted.html`	HTML file with packaging and installation details.

`for_testing` Folder

Use the files in this folder to test your application. The folder contains all the intermediate and final artifacts such as binaries, JAR files, header files, and source files for a specific target. The final artifacts created during the packaging process are the same files as described in for_redistribution_files_only Folder. For further information on how to test your packaged applications, see the following topics:

Target	Link
Standalone Application	Install Deployed Application
Excel Add-In	Install and Use Function Wizard

This folder also contains five text files.

File	Description
`includedSupportPackages.txt`	Lists all support files included in the application.
`mccExcludedFiles.log`	Log file that contains a list of any toolbox functions that were not included in the application. For information on excluding data files, see `%#exclude`.
`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 application. For more information on product IDs, see `matlab.codetools.requiredFilesAndProducts`.
`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.

The intermediate artifacts generated are a result of packaging of the MATLAB files. They are not significant to the user.