LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Released executables not reproducable from compile to compile

I was surprised to see that the executables generated in release mode do not yield the same file contents from compile to compile. This is what I did:

1) "Mark project for compilation"
2) "Create release executable"
3) Renamed the newly created executable by added "_old" just before the ".exe".
4) "Mark project for compilation" again
5) "Create release executable" again
6) Using windows command prompt, I typed "fc/b file_old.exe file.exe" to yield a binary file compare.

I was expected maybe a handful of differences due to the difference in the exact time of compilation. What I got was an enormous list of differences. As an experiment I did things such as delete the obj file between compiles, close lab windows between compiles, etc. Nothing I do seems to build the exact same executable file.

Even though the executable files operate correctly, the different executable are not a good thing for source code version control.

Help!
Marcus
using lab windows version 7.0 on windows 2000
0 Kudos
Message 1 of 2
(2,893 Views)
Hello Marcus,

I was unable to reproduce the behavior you are seeing. I first deleted the cvibuild directory for my project, created my first release executable, renamed the file, deleted the cvibuild directory again, then created my second release executable.

From, there I ran the WinDiff tool that ships with Visual Studio 6, and the only difference it found was that one of the executable files was more recent.

If you remove the cvibuild directory before creating each release executable, do you still see the same behavior?

Thanks.
Wendy L
LabWindows/CVI Developer Newsletter
0 Kudos
Message 2 of 2
(2,860 Views)