[Scons-users] max-drift vs. Decider

[Bill Deegan]

Alexander,


>From the SCons man page:

http://www.scons.org/doc/production/HTML/scons-man.html
--max-drift=*SECONDS* Set the maximum expected drift in the modification
time of files to *SECONDS*. This value determines how long a file must be
unmodified before its cached content signature will be used instead of
calculating a new content signature (MD5 checksum) of the file's contents.
The default value is 2 days, which means a file must have a modification
time of at least two days ago in order to have its cached content signature
used. A negative value means to never cache the content signature and to
ignore the cached value if there already is one. A value of 0 means to
always use the cached signature, no matter how old the file is.


-Bill



On Sat, Mar 30, 2013 at 11:22 AM, Alexander Tsvetkov <xflower at gmail.com>wrote:


>

> Dear Scons!

>

> I'm (unsuccessfully) trying to understand the subtle relationship between

> max-drift parameter, MD5 decider and MD5-timestamp decider.

>

> To be specific, how comes that after setting max-drift=0, changing the

> file does not cause recompiling?

>

> Thank you!

>

> _______________________________________________

> Scons-users mailing list

> Scons-users at scons.org

> http://four.pairlist.net/mailman/listinfo/scons-users

>

>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://four.pairlist.net/pipermail/scons-users/attachments/20130330/c7bec1f3/attachment.htm>