Showing results for 
Search instead for 
Did you mean: 

Load lvlbp from different locations on disk

I have project file that includes lvlibp library, functions from inside are called from many places inside application.

Now this library resides in directory A, I want to disk cleaning and load the same PPL but from another place on disk. 

I have played with it and I can not do this... When I remove currently used ppl it goes to dependencies. When I add to project library from new path there is hundreds of confilcts that can not be resolved. 


Is there a simple catch that I am missing? 




I have attached simple example.

0 Kudos
Message 1 of 2

Dear Paweł,


  • it is newer vise, to move a library, or any components of a project just so – from explorer or other external application, it applies especially for VIs in a library and the library itself – the library knows about all of the VIs inside of her, and vice versa
  • every library should have a separate folder in the project structure, that will only contain the library and all of the VIs inside that belong to her
  • the library should be a part of the project structure, de facto all of the components of the project should be a part of the folder structure and should be moved together – it is newer good to have items of one project distributed to many locations outside of the folder structure


e.g. a good folder structure of such an example should look like this:


  • project.lvproj
  • project.lvlps
  • project.aliases
  • subVI (folder)
  • lib (folder)
    • library A (folder)
      • libraryA.lvlib
    • library B (folder)
  • xyz (folder)


… and you should still move the whole “PROJECT FOLDER”


If you need to move a library, or any part of the project to a different location in your HDD (e.g. to make the project nice according to the above) you should do it from the Files view in project explorer. Select the item you want to move (library), Ctrl+E will switch to the Files view, and then right click on the item and select “Move on disk…” then select the desired location. This will keep the dependencies, move the library physically on the HDD, and will not introduce hard to resolve conflicts to your project.

Jozef Lipták
0 Kudos
Message 2 of 2