How do I avoid recompilation of VIs on different machines

[Ken Pietrzak]

We have several developers working on a labview project. The finished product will go on several target machines. We use the revision number, time, and date for version control. We use several addon toolkits (e.g. motion) which were compiled in earlier versions of labview. The llbs in these addon folders in vi.lib get recompiled on each machine at a different time and date. Therefore our project code gets recompiled on each machine that it is installed on which wrecks havoc on our version control process. The only way that I know to fix this problem is to save those folders from one machine and overwrite the existing folders with the saved folders on each target machine. Is there a better way? Why does lab
view have to recompile vis when the only change is the time and date of the subvis that it uses, i.e. there is no code change?

[EdDickens]

A path change to the sub-VIs also causes a recompile. Make sure all of your development machines have the LabVIEW installations and your project files in the same locations. I setup all of our machines with LabVIEW installed at "c:\National Instruments". This puts all the vi.lib, user.lib, instr.lib directories in the same relative place accross machines.

Another thing I do is a mass complile on a single machine, then sync the vi.lib, user.lib, tools and any other directories to my other machines. (I use a freeware app called Treecomp, works great) This really cuts down on the little code changes you are describing here.

Ed

[LarsRoe]

You can look at the current changes for a VI by going to VI Properties and clicking on the "Current Changes..." button.

[Ken Pietrzak]

Thanks, yes that must be it. The folders on the other machines must have slightly different names. I tried reinstalling the addon code on my machine and recompiling (therefore different date and time) and none of my project code recompiled.

[EdDickens]

I forgot to mention that different file dates don't cause a recompile.

But finding a subvi at a different path, even if it's the exact same file, will cause the top level to recompile.

Ed

[Ken Pietrzak]

Thanks, but is there any way to determine which Subvis caused the recompilation?