Jump to content
hooovahh

VI Calling VIM Fails to Build [fixed in VIPM 2017f1]

Recommended Posts

Update: this issue has been fixed in VIPM 2017f1
 
I've been using the new VIMs feature of VIPM 2017 and am having some issues getting it to build successfully. If I have a VIM on the palette it builds just fine, but if I add a VI that calls that VIM the build fails, even if that VI isn't on the palette.

 

 

 

 

Attached is a zip with my source. It fails to build because the normal VI "Is Variant Repository.vi" calls a VIM that is in that package. If I delete that VI the build works fine. Is this a known limitation that a package can't be built, if a VI calls a VIM? Here are the errors seen when the build fails. Thanks.

 

 

 

 

 

VIPM 1.png

 

 

VIPM 2.png

 

 

Variant Repository Source 2017.zip

 

Share this post


Link to post
Share on other sites

So...is anyone from JKI monitoring these forums? I have a show stopping bug that I posted two weeks ago, in the latest version of VIPM, can anyone give any advice? Thanks.

Share this post


Link to post
Share on other sites

I have the exact same issue:

 

post-7853-0-18353300-1500037164_thumb.png

 

At the moment, I'm only calling VIMs inside my Examples, and so I'm excluding Examples from the package temporarily.

Edited by drjdpowell

Share this post


Link to post
Share on other sites

Hi !!

 

Apologies for missing out on these. We were able to reproduce the behaviour and have recorded as Case 17570 for VIPM team to take a look at.

 

I will get back to you when there are more updates on this.

Share this post


Link to post
Share on other sites

The recently posted update VIPM 2017 F1 fixes this issue for me. Finally I can build all the VIM packages I've been wanting to.

Edited by hooovahh

Share this post


Link to post
Share on other sites

Great! It was indeed one of the fixes implemented in VIPM 2017 SP1.

Thanks for confirmation and glad to know that you were able to build the package successfully.

Share this post


Link to post
Share on other sites

Sorry to open this thread again. However, I have VIPM 2018.0.0f1 and I am trying to build a package with VIMs in and I am getting exactly the same issue that James Powell posted earlier in this thread. Please can you tell me what the workaround was? As simply upgrading VIPM didn't work.

image.thumb.png.89d0443aaf354fc86bc84c84a2ad7bd7.png

Share this post


Link to post
Share on other sites

Same issue still in 2018 f2. 

Appears to be related to a vim in a class. Removing the vim from the class solves the problem. I got that work around from Tom and another at https://forums.ni.com/t5/LabVIEW/VI-Package-Manager-Fails-to-Build-with-Malleable-VIs-VIMs/td-p/3871468

Share this post


Link to post
Share on other sites
45 minutes ago, jamesmc86 said:

Same issue still in 2018 f2. 

Appears to be related to a vim in a class. Removing the vim from the class solves the problem. I got that work around from Tom and another at https://forums.ni.com/t5/LabVIEW/VI-Package-Manager-Fails-to-Build-with-Malleable-VIs-VIMs/td-p/3871468

Hi @jamesmc86. Thanks for letting us know. I'd like to get this fixed, if possible. Would you be willing to put a very small/simple example .vipb project together and share it, so that we can easily reproduce and investigate? Thanks.

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.