LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Private inlined VIs and packed project libraries

So, I'm trying to build a packed project library and it has a few *private* VIs that are crying out to be inlined (simple VIs used in a for loop etc). However, this seems to be causing a few issues:

 

1. When I attempt to build the lvlibp I get an error stating "You cannot include inlined VIs inthis build if you remove the block diagram from the VI or if callers adapt to VIs in the packed library.". Whilst this makes sense to me for public packed library VIs, why does this matter for private ones - surely the VI will already get flattend out into the calling VI during the build process?

 

2. If I try and set the Source File Settings for the inline VI to not remove the block diagram (as suggested by the error), the error still does not go away (I would really like to keep the ability for callers to adapt to VIs in the packed library).

 

Here's a stripped out project (with instructions) showing the issue.

 

It seems like a bug to me, but any ideas? 

Thanks,

Shaun

0 Kudos
Message 1 of 4
(2,496 Views)

I was just going through the instructions to reproduce the error. Because the error says "You cannot include inlined VIs in this build if you remove the block diagram from the VI OR if callers adapt to VIs in the packed library," it seems like as long as you maintain your settings for the caller to be able to adapt the VI, then I would expect this error to continue to occur.

0 Kudos
Message 2 of 4
(2,467 Views)

Yeah - looks like I mis read that. Although it still perplexes me why I need to include the block diagrams and turn off caller adapting for private VIs - those are only ever going to be compiled and used within the packed library itself - LabVIEW will surely never need to embed the block diagram of the inlined VI into another VI because it wont be accessible outside the library?

0 Kudos
Message 3 of 4
(2,450 Views)

You can always make a suggestion on the idea exchange -- maybe there's a really good reason by LabVIEW currently won't do what you want it to with the private inlined VIs and maybe there's not, maybe they can change it.

0 Kudos
Message 4 of 4
(2,436 Views)