LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

What path do I use to load VIs from a packed library

I ported a project from LV8.5 to LV2010. This project represents a plugin for a larger application. It is accessed by VI server methods.

 

When I made a packed library, I could not access the VIs in it. After messing around I found a VI that lists the exported VI paths.

 

Apparently when the packed library was made, it included several levels of the file hierachy. So instead of getting a reference for:

 

MyPackedLibrary.lvlibp/TopLevel.vi

 

I have to do this

 

MyPackedLibrary.lvlibp/DirOne/DirTwo/DirThree/TopLevel.vi

 

I don't know why it did this and can't see anything that makes sense in the build specification.

 

I want to know how to set this path.

 

Thanks!

0 Kudos
Message 1 of 2
(2,368 Views)

Hi Clendon,

 

Looking at the settings for PPL's, it appears they default to "Preserve disk hierarchy" (see Packed Project Library Properties -> Destinations -> Destination Type), with no option to disable that choice.

I'm not sure if the setting will be enabled in future versions of LabVIEW, so your best bet might be to simplify your on disk representation of your library before compiling.

 

Hope this helps,

Fred Visser -- SystemLink R&D -- National Instruments
0 Kudos
Message 2 of 2
(2,343 Views)