How LVLIB stores the references to its member files?

[MimiKLM]

Hi,

Exactly as in the subject. Is it a relative path or absolute path?

[tst]

I haven't looked specifically, but I'm assuming it's basically the same as every other path:

1. Relative if it's in the same volume.
2. Absolute if it's in another volume.
3. Logical if it's in a logical folder (like vi.lib).

You can check it yourself easily enough by opening the file in notepad and looking at the paths. It should be a simple ASCII file.

[Pappion]

How would I make this relative enough to allow the project and lvlib be moved?

<Item Name="Initialize.vi" Type="VI" URL="/&lt;instrlib&gt;/YourNameHere/Public/Initialize.vi"/>

[CMal]

---

@Pappion wrote:

How would I make this relative enough to allow the project and lvlib be moved?

<Item Name="Initialize.vi" Type="VI" URL="/&lt;instrlib&gt;/YourNameHere/Public/Initialize.vi"/>

---

In your case, the lvlib is referencing a VI in the instr.lib folder, which is a symbolic path that LabVIEW recognizes.  When you reference something in a symbolic path, you can safely move the caller to any location without worrying about linking errors.  Just don't try to move any VIs that are inside the symbolic paths (instr.lib, vi.lib, user.lib,...) because LabVIEW already knows how to find them.

Chris M

[Pappion]

I want to make a customized renamed copy of the project+lvLib and keep it seperate so it doesn't get stepped on by our data base update.

I find this all to be extremely frustratiing. LabView used to be an easy language to play in.

The stock drivers do not cover 100% of features, may have some serious bugs, and are not tested with all versions of the instrument.

I tried editing the lvlib and lvproj paths. It works until I move the instrument project. I don't know how to cut the cord.

[tst]

---

@Pappion wrote:
I find this all to be extremely frustratiing. LabView used to be an easy language to play in.

---

I think it's still fairly easy - just do everything in the project explorer. If you want to create a copy of the project, open it and select Save As, then select the relevant option. The same is true of a .lvlib - just right click it in the project explorer and do a save as with the relevant options. Note that because LV files reference each other as described in my first reply, you might have to save some of the files if LV asks you.

Another useful tool is the files tab of the project explorer - it allows you to see if you're calling items from places you don't want, and you can then use the save as options to replace them with a copy.

[Yamaeda]

Open the lvlib in a text editor and check, it's an XML file. 🙂

I've seen both.

/Y

[Pappion]

I developed a manual process to do it.

I have only done it once, so the attached file is more of a guideline.