Jump to content
LabVIEWWI

VIPm Is copying vis from dependency vi into new directory

Recommended Posts

I am creating some packages for our internal reuse code.

I create Package "Config Files".   This package does not have any other package dependencies, and installs as expected (using custom directory, not under LabVIEW).

I create a second package, "File Paths", which calls a vi in the Config Files package.  Since the Config Files package is installed, VIPM correctly says that the Config Files is a dependency.

When I go to build and install (using custom directory, not under LabVIEW) the File Path package, I see a copy of the vi from Config Files under the directory of File path, instead of the file that should have been used under the Config File path.

What I Expect:

C:\Config Files\test.vi

When Installed:

C:\File Paths\test.vi

 

I saw some older forum posts about Internal and external dependencies, but I do not see that option in LV 2019.   Has this option been removed?

Share this post


Link to post
Share on other sites

Here is what I have done so far to reproduce the issue (I can reproduce on multiple packages, I used a simpler example for the post):

Build my FGV Package.  Shown below is the file locations on disk in the LabVIEW Project.   I then built the package, and installed the package.  After installation, the files are all in the FGV folder, with no extra files.

2026879266_FGVPackageDependencies.PNG.71f2010143b06d15df552393f9b44a54.PNG

226737495_FGVPackage-LabVIEWFileLocation.PNG.30186967335ab45fd1fdaba0f390c872.PNG

 

Now I want to build my File Path package, which depends on the FGV Package I just installed.  NOTE the FGV - Test Mode located in the FGV folder on disk.

1697778222_FilePathPackage-LabVIEwFileLocation.PNG.0dd31437cb8a0691a95c67267df8647c.PNG

VIPM correctly identifies that the BMI FGV package is required.

942262445_FilePathDependencies.PNG.a11f1608c1b7eb18ed2fb16d9d5e294e.PNG

Save the configuration and build the package.

Install the package.

When the package is installed, the file that was in the FGV Package has been added to the directory File Path, instead of using the FGV - Test Mode located in the FGV folder with the FGV Package.

2133704601_BMIFilePathInstall-Bad.PNG.9c5961a45e4acda454e57205ee721c27.PNG

 

Share this post


Link to post
Share on other sites

Hi. I just took a look in the latest version of VIPM and it's having some trouble building your package.

Note: installing and calling VIs installed outside of LabVIEW is somewhat non-standard, so that's probably why it's not working too well.

We'll need to do further debugging.

Share this post


Link to post
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.

Guest
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.

Loading...

×
×
  • Create New...

Important Information

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