The main file of the application. This file reads and executes the content stored in the embedded CTF archive. On Windows, this file is foo.exe.

mcc generates run_<component>.sh file on UNIX (including Mac) systems for standalone applications. It temporarily sets up the environment variables needed at runtime and executes the application. On Windows, mcc doesn't generate this run script file, because the environment variables have already been set up by the installer. In this case, you just run your standalone .exe file.

The library wrapper C source file containing the exported functions of the library representing the C interface to the two MATLAB functions (foo.m and bar.m) as well as library initialization code.

The library wrapper header file. This file is included by applications that call the exported functions of libfoo.

C source file containing data needed by the MCR to initialize and use the library. This data includes path information, encryption keys, and other initialization for the MCR.

The exports file used by mbuild to link the library.

Note   UNIX extensions vary depending on the platform. See the External Interfaces documentation for additional information.

Exports file used by the linker. The linker uses the export file to build a program that contains exports, usually a dynamic-link library (.dll). The import library is used to resolve references to those exports in other programs.

Import library. An import library is used to validate that a certain identifier is legal, and will be present in the program when the .dll is loaded. The linker uses the information from the import library to build the lookup table for using identifiers that are not included in the .dll. When an application or .dll is linked, an import library may be generated, which will be used for all future .dlls that depend on the symbols in the application or .dll.

The library wrapper C++ source file containing the exported functions of the library representing the C++ interface to the two MATLAB functions (foo.m and bar.m) as well as library initialization code.

The library wrapper header file. This file is included by applications that call the exported functions of libfoo.

C++ source file containing data needed by the MCR to initialize and use the library. This data includes path information, encryption keys, and other initialization for the MCR.

The exports file used by mbuild to link the library.

The shared library binary file. On Windows, this file is libfoo.dll.

Note   UNIX extensions vary depending on the platform. See the External Interfaces documentation for additional information.

Exports file used by the linker. The linker uses the export file to build a program that contains exports (usually a dynamic-link library (.dll). The import library is used to resolve references to those exports in other programs.

Import library. An import library is used to validate that a certain identifier is legal, and will be present in the program when the .dll is loaded. The linker uses the information from the import library to build the lookup table for using identifiers that are not included in the .dll. When an application or .dll is linked, an import library may be generated, which will need to be used for all future .dlls that depend on the symbols in the application or .dll.

The bundle created for executable foo. Execution of the bundle occurs through foo.app/Contents/MacOS/foo.

Application

The generated shell script which executes the application through the bundle.