Now that you've finished learning about Managing Package Dependencies you'll want to know about Package Configuration Management. But, what does "configuration management" mean, exactly?
Simply put: If the package you are building uses subVIs from other packages, you need to make sure that you have those other packages installed when you build your package (and when your working on your package).
In our last exercise, Managing Package Dependencies, we did a Scan for Package Dependencies from the Dependencies page of theAdvanced Build Parameters. In doing so, we actually created a VI Package Configuration that is associated with our package. Now, let's take a look at it.
1) Open the Package Builder window and select the “Test Package Source” folder as your VI Package Source Folder. (Note that you obtained Test Package Source.zip in the Building your First Package exercise)
2) Click on the Package Dependencies under Advanced section of the Package Dependencies window.
3) To view the VI Package Configuration for your package, press the Open VI Package Configuration button, as shown below:
4) This will open the Package Configuration Editor window, shown below.
From this window you can manage the details of which packages your package depends upon. You can do the following:
Apply your VI Package Configuration
When you apply your VI Package Configuration, VIPM will ensure that all the packages are installed in LabVIEW.
Add and Remove Packages
You can add and remove packages from your VI Package Configuration.
Add packages by dragging and dropping them from the VIPM Main window's package list (as shown below).
Remove packages by right-clicking on them in the Package Configuration Editor window and selecting Remove from the context menu.
Change to Package Versions
You can right-click on packages in the Package Configuration Editor window and choose a different package version by selecting a different package version under the Change to Version>> context menu.
Scan for Dependencies
Scan for your VI Package Source Folder to discover the dependencies
And much more...
Now, that we're doing configuration management, let's look at how to take it to the ultimate level: Using VI Package Builder with Source Code Control.
Up: VI Package Guide
If you have any feedback or questions (including ideas for other topics you'd like to learn more about), please consider posting them to the VIPM Discussion Forums. We're looking forward to your feedback.