All geek questions in one place

How does version control work with LabVIEW VI?

Does anyone have experience with version control and LabVIEW? Since LabVIEW VI are not textual, how does it work? I would like to use git, but I have a few questions:

  • When making changes, does git recognize the differences in the VI or does the entire file replace with a new one? Does this lead to a large expansion of the repository?

  • Is it possible to combine different versions of VI?

  • Or is there a version control that works best for LabVIEW?

+5
source share
2 answers

When making a change, does git recognize the differences in the VI or replace the whole file with a new one? Does this lead to a large storage expansion?

Inputs are binary files, so git save the updated version as a new object. This can cause the LabVIEW repository to grow faster than the original plain-text database.

Is it possible to combine different versions of VI?

Yes. There is a tool that installs with LabVIEW called LVMerge.exe that can do this.

Or is there a version control that works best for LabView?

I like and use git with LabVIEW. I also use these helpers:

+7
source

To be fair, LabVIEW is more suitable for SVN.

There is an easy way to integrate LabVIEW SVN and SVN diff in a tortoiseshell SVN.

Read this article: http://digital.ni.com/public.nsf/allkb/1A300A1BB1833EE786257A7C0077B422

In addition, there is a set of tools for LabVIEW for working with SVN directly from the LabVIEW Project. http://sine.ni.com/nips/cds/view/p/lang/en/nid/211524

Here is the help to get started with git: https://decibel.ni.com/content/docs/DOC-37416

You can configure git diff and git merge for LabVIEW.

+3
source

Source: https://habr.com/ru/post/1246414/

More articles:


All Articles