Jump to content
Captain Kirby

VIPM Build Ignoring Shared Variable Libraries

Recommended Posts

I'm trying to create a package from a LabVIEW project that includes a shared variable library (among other things such as documentation, subVIs, etc.) The package should be installed into the Project Templates destination. Other projects installed to this location without shared variables have been successful.

 

When I build the package including the project with a shared variable library, I recieve no errors and the build is successful. It also installs into the LabVIEW project templates location correctly. I can also select the project successfully through the "create project" dialogue, however, the project is not created and ends with an "Error 1" or "Input Parameter Invalid". Adding the shared variable library to the Project Templates folder location manually removes the LabVIEW error and the project can be created successfully in LabVIEW.

 

I've confirmed that the source file settings for the shared variable library are configured to install the library to the correct location in the LabVIEW Templates folder.

 

This seems very similar to this bug found and solved in the past, but for the Example VI's destination.

 

[bug] LabVIEW Variable Library is ignored when building a package

 

I'm sure I'm doing something silly. A quick search of the forum didn't find anything too similar (though I'm sure I could have missed it.) here is the source code and package specification that is causing the problem.

Edited by Captain Kirby

Share this post


Link to post
Share on other sites

I'm trying to create a package from a LabVIEW project that includes a shared variable library (among other things such as documentation, subVIs, etc.) The package should be installed into the Project Templates destination. Other projects installed to this location without shared variables have been successful.

 

When I build the package including the project with a shared variable library, I recieve no errors and the build is successful. It also installs into the LabVIEW project templates location correctly. I can also select the project successfully through the "create project" dialogue, however, the project is not created and ends with an "Error 1" or "Input Parameter Invalid". Adding the shared variable library to the Project Templates folder location manually removes the LabVIEW error and the project can be created successfully in LabVIEW.

 

I've confirmed that the source file settings for the shared variable library are configured to install the library to the correct location in the LabVIEW Templates folder.

 

This seems very similar to this bug found and solved in the past, but for the Example VI's destination.

 

[bug] LabVIEW Variable Library is ignored when building a package

 

I'm sure I'm doing something silly. A quick search of the forum didn't find anything too similar (though I'm sure I could have missed it.) here is the source code and package specification that is causing the problem.

 

 

Sorry, looks like I forgot the attachment somehow.

Reproduce SV Bug.zip

Share this post


Link to post
Share on other sites

Sorry for the long delay, I had stopped monitoring the thread.

 

But no, that's not what I get. I still have the same issue of the lvlib with shared variables not being installed to the project template folder. Here's a screenshot of the source and destination folders on my machined, and a dummy package similar to yours (I think) that reproduces it on my machine.

 

I tried to recreate the behavior with a dummy package. The package built and install successfully as expected.

http://screencast.com/t/f2iPblbIvw

 

Is that what you get as well?

post-23493-0-25216600-1384837635_thumb.png

Reproduce.zip

national_instruments_lib_tester-1.0.0.1.vip

Share this post


Link to post
Share on other sites

Just to give an update to this. I investigated the issue and the problem is that VIPM doesn't support shared variables properly.

However, I have a workaround.

 

The workaround is to add a placeholder VI inside the LVLIB that contains the shared variables (see image)

This will force VIPM to pull in the LVLIB into the package.

 

Right now. VIPM relies on linker info of the VIs to pull in appropriate LVLIBs to the package. In other words, if VIPM cannot find a reason to have an LVLIB in the package (no VI needs it), then it will not include it in the package. Placing a VI in there, triggers VIPM to keep the LVLIB.

 

I need to do some work on this but in the meantime. The above workaround should help you build the package correctly.

 

 

2014-02-25_1917.png

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.