Using the LabVIEW Runtime when Distributing Build Outputs

You must install the LabVIEW Runtime on any computer on which you want to run any type of LabVIEW build output. Design VIs for build outputs with behaviors of the LabVIEW Runtime in mind, and understand how to deploy the LabVIEW Runtime to support your build outputs on end user systems.

The LabVIEW Runtime includes the libraries and other files necessary to run basic application types built in LabVIEW.

Note The LabVIEW Runtime is multilingual.

Designing Programs for the LabVIEW Runtime

  • Some VI Server properties and methods are not supported in the LabVIEW Runtime. Avoid using these properties and methods in the VIs you include in an application or shared library.
  • Incorporate error handling into the VIs of the application. LabVIEW does not display automatic error handling dialog boxes in the LabVIEW Runtime.
  • If the VI uses custom run-time menus, make sure the application menu items that the VI uses are available in the LabVIEW Runtime.
  • Avoid writing block diagram code that executes after the last front panel window closes.

    When you close all front panel windows in a LabVIEW-built application, the application stops. If the VI you build into the application contains code that executes after the last front panel window closes, this code does not execute in the application.

Deploying LabVIEW Runtime to Users

  • When you create a build specification for an installer, LabVIEW includes the LabVIEW Runtime by default.
  • Compatibility of the LabVIEW Runtime with build outputs: compatibility considerations depend on the version of LabVIEW that created the application and on the configuration options for the application.
    Table 44. Compatibility Between LabVIEW Build Outputs and the LabVIEW Runtime by LabVIEW Version
    LabVIEW Version LabVIEW Runtime Compatibility
    LabVIEW 2017 and later
    • Option that begins with "Allow future versions" checked: Any version of LabVIEW Runtime including or newer than the version of LabVIEW that created the application can run the built application.
    • Option that begins with "Allow future versions" unchecked: You must install each version of LabVIEW Runtime that corresponds with each version of LabVIEW used to create the application types.

    Leave this option checked to prioritize forward compatibility.

    Uncheck this option to accomplish the following:

    • Prevent changes to the performance profile with software updates
    • Avoid unexpected problems that might result from compiler upgrades

    This option is available on the Advanced page of the dialog box for relevant types of LabVIEW build outputs.
    LabVIEW 2016 and earlier

    You must install each version of the LabVIEW Runtime that corresponds with each version of LabVIEW used to create the application.

    For example, if you want to run an application created in LabVIEW 7.0 and an application created in LabVIEW 8.0 on the same computer, the computer must have versions 7.0 and 8.0 of the LabVIEW Runtime. The LabVIEW Runtime 7.0 supports only the LabVIEW 7.0 application; the LabVIEW Runtime 8.0 supports only the LabVIEW 8.0 application.
  • All types of applications built with one particular version of LabVIEW can share the same instance of the LabVIEW Runtime. To support any number of compatible built applications, you need to install the LabVIEW Runtime only once.
  • Operating system–specific considerations for the LabVIEW Runtime:
    • Windows: If you want to include the LabVIEW Runtime in an installer built with the Application Builder, you must log on as an Administrator or a user with administrator privileges to run that installer.
    • Linux: When you install the LabVIEW Runtime on a target computer where you want to run an application that uses the Mathematics or Signal Processing VIs, enter yes when prompted to install the LabVIEW Runtime Advanced Analysis Support package (labview-rte-aal-1.1-1.i386.rpm).