Hi all,
Some things really sneak up and surprise you from time to time: if you build a Packed Project Library ( lets call it: PPL_A") that has a dependency on another Packed Project Library which resides in vi.lib (lets call that one "PPL_VILIB"), you are not able to open the Packed Project Library ("PPL_A"). You end up with a dialog box simply stating: "Project or Library File cannot be opened" (see pic).
Any other location other than the LabVIEW symbolic paths (<vilib>, <userlib>) works fine.
You can also open "PPL_A" if you have the "PPL_VILIB" loaded into memory beforehand. It looks like the second PPL is failing to load into memory as it cannot resolve the path to one of its dependencies, but the behaviour is different than that of it simply being missing - LabVIEW doesn't even try to search for it. At this point its suspiciously looking like a ppl cannot resolve dependencies from a symbolic path or something.
This behaviour is the true for 2018 and 2019, however it seems to be fine for 2014.
To test, try to build a PPL that references another PPL placed in vi.lib. Attached is an example:
1) Build "lib1.lvlibp
2) place "lib1.lvlibp" in <vi.lib>
3) Build "llib2.lvlibp" (which depends on lib1.lvlibp)
4)Close the project and try to open the built lib2.lvlibp
As always, any thoughts on this greatly appreciated: this is a huge wrench in our plans, as you can imagine.
Thanks in advance,
Cris