VI Package Manager (VIPM) > Using VI Package Builder

Package Dependencies

The Dependencies properties page of the VI Package Builder window allows you to manage the dependencies of your VI Package build.

Figure 57 – Package Dependencies Property page

A Package Dependency is something your package needs.  For example: When your package ("Package A") uses subVIs that are part of another package ("Package B"), we say that Package B is a dependency of Package A.

In order for your source to have dependencies on a package (“Package B”), it is assumed that some of your source code is calling VIs installed in LabVIEW that got there by installing (“Package B”).

Before you can build your package, please make sure that the package your source depends on is already installed in LabVIEW using VIPM and make sure you have declared this dependency in the Dependencies list.

You can add or remove a dependency to the dependency list by clicking the  buttons. This will open the Add\Edit Package Dependency Dialog. You can also populate the dependencies list automatically by clicking the button. If you have more advanced dependency requirements, you can edit the VI Package Configuration of your VI Package by pressing the  button.

In order to edit an existing dependency entry, click on the  button. You can also double-click on a package name in the list. This will open the Add\Edit Package Dependency Dialog.

What happens to the external dependencies when my package is installed?

When VIPM opens your package, it detects that there are declared dependencies and will automatically suggest to the end user that they be installed at the same time as your package. To find the dependencies, VIPM scans all known VI Package repositories and the local library.

In order to provide a smooth install experience for the end user. Make sure that your dependencies are available in the VI Package Repository or the LabVIEW Tools Network. Alternately, you can distribute your package inside a VIPC file which can contain your package and all dependencies.

Internal Dependencies

If you don’t want to depend on external packages, then you can instruct VIPM to take the VIs your package depends on, and make them internal. VIPM will then take all the VIs called in external packages, rename them and pull them into the package during the build process.

In order to do this, you must do the following:

      Perform a scan of your project by clicking on the ‘scan for dependency’ button.

      Wait for the Scanning process to complete.

      Close the VI Package Configuration Window if it’s not already closed.

      You will see the external dependencies in the dependencies list

      Remove all the packages from the Dependencies list in which you want VIPM to make internal. If they are not in the list then VIPM will make them internal.


Add or Edit Package Dependency Dialog

If you have any feedback or questions (including ideas for other topics you'd like to learn more about), please contact us using our
support page.  We're looking forward to your feedback.

All Contents, Copyright © 2006-2014, JKI. All Rights Reserved.