> So one could just print the PE timestamp (getting it thru, er, a simple
but undocumented trick).
That will work even if you don’t recompile the .c file that contains
SourceCppIdentify.
Do you mean __ImageBase?
http://stackoverflow.com/questions/25771/output-compile-time-stamp-in-visual-c-executable
There is also TIMESTAMP – if that isn’t also broken – but it is
just file date not build date.
At least you didn’t get used to C99 function directives, MSC never
properly handled those.
TIMESTAMP is in the same gulag as TIME and DATE.
Mark Roddy
On Wed, Dec 5, 2012 at 8:01 PM, Lee Fisher wrote:
>
> So one could just print the PE timestamp (getting it thru, er, a simple
>> but undocumented trick).
>> That will work even if you don’t recompile the .c file that contains
>> SourceCppIdentify.
>>
>
> Do you mean ImageBase?
> http://stackoverflow.com/ questions/25771/output-
> compile-time-stamp-in-visual-**c-executablehttp:
>
> There is also TIMESTAMP__ – if that isn’t also broken – but it is just
> file date not build date.
>
> At least you didn’t get used to C99 function directives, MSC never
> properly handled those.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.**cfm?name=ListServerhttp:
></http:></http:>
“Lee Fisher” wrote in message news:xxxxx@ntdev…
>
>> So one could just print the PE timestamp (getting it thru, er, a simple
>> but undocumented trick).
>> That will work even if you don’t recompile the .c file that contains
>> SourceCppIdentify.
>
> Do you mean __ImageBase?
> http://stackoverflow.com/questions/25771/output-compile-time-stamp-in-visual-c-executable
Yes.
– pa