Projekt-Explorer Pseudo intelligence

[bodo_online]

Hi,

I use the following environment.
Versioning with GIT.
The projekt is open in a “virtual drive”.
"M:\Main_Application\Framework.lvproj"
The advantage of this method is that I can handle different versions of the project, reuse it in other projects and
also I have of each PC the same link role.
Each vi is called from M.\
I also uses a lot of packed libs
LabVIEW search path standard + M:\
Compiling organization procedure: MGI Solution Explorer

My problem:
Sometimes LabVIEW load files from the real disk path
C:\GIT\Actor_Framework\Framework
This cause conflicts. Sometimes I also get linking conflicts in the “Packed Libs”. Those conflicts cannot be eliminate.
I try to delete the cache of complied objects without any solution.
I don’t know when an why LabVIEW change any paths and linking role, how I can fix it manually.
How can I deactivate this pseudo intelligence.

The project file XML contains just relative paths.


best regard,

Bodo

[GerdW]

Hi Bodo,

you should write your questions in English in this worldwide forum. For German discussions I can recommend the German www.labviewforum.de …

---

@bodo_online wrote:

How can I ensure that LabVIEW does not try to load VIs from sources that I have not specified?

How can I manually correct the paths for Packed Libs.

---

Do you use a "virtual drive" or a "network drive"? Why don't you use the "real" path C:\…?

Packed libraries contain compiled code, I guess you cannot change the compiled code after compilation…

[bodo_online]

see update above