Question about project dependencies

[MaSta]

Hello and good morning!

I have a project with some libs listed under "Dependencies". They're used in sub VIs which are part of a purchased, third party software package, so they are "as is".

Until now I have never really checked the project for "List objects without caller", because it's not finished yet. Now that I did, it would list me tons of stuff not used in the project,

but being part of libs.

Means, it seems LV would always list the entire lib with its tree and not just those elements it really uses in the subs. Is this normal? I found no way to simply start an action like "Remove all uncalled and unused stuff".

Because I cannot remove anything from a protected lib in the tree view and thus cannot get a clean project. Sure, as long as the codes runs and all needed subs are there this is overhead.

But the overhead is kinda big. Too big. The main problem is that those unused dependencies itself have missing dependencies which LV wants to use if you want to deploy the project to another folder with the "include all dependencies" option. 

[wiebe@CARYA · Accepted solution]

It is normal, or rather, how you describe it is how it is.

I guess LabVIEW's philosophy has always been to automatically include libs for a care free experience, unlike e.g. C\C++ where one has to include libs and then link them as well.

I haven't been in your situation often, where libs add so much it becomes a problem.

I guess if it really bothers you, you'd have to make a ppl wrapper with functions you want. Unused code in dependency libraries will probably still be included in the ppl (the ppl will be larger than needed), but you won't see those items in your project.

[MaSta]

Right, it was just a pita when I wanted to have a cleaned, working copy that I could send someone. So far, I see those unused dependencies only when actively running that action. OK,  question answered.