From: Nobody on
Links:

http://en.wikipedia.org/wiki/WinMerge
http://winmerge.org/


From: gast128 on
On 10 mrt, 23:19, "R I G Consulting, Inc." <rig_pos...(a)yahoo.com>
wrote:
> I am looking for a microsoft or public domain tool that can diff two
> binary files (exe, lib or DLL) and able to concur if they are
> identical or not *ignoring* the header details such as time stamps.
> The idea is to find if two binary files built during two different
> time period are identical.

When building the same project twice, the resulting binary differs,
since pdb guids and maybe timestamps are incoperated. U can use
dumpbin to compare only the content, which is described in kb article
Q164151.
From: Liviu on
<gast128(a)hotmail.com> wrote...
> "R I G Consulting, Inc." <rig_pos...(a)yahoo.com> wrote:
>> I am looking for a microsoft or public domain tool that can diff two
>> binary files (exe, lib or DLL) and able to concur if they are
>> identical or not *ignoring* the header details such as time stamps.
>> The idea is to find if two binary files built during two different
>> time period are identical.
>
> When building the same project twice, the resulting binary differs,
> since pdb guids and maybe timestamps are incoperated. U can use
> dumpbin to compare only the content, which is described in kb article
> Q164151.

That article is rather old and referring to VC v6, though the principles
still apply. It likely predates the bindiff.exe utility I mentioned in
my other post, which appears to have been originally meant to automate
such comparisons (and does still work in non-debug/unmanaged cases).

Unfortunately, bindiff itself hasn't been actively maintained in a
while, and is missing a number of options relevant to real life usage,
such as ignoring .pdb paths and timestamps.

So, yes, dumpbin is the last resort as always, but I still wish there
were a more direct and painless way to verify "reproducible builds".

Liviu