LabVIEW

[d_n]

I would like to use Subversion as a Source Code Control tool. I have searched the NI site but I could not find anywhere if Labview 8 can be used with Subversion. Has anyone used successfully Subversion with any Labview version?

Many thanks

[Arno Euteneuer]

I just tried the LabVIEW 8 evaluation version together with a Subversion SCC plug-in (again an evaluation copy) from PushOK (http://www.pushok.com/soft_short_info.php) and it seems to work like expected. The SCC plugin is correctly recognized by LabVIEW and can be used to check in and out files etc. Only I wasn't able so far to use LVDIFF (http://meta-diff.sourceforge.net/index.html#lvdiff) as an "external" diff viewer from within LabVIEW. Maybe the reason is one of the limitations of the evaluation status. (It seems that the Call by Reference Node is not able to get the connector panel assignment from the NI comparision VI...)

Regards

Arno

[TimM(AE)]

Hi

LabVIEW 8 supports several third-party source control providers. Available source control operations in LabVIEW 8 are the same regardless of which third-party provider you select. Specific support or functionality for each operation varies by provider.

LabVIEW 8 includes two source control integration interface types. On Windows, LabVIEW 8 integrates with any source control provider that supports the Microsoft Source Code Control Interface. On non-Windows platforms, LabVIEW 8 integrates with Perforce using a command line interface. National Instruments has tested LabVIEW 8 with the following third-party providers:

• Perforce
• Microsoft Visual SourceSafe
• MKS Source Integrity
• IBM Rational ClearCase
• Serena Version Manager (PVCS)

Tim M

AE

[Derek Price]

I also got Subversion to work (eventually!) with LV8.  I, too, wish that the LV Diff would work.  If anyone has figured this out - please let us know!  For those interested, I used the single-click SVN installation available here (Windows) [1].  To get LV to recognize Subversion, I used the SCC proxy by PushOk [2].

[1] http://svn1clicksetup.tigris.org/
[2] http://www.pushok.com/soft_svn.php

Thanks

[kphite]

Derek,

Try using the meta-diff tool here: http://sourceforge.net/projects/meta-diff

 It works great even though it's not integrated within LV.

kph

[Jim_Kring]

I have gotten this working.  It is a two part problem:

1) lvdiff needs to be modified for LabVIEW 8.0, since the conpane of project\procmphier.llb\CMP compare two VIs.vi has changed.  Use the attached VI, but rename it from "lvdiff-8.0.vi" to "lvdiff.vi" and replace the one in the installed location (back up your original).

2) you need configure PushOK SVN Proxy to "Allow non modal view and compare windows (cause temporary files remain on disc)" [sic].  This checkbox can be set from the PushOK SVN Proxy properties dialog available from the Start>>Programs>>PushOK Software>>SVNSCC>>Configure plugin.

I'll work with Ian Dees (lvdiff author) to try to get my changes to lvdiff included in the main distribution.  We can make a fancier version that can handle any version of LabVIEW, intellegently.

Message Edited by Jim Kring on 12-30-2005 04:31 PM

[Khalid]

Just wanted to add a note -- hopefully will be of help to someone -- that the LVDiff v2.3 works with labVIEW 8.20 (and Perforce in my case):

http://sourceforge.net/projects/meta-diff/

Thanks,

-Khalid

[Joe_Gerhardste…]

I am using Subversion with LV 8.0.1 and TortoiseSVN.  This does not use the internal SCC tools in LabVIEW -- you need to check in/check out/merge through Windows Explorer.  I initially thought this might be more cumbersome than using the internal LV SCC stuff (I have used Perforce with LV 6i in a past life), but since our code is split up by libraries with each library in a different directory (and each library owned by a different developer), it actually works out very nice and solves one big problem I didn't like with Perforce/LV.  When working with LV's SCC tools, it likes to set everything as "read only" when checked in, and not-"read only" when checked out.  This prevents you from saving changes to VIs that are cross-linked to ones you are modifying (but are not checked out).  After a while, the number of VIs that want to be saved but cannot because of the "read only" becomes overwhelming (typically much larger than the number that you can actually save).  With Subversion, I can save changes to all these other VIs, then revert the directories backwards to the Head Revision at the end day when I check my actual changes in.
 

[JoeC]

I am trying to setup TortoiseSVN for use with subversion.  Does anyone know what the path and name of the executable for the differencing program in LV 8.6?  I would like to be able to do differencing using TortoiseSVN.  Tortoise does allow for External differencing engines as per the attachment doc1.

[Sappster]

Hi Joe,

I'm not extremely familiar with SCC but I will try and find your answer. Here is all the information I have for integrating scc in LabVIEW. Let me know if this helps.

SCC Setup