> I like Nate's date.cc idea... basically that says whenever you build a > binary, stick the current info in, but just because the info has > changed that's not sufficient reason to consider the binary out of > date. That's the same policy we use wrt the date and time.
Actually, I took a quick look and I'm not sure why date.cc works. It explicitly depends on all other cc files which is why it is rebuilt, but I'm not sure why the date change itself doesn't trigger a rebuild. It could be because __DATE__ is simply an implicit variable and the SCons scanner doesn't see any input changes and never scans the file again after the first time. We could add the hg revision to date.cc (and pass it in via a #define) and perhaps use the Ignore() directive on it? Lisa, want to give it a shot? Nate _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
