Actions
Forum Thread Details
  • State Not Answered
  • Replies 12 replies
  • Subscribers 124 subscribers
  • Views 2036 views
  • Users 0 members are here
Related

LabView and Git

Andrew J

Hi  ,

amongst your many useful Git postings, have you ever created one about using LabVIEW with Git?  I can't find anything but I thought I'd ask before wandering off to the Interweb.

  • 0

      and I had our first experience, working together on a single LabVIEW project. It's a clunky experience.

    In particular because the binary nature of VIs:

    • You can't both work on the same VI and merge it.
    • You need to be on the same version of LabVIEW,
    • or agree upfront to save the result as a particular version
      but that touches each binary component, because it's on Project level.
    • Or work outside of the repository, and only move things in that you are finished with, saved in the pre-agreed version

    The project file is text based, but if you merge two people's changes, it may not be what you (nor the Project Explorer) would expect.

    Based on this experience. There may be much better WoW out there ...

  • 0 in reply to Jan Cumps

    If you look at the gitattributes file I created, practically all the LabVIEW files are treated as binary.  I think people have better experience with subversion or perforce.  I didn’t have much difficulty being a sole contributor with git, but doing anything in LabVIEW tended to flag a change even if there really wasn’t one.  There is a setting to improve the usage with git but I found it was set by default so it probably was with your installs - I can’t remember exactly, but I did document it in one of my blog postings.