LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Verify application includes latest VIs

Solved!
Go to solution

Hello again all you helpful forum-goers!

 

I need a way for an independent reviewer to verify that the LabVIEW application I built and checked in to my source code control was built with all of the latest versions of the VIs checked into source code control for my project.

 

Unfortunately, LabVIEW seems to build the application with a slightly different size in kB on every computer which we use to do so, nevermind an MD5 checksum.  Some of the differences make sense, like when someone uses a version of LabVIEW with a different service pack installed, or even when it is being built on a 64-bit computer vs. a 32-bit computer (nevermind the fact that both are running the same 32-bit version of LabVIEW).  But we've managed to get a setup where two computers are exactly the same in the above two respects, and they still end up with an application with a slightly different size.

 

The goal, as stated above, is to make sure the application checked in contains all of the latest code.  We were resigning ourselves to just checking the size of the application as a "good-enough" solution.  Now even that isn't working.

 

Is there any good way to perform this check that I am not thinking of?

 

Thank you for your time!

 

-Joe

 

P.S.  I am using LabVIEW 2011, service pack 1.

0 Kudos
Message 1 of 5
(2,726 Views)
Solution
Accepted by topic author jmorris

For an exe, you could create a build log (and check it into source).  This is an option on the build specification's Advanced page.

 

each vi gets a line in the file as <full path> <last save time> <version>:

 

C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\Analysis\baseanly.llb\Mean.vi	1/13/2011 8:01:42 PM	38

 now you have all the info you need for checking.

 

Then again, this can make builds run slowly.

-Barrett
CLD
Message 2 of 5
(2,716 Views)

Thanks, Barrett!  That turned out to be exactly what I needed.  While the "last saved" date is different for many VIs when someone creates a new sandbox from source code control, the VI revision number is a good check for what I wanted.  Smiley Happy

 

-Joe

0 Kudos
Message 3 of 5
(2,695 Views)

Great!

 

btw I take back my "makes it run slow" comment, the particular project I had open this morning builds slow no matter what 🙂

-Barrett
CLD
0 Kudos
Message 4 of 5
(2,689 Views)

I did not notice my build going extra slow, but I did not time it, either.

0 Kudos
Message 5 of 5
(2,685 Views)