Porter Posted September 11, 2019 Report Share Posted September 11, 2019 I have been transitioning my framework's core libraries to packed project libraries. Unfortunately, the higher level PPLs depend on lower level PPLs, but i think that I've managed to sort out all of the broken connections. Now the issue that is bothering me is that whenever I open a project containing a higher level PPL, I get a bunch of "VI cannot be found on disk errors" that refer to VIs within the higher level PPL. My initial thought was that the file paths were too long, but that doesn't seem to be the case. Has anyone else come across this behavior when using PPLs? Quote Link to comment
Porter Posted September 13, 2019 Author Report Share Posted September 13, 2019 It is solved now. I unchecked the exclude PPLs and DLLs in the build spec of LF.lvlibp And moved the resulting LF.lvlibp to the same directory as the other PPLs. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.