When I build a packed library, the build process keeps looking for the same VIs over and over again

[clendon.gibson@canrig.com]

Hello everyone,

I searched for an answer to my problem and was unable to find one. If there is a thread on this already please point me there and accept my apologies for the duplicate post.

I am having trouble making a packed library for a project I am migrating from LV 8.5 to LV 2010.

When I try to build the library, it keeps asking me where certain VIs are. The VIs are in the project already. What is even more confusing is that the box that displays the attempt to find the VI (it lists what paths it is trying) has the correct path to the VI.

When I navigate to the correct VI the build continues, although sometiems I am required to navigate to all the VIs in a directory.

What is also confusing is the need to navigate to the same VI more then once during the build.

The project is made up of several lvlibs. Inside one of the lvlibs are the two main VIs. These VIs are called via VI server. This project is a VI server based plugin for our main application. The target I am working with is cRIO RT, but we will also need to make Windows and Linux builds.

[PJS]

I experienced a similar issue.  What I ended up doing was deleting the VIs from the vilib and then adding them back.  This fixed the problem for me.

[clendon.gibson@canrig.com]

I tried this and it did not seem to work.

So what I did was first remove and the add back the lvlib to the project I am trying to build as a packed library. Then I reread the instructions.

I then took one of the lvlibs which has VIs that the build process can not find without help and removed all the VIs and then added them back in.

I then tried another compile. The build process still can't find the files unaided. (Very specifically it can't find files in the lvlib I changed.) Just to try, I exited LabVIEW and then started it again. I tried another build with the same results.

As a note, this only happens with Packed Library builds. I can make a Source Distribution just fine.

[BTreece]

I would make sure that all of your VIs are properly linked to the library.  You can also refer to the LabVIEW Help to make sure that you are properly calling all of the VIs when you are creating the build specification.

Brandon Treece

Applications Engineer

National Instruments

[clendon.gibson@canrig.com]

How would I tell if a VI is properly linked to a library?

Wouldn't removing all the VIs from a library and then adding them back ensure that they were properly linked?

I did this by using the add folder (snapshot) option in the project.

I will look at the Help page and try the project again.

[BTreece]

Yes, if you removed the files from the library and added them again, they should be linked properly.  I would walk through the help document that I linked in my last post.  Go through the Application Builder checklist and make sure that you are not missing anything.  Let us know if you are having any further issues.

Brandon Treece

Applications Engineer

National Instruments