Hello,
I have a big problem when using my own lvlibp. We have an lvlib for a "home-made" tool that we (re-)use in many developments. Our intention is to integrate it in our development projects as an LVLIBP, with various advantages (compact code, protected source, clear "build" versioning for the whole library, and so on). Building the lvlibp from the lvlib works fine. However, we see that LabVIEW automatically includes all dependencies in the resource folder, like lvanlys.dll that is used in our source VIs.
Then when we want to use that lvlibp in a project, we of course get conflicting dll paths, as we obviously have other parts of the project code that also refer to lvanlys.dll (the one in Program Files/LabVIEW/resources). Then when opening the top VI, the dll from the lvlibp resources folder is always preferred to the "original" one, so that we are always asked to save VIs from .vilib to refer to this "new" path of the dll... It is impossible to work like this...
How can you actually use lvlibp's that refer to common LabVIEW dlls without having these conflicts when integrating the resulting lvlibp into a new LabVIEW project ??? Did I miss something or are these LVLIBP just unusable in this (very general and common) case ?
Thanks,
Vincent