LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why does every compile produce a different binary file

Hi,

 

We are using a new configuration management tool and due to this we had to prove that we could take projects back out and reproduce the original binary files. Every time we tried this the new binary file matched the original in terms of size, but the actual data had differences.

 

After a bit of experimenting it was noticed if you force CVI to recompile a project you can never get the exact same binary file, even a recompile straight after making the first one. Anybody now why this is the case, or why we are seeing this?

 

Creating custom step DLL's to be used in Test Stand 4.0 with CVI 8.0.1

 

Thanks in advance

0 Kudos
Message 1 of 5
(3,206 Views)

I take you use CVI, while you posted in the LabVIEW board.

 

However the builds made with LabVIEW have some additional info that is related to the actual build time. I guess the same goes for CVI (and many other compilers).

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 2 of 5
(3,199 Views)
You've posted this in the LabVIEW forum. You actually want the LabWindows/CVI forum.
0 Kudos
Message 3 of 5
(3,199 Views)

That was our initial take, that it would just be time stamps information. Until that is we used a comparison tool and there were differences throughout the files and sometimes in blocks that were just too big to be time stamp information alone.

 

 

0 Kudos
Message 4 of 5
(3,165 Views)
ps sorry for posting in the forum, I have now reposted in the correct forum
0 Kudos
Message 5 of 5
(3,161 Views)