Dependency Changed Error With LabVIEW Packed Library

Issue Details

• I have built a LabVIEW Packed Library, but when I open one of the library VIs, the VI is broken with error "This VI uses a dependency that has changed. That change requires this VI to recompile".
• I have successfully built a Packed Library in LabVIEW. Now I've modified the library or moved it on disk and LabVIEW reports the error below. How can I fix this?

Solution

1. In the Packed Library's Build Specifications, enable debugging.
   • Enabling debugging requires more memory and can slow down a VI's execution speed because it retains a VI's Block Diagram. However, this option ensures that LabVIEW recompiles the library VIs. Refer to Optimizing Execution Speed for Built Applications for more information.
   • To enable debugging, follow the steps below:
     1. Right-click on the Build Specifications and select Properties.
     2. Navigate to the Advanced page.
     3. Place a checkmark in the Enable debugging option.
     4. Rebuild the Packed Library.
2. Alternatively, disconnect type definitions and exclude unused library members.
   • Excluding unused library members reduces the size of the library. In doing so, LabVIEW only includes library VIs that are explicitly called on the Block Diagram. This reduces the risk of conflicting dependency locations. Refer to Additional Exclusions Page (Packed Library Properties Dialog Box) for more information.
   • Right-click on the Build Specifications and select Properties.
   • Navigate to the Additional Exclusions page.
   • Place a checkmark in the following options:
     • Disconnect type definitions
     • Remove unused members of project libraries
     • Modify project library file after removing unused members