LabView and Git

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.

Top Replies

scottiebabe over 1 year ago in reply to Jan Cumps +3

Labview appears to have a VI compare tool Difference including cosmetic changes
Jan Cumps over 1 year ago +3

taifur 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…
Andrew J over 1 year ago in reply to scottiebabe +2

I did, and developing a couple of frameworks for testing with it as well. Then NI decided NXG wasn't the future after all and canned it so all that effort was , really, wasted. It was more than annoying…

0 Jan Cumps over 1 year ago
No. I have no relevant experience with it.

I have a github repo for the driver of our Pico SCPI labTool. But it is not on source line level. I will post a link to it.

My approach:

I created a repo, with a .gitignore specific for LabVIEW.

I use commits, branches and pull requests just like for a C project.

No solution for working together in parallel
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Andrew J over 1 year ago in reply to Jan Cumps

Ok, thanks. Thought I'd check first. LabVIEW and Git don't natively integrate so it's a question of managing outside and setting up an appropriate .gitignore and .gitattributes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jan Cumps over 1 year ago in reply to Andrew J

link to that LabVIEW repo: https://github.com/jancumps/pico_scpi_labtool_labview_driver
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Andrew J over 1 year ago in reply to Jan Cumps

I may well take a copy of that .gitignore! For a single developer I don't suppose some problems are likely to occur but it would seem that auto-merging text files like a .lvproj may well cause an issue in a multi-dev environment.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 scottiebabe over 1 year ago in reply to Jan Cumps

Congrats on joining JC as one of the LabView Professionals!
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 scottiebabe over 1 year ago in reply to Jan Cumps

Labview appears to have a VI compare tool

Difference including cosmetic changes
Cancel
Vote Up +3 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Andrew J over 1 year ago in reply to scottiebabe

I have spent time (wholly wasted now..grrrrr) working with LabVIEW NXG so I am somewhat familiar. LabVIEW is different though so it will take some time to get to grips with the differences. I am certainly not anywhere near as experienced as Jan, probably no more than yourself.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Andrew J over 1 year ago in reply to scottiebabe

Indeed it does. This runs outside of source control though as I understand it.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 scottiebabe over 1 year ago in reply to Andrew J

Googling "Labview NXG" lead me straight back to you, A+ for organic search success!

LabVIEW NXG Community Edition: Post 1 - Review

I will have to give it a read, it looks like you spent a lot of time and effort reviewing!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Andrew J over 1 year ago in reply to scottiebabe

I did, and developing a couple of frameworks for testing with it as well. Then NI decided NXG wasn't the future after all and canned it so all that effort was , really, wasted. It was more than annoying...

I'm not sure you'll get much out of reading a review of it now, except of course to admire my excellent prose, or help you sleep.
Cancel
Vote Up +2 Vote Down

Sign in to reply

Verify Answer

Cancel