executable under version control

[Special]

We are using LabWindows/CVI and put all the source files under version control with QVCS. (Also the .exe file)

Two questions arise:

1)      When building a release executable, say a view minutes from each other (same project files) one gets two different binary files? How is this possible and is there a way to get the same .exe files? (the source files are after all the same)

2)      In one project we used the “NI USB 6008”, building the whole project (create release executable) on one PC where drivers where installed gave a file size of about 716Kb. Building this same project on a PC without drivers installed for the “NI USB 6008” gave a file size of 683Kb. The “init_NI_USB_6008.c and .h” where included in the project.

Which other files where needed to add to the project to be able to get the same executable? This is also important if we want to make a distribution kit!

Thanks.

[KvZ]

Hi,

1. How does the version control handle biniary files? Does it look at the creation date? Another thing to check would be to see if there is a date added to the resources of the exe file?

2. I don't know the init_NI_USB_6008.c file, what driver are you using? Usally you will need to have all the dependencies on the build system before you can build an executable. If you like to build a distribution kit you will also need the Driver Installer files it self inorder to include them in the distribution kit.

Karsten

[Special]

Hello karsten,

1. QVCS does not look at anything it just puts the files under version control. I compare the files myself and if I build the same project with NI CVI then the .exe should be the same! But the arn't? What is the reason?

2. This is clear. Building a executable on a different system (without the dependencies) is not possible.

Rob

[KvZ]

Hi Special,

I did a test here and I did see some differences in the header of the executable, the machine code was identical. This probably due too date & time and or build numders included in the header section. I also saw some additional differences in the trailer when I included the UIR files in the executable. And also the file size was exactly the same in all test cases.

Thanks

Karsten