Jump to content

Issue with Additional System Dependency in VIPM Package Build

Recommended Posts

Hi VIPM Community,

I've encountered an issue with the VIPM package build process where an unexpected system dependency with the same vip file name" is added when installing the package using the .vip file. This "additional system dependency is not specified in the build spec" and confuses during installation irrespective of the VIPM version.

Specifically, when I choose "OS User Documents" as the destination option in the build specification, VIPM includes a dependency on "System," which is unintended.

This unexpected dependency complicates the installation process for end users and may result in compatibility issues with certain LabVIEW environments. Despite reviewing my LabVIEW project and VIPM package configuration, I've been unable to identify the root cause or justification for this issue.

Has anyone else encountered a similar problem with VIPM package builds? I would greatly appreciate any insights or suggestions on resolving this issue.



Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.