View Single Post
  #31   Spotlight this post!  
Unread 17-01-2010, 17:49
Nibbles Nibbles is offline
Interstellar Hitchhiker
AKA: Austin Wright
FRC #0498 (Cobra Commanders)
Team Role: Alumni
 
Join Date: Jan 2008
Rookie Year: 2003
Location: Arizona
Posts: 103
Nibbles is just really niceNibbles is just really niceNibbles is just really niceNibbles is just really niceNibbles is just really nice
Re: C and LabView version control with Git

There is a 3rd party diff implementation called LVDiff which uses the existing VIs provided with the Development system to perform a diff. It has a bit of overhead, all you really need is to run a supplied VI with the two files and LabView will launch the diff tool (I have a .vi that can do this correctly parsing the command line arguments, I'll attach it when I get the chance). In the "2009" edition of the documentation (but not 8.6) there is a pre-provided LVCompare.exe file that does the same thing, compiled into a binary. LVMerge.exe is the official merge tool and is provided with our 8.6 version, but it doesn't seem to be writing over the correct file, instead returning a successful result, but not writing it out, thus taking one file as the merged result entirely ignoring the other... the only explanation I can come up with is a software bug.

I have played around with TortoiseGit (forked from TortoiseSVN), you can get two changes in two separate files to merge into one? I can get as far as calling LVMerge with the (as I understand) correct arguments (or using the merge under Tools->Source Control iirc).
__________________
Help standardize match data! Use the XML interchange format. (Specification page)
AAA_awright on Freenode IRC chat. (Join us at ##FRC on chat.freenode.net, or in your browser)
Reply With Quote