Anyone using CVS with Labview?

[Mark_Ireton]

I found some software (http://www.jalindi.com/igloo/) that looks like it would provide a Microsoft SCC API for CVS. Has anyone used this or another API for CVS with Labview?

[Jim_Kring]

I am currently using Tortoise CVS, which provides CVS control that is integrated very nicely into Windows explorer. I am using this to connect to our CVS repository on SourceForge.net for the OpenG Application Builder project. This is not really an API for CVS, but it works very nicely. I think that I noticed in the Jalindi Igloo tool, you must manually set the Binary flags of files. Tortoise CVS takes care of this automatically, which is a big help.

-Jim

Tortoise CVS

OpenG Application Builder

SourceForge.net

[JeanPierre]

I don't know how LabVIEW interfaces with SCC APIs but it would be nice to have CVS more tightly integrated. If someone knows how to plug-in Jalindi Igloo or other CVS tool into LabVIEW's SCC or have info on that matter, let me know.

TortoiseCVS already provides a nice and simple user interface in Windows Explorer, I would like to have it invoke the "Compare VIs" tools when there is a revision conflict.

[Mark_Ireton]

I've had success using Jalindi Igloo with CVI and TestStand. Looks like Labview is hard-coded (?) to use either built-in SCC or Micro$oft Visual SourceSafe. If NI could figure out how to get Labview to work with Igloo, we'd have a very nice and inexpensive solution.

[Greg_McKaskle2]

> I've had success using Jalindi Igloo with CVI and TestStand. Looks
> like Labview is hard-coded (?) to use either built-in SCC or Micro$oft
> Visual SourceSafe. If NI could figure out how to get Labview to work
> with Igloo, we'd have a very nice and inexpensive solution.
>

There shouldn't be any problem with using CVS, but it is not currently
integrated into the LV menus and save/load. You should be able to use
the CVS commands via either command line or any interface it may
present. If you find that you want to do a bit more integration, you
can add any VIs that you write to the tools menu by adding them to the
project folder.

Greg McKaskle

[JeanPierre]

I have hit a bug with builtin SCC in LV6.0 where almost all VIs in the project are flagged that the local copy is modified when it is not. No matter how I re-save, re-checkin, re-checkout, the modified flag stays (unless the front panel is opened). I have contacted NI support and they haven't found the source yet. They spent a lot of time on this but the bug persists even after conversion in LV6.1.

That to say that I am moving to CVS at my workplace, after having success with it on sf.net for OpenG projects.

>There shouldn't be any problem with using CVS, but it is not currently integrated into the LV menus and save/load.
Jalindi Igloo being SCC API compliant I wonder why LabVIEW hasn't a generic SCC API interface
instead of a specific interface with VSS. Integration with CVS is on my wish list and I'll keep asking.

In the mean time, is anyone interested in an OpenG project to build LabVIEW CVS tools around the CVS command line client? Reply here on DE or contact me at jpdrolet@users.sourceforge.net

[Rolf]

Wouldn't it be just as easy and probably more efficient to use the DLL
interface of the CVS libraries. Seems like a CVS plugin to the LabVIEW SCC
system shouldn't be any more complicated than writing a completely different
system.

Rolf Kalbermatter

"Jean-Pierre Drolet" wrote in message
news:506500000005000000A4960000-1027480788000@exchange.ni.com...
> I have hit a bug with builtin SCC in LV6.0 where almost all VIs in the
> project are flagged that the local copy is modified when it is not. No
> matter how I re-save, re-checkin, re-checkout, the modified flag stays
> (unless the front panel is opened). I have contacted NI support and
> they haven't found the source yet. They spent a lot of time on this
> but the
bug persists even after conversion in LV6.1.
>
> That to say that I am moving to CVS at my workplace, after having
> success with it on sf.net for OpenG projects.
>
> >There shouldn't be any problem with using CVS, but it is not
> currently integrated into the LV menus and save/load.
> Jalindi Igloo being SCC API compliant I wonder why LabVIEW hasn't a
> generic SCC API interface instead of a specific interface with VSS.
> Integration with CVS is on my wish list and I'll keep asking.
>
> In the mean time, is anyone interested in an OpenG project to build
> LabVIEW CVS tools around the CVS command line client? Reply here on DE
> or contact me at jpdrolet@users.sourceforge.net