Additional Exclusions Page (Packed Library Properties Dialog Box)

LabVIEW 2018 Help


Edition Date: March 2018
Part Number: 371361R-01
View Product Info

DOWNLOAD (Windows Only)


LabVIEW 2016 Help
LabVIEW 2017 Help
LabVIEW 2018 Help
LabVIEW 2019 Help
LabVIEW 2020 Help

Requires: Application Builder or Professional System

Use this page of the Packed Library Properties dialog box to configure settings to reduce the size of the packed project library.

Note  The options on this page do not apply to the .lvlib file you select as the Top-level Library on the Source Files page because LabVIEW includes all files of the source .lvlib file in the build.

This page includes the following components:

  • Disconnect type definitions— Specifies whether to omit type definitions from controls during the output of the build process. Selecting this option for an application with a large number of VIs can potentially reduce the memory usage of the built application.
  • Remove unused polymorphic VI instances—Specifies to remove unused polymorphic VI instances during the build process. When you add an instance of a polymorphic VI to the block diagram of a VI you include in the build, LabVIEW adds all other instances of the polymorphic VI to the build. If you place a checkmark in this checkbox, LabVIEW removes any polymorphic VI instances you do not call directly from the block diagram. Disable this option if you dynamically load an instance of a polymorphic VI so LabVIEW does not exclude the polymorphic VI instance you dynamically load from the build. Removing the checkmark from this checkbox might increase the size of the packed library.
  • Remove unused members of project libraries—Specifies to remove unused project library members during the build process. If you place a checkmark in this checkbox, LabVIEW includes only the VIs from the library you call directly from the block diagram. Enabling this option reduces the size of the packed library because LabVIEW does not include the other VIs referenced by the same project library unless the VIs are referenced by other VIs that are part of the build.
    • Modify project library file after removing unused members—If you select to remove unused members of the project library, place a checkmark in this checkbox to direct LabVIEW to modify the library so that the library file does not refer to the removed members. If you do not modify the project library, the packed library might take longer to build.

  • Exclude dependent packed libraries—Specifies to reduce the overall number of files in a build output. When you enable this checkbox, LabVIEW excludes copies of dependent packed project libraries to which you link from other build outputs. To exclude dependent packed project library files, LabVIEW retains the links relative to the original dependent packed project libraries instead of copying those files during the build. For example, if you create one build output and then a subsequent build output, you can relatively link the subsequent build output to a file in the first build output. If you leave this checkbox disabled, LabVIEW copies the dependent packed library file to which you linked instead of retaining the relative link to that file.
  • Exclude dependent shared libraries—Specifies to reduce the overall number of files in a build output. When you enable this checkbox, you limit the number of shared libraries LabVIEW copies. When you create one build output and then link to a file in that build output from another build output, LabVIEW traditionally copies the linked file. To limit the number of copied files, LabVIEW retains the links relative to the original files instead of copying the files during the build.
    Note  If you move the original files to which multiple build outputs are linked, those outputs may not load correctly depending on the location to which you move the original files.



Building and Distributing Applications Home

WAS THIS ARTICLE HELPFUL?

Not Helpful