Search the Community
Showing results for tags 'package builder'.
Found 2 results
Cross posted on LavaG, but was not getting any replies. So lets try here. I am using the newest version (2020.1) of VIPM, but I had this same issue with the release of 2020. For two of the packages that I have created for internal repos, VIPM has decided that I need a System Package. The posts I have seem from JKI indicate that this is a sub-package that is used internally to the main package, and should be automatically included. However, after I am seeing issues on any PC other than the PC where the package was built. Is there a setting I am missing? Showing the (System) package as a dependency: Package Configuration in the VI Package Configuration Editor Package installed, on the PC where the package was initially created (no issues, no exclamation mark) Package when installed on another PC (NOTICE: the System Package name has changed and there is a red exclamation mark, but there are no errors shown on install of the package).
Hello, I'm trying to update a package that was previously building just fine. I've made what I thought were inconsequential changes to the contents of the package (updated a few VIs... no new dependencies) and the package no longer builds. VIPM seems to hang at "Testing for empty source." What does this mean? How can I figure out what's causing the hang and move forward? Thanks, Jason