Mercurial User Group

Getting Started with Mercurial in LabVIEW

About

Mercurial is a distributed version control system. I played around with it and its really easy to set up and use version control for your LabVIEW Projects.

This group is for all mercurial LabVIEW users and interests, so feel free to post/discuss anything related.

I set up a project to develop LabVIEW integration of mercurial (http://decibel.ni.com/content/projects/mercurial-labview-integration). The (sure mercurial) source code repository is hosted at https://bitbucket.org/AndreasS/mercurial-labview-integration, so go ahed, check it out and improve it.

Getting started with mercurial

Hg Init: a Mercurial tutorial           http://hginit.com/

Mercurial homepage:                   http://mercurial.selenic.com/

Mercurial: The Definitive Guide:     http://hgbook.red-bean.com/

Learning Mercurial in Workflows:  http://mercurial.selenic.com/guide/

Quick Start Guide to TortoiseHg:  http://tortoisehg.bitbucket.org/manual/2.0/quick.html

Installation of Mercurial for use with LabVIEW

  1. Download and install mercurial + TortoiseHg Windows client from http://tortoisehg.bitbucket.org/
  2. Download and install the LabVIEW Mercurial Integration from https://bitbucket.org/AndreasS/mercurial-labview-integration/downloads
  3. Try out the Hg Init Tutorial using TortouiseHg and LabVIEW
  4. Give Feedback!

LabVIEW project integration

I've release a tool for using the LabVIEW project with Mercurial. It's available for download at Bitbucket for LabVIEW 2011 Professional.

Links

Andreas Stark
Senior Transportation Systems Engineer
Message 1 of 18
(16,574 Views)
17 REPLIES 17
Highlighted

Re: Getting Started with Mercurial in LabVIEW

Hi,

I downloaded the LVdiff tools and have a poblem with it. I am using LabVIEW 2011 32-bit on a Windows 7 64 bit machine.

Having a quick look the problem is base around the fact that it creates the lvdiff2 dir in the Program Files (x86) dir, which is good as that is where LabVIEW 2011 is installed, but the settings in the TortoiseHg ini file all refer to C:\Program File\National Instruments instead.

I have just cloned to code from bit bucket to have a better look

cheers

Danny

Danny Thomson
0 Kudos
Message 2 of 18
(8,631 Views)
Highlighted

Re: Getting Started with Mercurial in LabVIEW

Hi,

I created an issue for this: https://bitbucket.org/AndreasS/mercurial-labview-integration/issue/6/modify-paths-for-64-bit

Andreas Stark
Senior Transportation Systems Engineer
0 Kudos
Message 3 of 18
(8,631 Views)
Highlighted

Re: Getting Started with Mercurial in LabVIEW

0 Kudos
Message 4 of 18
(8,631 Views)
Highlighted

Re: Getting Started with Mercurial in LabVIEW

Hi Danny,

you're right raising these issues directly in bitbucket. Your suggestions totally right. My intend initially was to get a installer for totally inexperienced mercurial users. That's why I choose to overwrite the user name, but I think this should be optional.

I'll try to fed in the changes if nobody else want's to upload a new version of the code to bitbucket.

Andreas Stark
Senior Transportation Systems Engineer
0 Kudos
Message 5 of 18
(8,631 Views)
Highlighted

Re: Getting Started with Mercurial in LabVIEW

Hi Andreas,

I've installed your tools and tried to use it but unfortunately I gave back this error as result.

lvdiff2_Memory_error.png

I'm using Windows 7 64bit and labview 2012....

I alse have installed labview 2010SP1.

How abot it?

Ricky
Italian Developer engineer
www.www.selt-sistemi.com
0 Kudos
Message 6 of 18
(8,631 Views)
Highlighted

Re: Getting Started with Mercurial in LabVIEW

@James

It seems the issue was due to the path of the program file on the windows 7 - 64 bit, updating the lvdiff2 as you suggested doing, the issue was solved. I downloaded the patch and installed it but, even though the first issue seems to be solved the lvdiff2 for Win64 can't still open the VIs, now the problem is that the lvdiff2 doesn't recognize the version of labview automatically and it is trying to open a LV2012 vi using LV2010sp1. It would be a very good thing if it was able to recognize the version of labview automatically!

Ricky
Italian Developer engineer
www.www.selt-sistemi.com
0 Kudos
Message 7 of 18
(8,631 Views)
Highlighted

Re: Getting Started with Mercurial in LabVIEW

Not sure why it would be memory full but it could be related to paths as that doesn't appear to use 64 bit paths. I have modified Andreas example for 64 bit OS at https://bitbucket.org/JamesMcN/mercurial-labview-integration/downloads

Andreas: Feel free to pull these changes into your repository, I have built on a fork of yours so should come back in easily enough.

James Mc
========
CLA and cRIO Fanatic
My writings on LabVIEW Development are at devs.wiresmithtech.com
0 Kudos
Message 8 of 18
(8,631 Views)
Highlighted

Re: Getting Started with Mercurial in LabVIEW

@James

It seems the issue was due to the path of the program file on the windows 7 - 64 bit, updating the lvdiff2 as you suggested doing, the issue was solved. I downloaded the patch and installed it but, even though the first issue seems to be solved the lvdiff2 for Win64 can't still open the VIs, now the problem is that the lvdiff2 doesn't recognize the version of labview automatically and it is trying to open a LV2012 vi using LV2010sp1. It would be a very good thing if it was able to recognize the version of labview automatically!

Ricky
Italian Developer engineer
www.www.selt-sistemi.com
0 Kudos
Message 9 of 18
(8,631 Views)
Highlighted

Re: Getting Started with Mercurial in LabVIEW

I've solve the second problem simply launching the right verision of labview before calling the Visual diff menu from tortoisehg. It works properly.

Ricky
Italian Developer engineer
www.www.selt-sistemi.com
0 Kudos
Message 10 of 18
(8,631 Views)
Reply
This is an open group. Sign in and click the "Join Group" button to become a group member and start posting.