You can create packages and deploy them to clients through NI Package Manager or SystemLink.
Before creating packages, create a source distribution, packed project library, shared library, .NET assembly, or executable to include in your packages.
Note You cannot distribute stand-alone VIs.
In the�Project Explorer window, right-click�Build Specifications�and select�New»Package.
In the Package Properties dialog box, under�Information, enter the name you want to use for your package in�Package name.�The package name must be all lowercase and contain no spaces. NI Package Manager and other packages use this name to reference the package you create.
Under�Destinations, set up any destination folders where you plan to install the package in the client.
Under�Source Files, specify which files or build specification outputs you want to install.
(Windows) Under�Shortcuts, you can add a shortcut to the Startup menu if you want your application to run as soon as the system starts up. You can also add a shortcut to the Desktop or Program Menu on Windows.�By default, LabVIEW adds a shortcut in the Windows Program menu for each application included in the package.
Under�Package, specify the display name and synopsis for your package.�The display name is what users will see in the Package Manager or NI SystemLink when they install your package. The synopsis is the first line of the description that users see before they click on a package to see its full description.
Under�Dependencies, specify dependencies on any currently installed packages.
Configure the relationship of the dependency. You can define a dependency as�required,�recommended, or�suggested�and specify version ranges.
To prompt the user to install your package when they install a related package, place a checkmark in the�Include enhanced relationship checkbox.
Under�Version Information, specify the version of your package and what version you want to display to the user.�If you remove the display version, the user sees the full version in the Package Manager.
Under�Advanced, set your package to run executables or scripts while it installs or uninstalls.�For example, you can specify whether the process for installing or uninstalling the package waits for a certain action to complete.
(Optional) Under Package Installer, place a checkmark in the Create a Package Installer checkbox to build your distribution into a package installer file (.exe).
(Optional) Under Feed, choose whether to add your package to a local feed or publish the package to a feed on the SystemLink server.
Click�Build.�A�(Windows).nipkg�file or (NI Linux Real-Time).ipk file appears in the destination you specified.
You can distribute the package to clients through Package Manager or SystemLink. (Windows) Your clients can use Package Manager or SystemLink to subscribe to a feed to find and install your packages. (NI Linux Real-Time) Your clients can install packages through SystemLink or from the command line on the NI Linux Real-Time target. Package Manager does not support .ipk files.
