How can I replace a packed project library (lvlibp) to a regular project library (lvlib) in a LabView project?

[sziszkont]

I have a lvproj file with many lvlib and some lvlibp files. There is a lvlibp file that is also available in lvlib format. How can I replace it easily? I need all caller VIs of that packed project library (lvlibp) in the LabVIEW project to update with the qualified names of the "regular" library (lvlib).

[crossrulz]

---

@sziszkont wrote:

I have a lvproj file with many lvlib and some lvlibp files. There is a lvlibp file that is also available in lvlib format. How can I replace it easily? I need all caller VIs of that packed project library (lvlibp) in the LabVIEW project to update with the qualified names of the "regular" library (lvlib).

---

Right-click on the PPL in the project and choose "Replace With...".  You can then find the lvlib file.

[JÞB]

---

@sziszkont wrote:

I have a lvproj file with many lvlib and some lvlibp files. There is a lvlibp file that is also available in lvlib format. How can I replace it easily? I need all caller VIs of that packed project library (lvlibp) in the LabVIEW project to update with the qualified names of the "regular" library (lvlib).

---

Easily is relative term.  There is NOT going to be a painless process to replace a PPL with a source code lvlib.

If you really need to make this happen you are going to need to use some LabVIEW "NI"nja training. 

Key tips for the NInja learner;

• Make sure your SCC repository has been setup. 
• Require Commit comments and Commit/Revert often.  Yes, revert will be an option at each step! And DON'T FORGET IT!  you are going through a swampy jungle and may need to go back and try alternate paths.
• Be very familiar with the VI Hierarchy view.  You are going to need it and all of its layout and search features.   Take some time to review the Help File on the Hierarchy View and actually go through the mechanics of the right-click, Tool bar and Menu items.

That is the homework now we are still not ready to just jump in.  We need to do some preliminary research and see what scary things lie in wait to bite or trap us. Inspect the lvproj in Hierarchy view look for;

• PPLs that call into other PPLs.  These will need to be fixed at the source lvlib project first prior to touching the main application project.  DOCUMENT THE DEPENDENCIES!  This is your "map" 
• Circular dependencies.  If you find any,  go to the nearest bank teller and buy several rolls of coins.  You will need them for the office "swear jar."  You should not have any circular dependencies and it's better to bite the bullet and resolve them before going further into the jungle.

After that, it's a matter of starting top down in the Hierarchy, 1 PPL at a time; opening the application project and replacing the lvlibps with the source lvlibs.  (Save and Commit)

Finally,  find a local charity and donate the proceeds in the swear jar.

And yes, that's the Easy way!  You don't want to try the hard way!

---

[JÞB]

---

@crossrulz wrote:

---

@sziszkont wrote:

I have a lvproj file with many lvlib and some lvlibp files. There is a lvlibp file that is also available in lvlib format. How can I replace it easily? I need all caller VIs of that packed project library (lvlibp) in the LabVIEW project to update with the qualified names of the "regular" library (lvlib).

---

Right-click on the PPL in the project and choose "Replace With...".  You can then find the lvlib file.

---

You are an optimist!  (Maybe just a little TOO used to dealing with well designed projects)