CODEWITHSUNDEEP
gitsvnlabview
running.t
running.t

Reputation: 5709

Is it a good idea to store LabView source code in git repository?

I am trying to choose best revision control system for a LabVIEW project.

In this and this article from National Instruments i have found that it might be a good idea to use SVN.

But I was wondering if I could use git (because I am used to it), and what are possible downsides comparing to SVN or any other version control system mentioned above.

As far as I know git is designed to store text files and LabVIEW source code are binary files. Hovewer I have found that many people are using LabVIEW with git. There are even github projects, that integrates LabVIEW with git.

So generally is it a good idea to use git and what are pros and cons?

Upvotes: 1

Views: 1597

Answers (1)

Yair
Yair

Reputation: 2276

I wouldn't know since I never used git, but the obvious major issue is merging, which can be much more of a pain in LV than in text - if you're planning on people working in parallel with other people and then merging, then that's the area I would look closely at. This isn't specific to git, but it can be more commonly needed with distributed systems. The other thing I would be concerned with is whether everyone you're working with can use the system without getting confused about the concept of local and remote repos.

We use SVN, which works reasonably well for the binary files (it stores a local copy for comparisons), and I'm guessing the only reason I would want to change to a DVCS (git, hg, etc.) is the ability to do local commits, which would make experimental code easier to do.

There are occasional discussions on the pros and cons of each and you can look one up. One relatively detailed one is this one, but it is from a few years back:

https://decibel.ni.com/content/blogs/Matthew.Kelton/2011/09/30/labview-and-versionsource-code-control--introduction

Upvotes: 2

Related Questions