LabVIEW
Help with project cleanup
You can remove all VIs from the project except the toplevel, then see which ones show up in dependencies. Move these back to the project structure where you had them before.
Everything you no longer need, won't be in dependencies.
(assuming you don't have stuff such as auto-populating folders, etc. Also of you call Vis via references obtained from filenames, you need to manually add those back.)
Of course your OS folders will still be full of stuff and you want to clean these up too.
There's probably a more automated way to do this, but assuming you can define "VI's that are still used in the project" as "the tree of dependencies from Main.vi", you can use Get VI Dependencies (Names and Paths). Set "Whole Hierarchy?" to True, and it'll list everything you need to keep.
To make a list of what to get rid of, I'd suggest iterating over all items in the project using VI scripting and making a Set of all of the full path names for everything it finds. Then run Get VI Dependencies, and remove all of the items it returns from the first Set. Then you should have a list of everything that's not called either directly or indirectly from the main VI.
(Make sure you do some filtering, as you'll probably have plenty of false positives- stuff in vi.lib, other libraries, etc.)
I make a Source Distribution build with only the top-level VI. Building it will collect all of the VIs called by that and put them neatly in another folder. You'll just have to find any VIs that are called dynamically.
@cordm wrote:
In the Project Explorer, you can right-click on the project and select Find Items with No Callers. Sort by path and ignore things in vi.lib.
Just remember to do it multiple times- you may have a chain of VI's where C is called by B which is called by A, but A is never called. The first time through, you'll only find A. If you remove it, the next time through you'll only find B, etc.
@jcarmody wrote:
I make a Source Distribution build with only the top-level VI. Building it will collect all of the VIs called by that and put them neatly in another folder. You'll just have to find any VIs that are called dynamically.
One problem with a source distribution is that vital parts of the project won't make it, but it is typically sufficient to copy some files, such as the lvproj itself to the new location. Vital things that will be missing from a source distribution when forgetting the lvproj file is the project layout, the built specifications, as well as e.g. the installer upgrade codes.
(I have a pretty fancy "built all" VI (and entry in the tools menu!) that builds all existing built specifications of a project and adds suitable pre and post processing steps, including copying the lvproj file, bult everything into a special output location hierarchy that is not monitored by google drive (for good reason!), documents all steps as it goes, and even opens the toplevel destination folder when done.)
