Is there an easy way to know if a vi within a LLB not being use by a Labview Application

[Dao]

To All,

I have developed a Labview application over a year that contains a number of LLBs.  There are significant number of VIs within those LLB files that were written but have not been called  by the application.  I am trying to optimize all LLB files to exclude those unused VIs.  Because there are many of them, the task to find out which Vi is being used and which one is not become very tedious.  First question: Is there a way to automate the process?  Second question: Does a compiled Labview application include all used and unused Vis from the LLBs in the .exe file?  I am very appreciate any inputs from this community.

A Labview User  

[Dennis_Knutson]

Imho, what you should do is stop using an llb for development. An llb is old technology and the only purpose these days is to distribute code. They are somewhat fragil in that a single broken VI in one will make the whole llb unuseable and they do not work at all with source code control. I would suggest you convert them to folders and update your project or make a lvlib from the ones you use and add those to the project.

When you do a build, the build will only include the VIs that are used.

[Ben]

In pre-LV 8 you could do a "Save with options..." and choose development distribution, single prompt preserve hiarchy and LV will pick-up all of the used VI's and plomp them down in a new location leaving all of the used behind as well as fixing up a of the linkages to point at the new location.

In LV 8 and beyond you can create a Source Distribution in the project and acoomplish the same thing.

Please note:

If you are using dynamic VI's you will have to include them in a Tree.vi (for LV prior to 😎 or make sure you included them when you create your source distribution.

Just trying to help,

Ben

[altenbach]

---

Ben wrote:

In pre-LV 8 you could do a "Save with options..." and choose development distribution, single prompt preserve hiarchy and LV will pick-up all of the used VI's and plomp them down in a new location leaving all of the used behind as well as fixing up a of the linkages to point at the new location.

In LV 8 and beyond you can create a Source Distribution in the project and acoomplish the same thing.

---

In LabVIEW 8+, you can get something similar to the first option by selecting "save for previous" and then pick the existing version (yes, it's there!).