Documentation

export

Export Simulink Project to zip

Syntax

  • export(proj,zipFileName)
    example
  • export(proj,zipFileName,definitionType)

Description

example

export(proj,zipFileName) exports the project proj to a zip file specified by zipFileName. The zip archive preserves the project files, structure, labels, and shortcuts, and does not include any source control information. You can use the zip archive to send the project to customers, suppliers, or colleagues who do not have access to your source control repository. Recipients can create a new project from the zip archive by clicking New in the Simulink® Project Tool, and then in the start page, clicking Archive.

export(proj,zipFileName,definitionType) exports the project using the specified definitionType for the project definition files, single or multiple. If you do not specify definitionType, the project's current setting is used. Use the definitionType export option if you want to change project definition file management from the type selected when the project was created. You can control project definition file management in the preferences.

Examples

collapse all

Open the airframe project and create a project object.

sldemo_slproject_airframe;
proj = simulinkproject;

Export the project to a zip file.

export(proj,'airframeproj.zip')

Related Examples

Input Arguments

collapse all

Project, specified as a project object. Use simulinkproject to create a project object to manipulate a Simulink Project at the command line.

Zip file name or path, specified as a character vector ending in the file extension .zip. If zipFileName is a filename, Simulink exports the file to the current folder. You can also specify a fully qualified path name.

Example: 'project.zip'

Data Types: char

Definition file type, specified as slproject.DefinitionFiles.SingleFile or slproject.DefinitionFiles.MultiFile. Use the definitionType export option if you want to change project definition file management from the type selected when the project was created. MultiFile is better for avoiding merging issues on shared projects. SingleFile is faster but is likely to cause merge issues when two users submit changes in the same project to a source control tool.

Example: export(proj,'proj.zip',slproject.DefinitionFiles.SingleFile)

Introduced in R2013a

Was this topic helpful?