Prev: Producing Standalone Applications

Input Files

The input to the conversion consists of several files:

• One .mex File of the complete m code of your application (.mex files are created from within the m application). This is the only mandatory file.

  If your application requires other .mex files which will be spawned as subprocesses from the main application, they must go into a "Document Directory Zip File".

• An optional Icon File for the icon of your application. This should be a .svg (Scalable Vector Graphics) file, stored using the Tiny SVG profile[6]. Bitmap icons (PNG, GIF, JPEG) can also be submitted, and the web application will attempt to vectorize them, but do not expect brillant results in this case.

  If no icon file is supplied, a default icon will be used.

• Optional NMI DLL Files. These are .dll files (dynamic link libraries) of your own native modules. The file will only be installed if it is not already present on the device, so multiple applications using and providing the same DLL can coexist.

• Optional Embedded SIS Files. These are .sis files containing components your application depends on and which may or may not be already installed. This is another way to install your own native modules[7].

• Optional Document Directory Zip Files. These are .zip files whose contents will be extracted into the document directory during installation. The system.docdir constant contains the path to this directory, and it is also the current directory when the application starts.

• Optional Absolute Path Zip Files. These are .zip files whose contents will be extracted into the root of the installation drive, allowing to put files into arbitrary locations not related to the application directory.

All files you submit will be combined into a single .sis file.

---

Next: Settings

Navigation