Re: How to turn off compiler/linker timestamping?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Dean Ramsier (ramsiernospam_at_nospam.com)
Date: 06/04/04 

Date: Thu, 3 Jun 2004 21:57:00 -0400

Note also that this topic has been discussed a few times, with the same
result. Others have done this kind of comparison to try to demonstrate
validity. You might try searching the newsgoups to find that old thread. 

-- 
Dean Ramsier - eMVP
"Michael J. Salamone [eMVP]" <mikesa#at#entrek#dot#com> wrote in message
news:uHu6ygZSEHA.3140@tk2msftngp13.phx.gbl...
> I don't believe there is a way to turn off the time stamping (by linker).
> You can see the time stamp by running dumpbin /all on the executable.
>
> The only thing I can think of is to roll your own comparison tool - one
that
> parsed through the PEF and ignored the time stamp.  Would be a bit painful
> to write, but the PEF is well-documented and you could do it.  Perhaps
there
> is a (free) utility that already does it.
> -- 
>
> Michael Salamone [eMVP]
> Entrek Software, Inc.
> www.entrek.com
>
>
>
> "Michael Schwab" <michael.schwab@cobecv.com> wrote in message
> news:eNxLbQYSEHA.2780@TK2MSFTNGP09.phx.gbl...
> > Everytime we re-compile/link our software, the CRC on the executable
file
> > (.exe) changes, even if we have made no changes in the source code.
Doing
> a
> > diff shows 1 or more byte changes in three widely separated areas of the
> > file.  More bytes are changed the longer it's been since the last
compile.
> > This pattern makes me think these are some sort of compile-time stamps
> being
> > embedded in the exe file itself.  I don't know if it's the compiler or
> > linker that's doing this.  This happens with eVC++ 3.0 through 4.0 SP3.
> >
> > This makes it impossible to do a validation build from the source code
> > control system copy and prove that there have been no changes, since the
> CRC
> > is always different.
> >
> > Is there some compiler/linker option to turn off this embedding of
> > timestamps, so that the exact same .exe file is created every time you
> > recompile?
> >
> > Thanks,
> > Michael Schwab
> >
> >
>
>

Relevant Pages

  • Re: How to turn off compiler/linker timestamping?
    ... You can see the time stamp by running dumpbin /all on the executable. ... "Michael Schwab" wrote in message ... More bytes are changed the longer it's been since the last compile. ... > embedded in the exe file itself. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: How to get the current source file date instead of oday ?
    ... Then, in /docroot, I have the following which I use to compile 'the book'. ... % what I want is time stamp for each included file -- following doesn't ... consectetur adipiscing elit. ... Aenean ultrices, libero non gravida hendrerit, elit velit varius nunc, vitae sollicitudin diam arcu ut metus. ...
    (comp.text.tex)
  • Re: Better organization for the Busy Developer
    ... What I mean is that it shouldn't change the time stamp just to compile. ... I think the problem is that SCX files don't become code and in the process ... To build the app, it strings together all those objcode memo fields in the ...
    (microsoft.public.fox.programmer.exchange)
  • Re: How to get the current source file date instead of oday ?
    ... Then, in /docroot, I have the following which I use to compile 'the book'. ... %\fancyhf% clear all header and footer fields ... % what I want is time stamp for each included file -- following doesn't work ... If I try this explicitly, it more or less works, but what I want is for the call to \getfiledate to pull the time stamp for each included chapter. ...
    (comp.text.tex)
  • Re: Gfortran on Windows (was Re: Fortran Newbie - Where to start?)
    ... After unpacking the .zip file and adding the paths to the root of the ... A minimal test setup to compile 'hello, ... (-s reduces the size of the .exe file, ...
    (comp.lang.fortran)