Caveats and Recommendations for Packed Project Libraries

FlexRIO Help

Edition Date: November 2015

Part Number: 372614J-01

»View Product Info

»Download the Help in ZIP Format

The following list describes some of the caveats and recommendations to consider when you build a packed project library:

  • If a VI calls a packed library on one target and you open the VI on another target, when the VI calls the packed library, the library tries to open on the original target. If the new target has another operating system or a different version of LabVIEW, the packed library cannot open on the new target, and the caller VI breaks. If you want the VI to call the packed library on the new target, rebuild the library for the new target.
  • When you create a debug build for a packed library, you can view the block diagram of each VI. Even though you can use the block diagrams to debug issues, you cannot edit the VI or save changes to the packed library. Save changes to a VI from the LabVIEW project with the project library. If you want to update the packed library, you must rebuild the library.
  • Include only related VIs in a packed library. When you open a VI in a packed library, all VIs in the packed library load. If you include non-related VIs, load time increases because more VIs need more time to load.
  • To link to a palette when you build a packed library, save the palette in the same version, target, and operating system as the packed library.
  • LabVIEW includes dependencies of the top-level library in the packed library, but they do not export with the build and are not visible in the packed library. To export the dependencies of a packed library, place the dependencies in the top-level project library before building the packed library.
  • If an exported VI has a connector pane with inputs or outputs of type definitions or classes, include the type definitions or classes in the top-level project library. When you right-click a project library and select Replace with a packed library from the shortcut menu, LabVIEW does not replace type definitions and classes, only exported items of the packed library. As a result, VIs in the packed library might break when you replace the project library with the packed library.
  • After you create a project library in a LabVIEW project, create a separate LabVIEW project for the project library before you build the packed library. If you build the packed library in the same LabVIEW project where you create the project library and you replace the project library with the packed library, you cannot rebuild the packed library.
  • (MathScript RT Module) Packed libraries do not support MathScript Nodes. LabVIEW returns an error when building a packed library that contains a MathScript Node.


Not Helpful