Labview packed library internal paths problem

[GarryG]

Hey thanks for posting this.  Verified it works for me.

[fabznx]

Just a quick remark about classes:

If you use Dynamic Dispatch (which is likely to happen when using classes) be aware, that disabling "preserveHierarchy" will create Directories (with distinct names) next to the lvlibp with all VIs that are Dynamic Dispatch and would double inside the lvlibp.

Reason: Since we do not preserve the Hierarchy, Labview will try to place all VIs in a single directory (the PPLs internal).

This will also happen for normal VIs, that are named equally, but stored in different directories on disk.

And this is also true - I think - for building Executables with this preserveHierarchy disabled.

[fabznx]

By the way. 

There is a solution to this.

Either you are the creator of these VIs. Then you could just rename them.

Or you are using Toolkits that have this problem, where you would have to rename the file during build.

One example for me is the jsonText Toolkit, which has a Serializer Class that uses the same exact names for its methods than the Internal ones.

In this scenario I'd use the Source File Settings to Rename this file in the build for the non-class VIs.