Jump to content
Sign in to follow this  
Porter

Annoying PPL behavior

Recommended Posts

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.

Capture.PNG.2dc503d3e500f4882737bd19dd4929e2.PNG

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?

 

Share this post


Link to post
Share on other sites

It is solved now. I unchecked the exclude PPLs and DLLs in the build spec of LF.lvlibp

277933416_Annotation2019-09-13141306.png.354dda46409591731d06bdca3b790850.png

And moved the resulting LF.lvlibp to the same directory as the other PPLs.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.