[Scons-users] Rebuild changed targets
Johan Holmberg
johan556 at gmail.com
Sat Mar 23 21:19:24 EDT 2013
On Fri, Mar 22, 2013 at 8:52 PM, Dirk Bächle <tshortik at gmx.de> wrote:
> Hi Mike,
>
>
> On 22.03.2013 19:26, Mike S. wrote:
>>
>> For some reason SCons doesn't regenerate an intermediate target if it's
>> modified. Am I doing something wrong?
>>
>
> no, you're doing nothing wrong. It's just the current behaviour of SCons,
> which doesn't track changes "from the outside" for targets. Things get only
> rebuilt if SCons detects that one of the sources (or inbound dependencies in
> general) changed.
> Please also refer to the recently opened issue
>
> http://scons.tigris.org/issues/show_bug.cgi?id=2892
>
> for more infos.
>
> Best regards,
>
> Dirk
>
This issue has been discussed before several times. Look for example
at the following thread from 2008:
http://scons.tigris.org/ds/viewMessage.do?dsForumId=1272&dsMessageId=80582
An issue in the bug tracker was added then (but there has been no action to it):
http://scons.tigris.org/issues/show_bug.cgi?id=2230
I think it is interesting that Cons (the Perl-program, around year
2000) worked better in this case. As the bug-report above says:
"We should add back in Cons-classic-style validation of target files using MD5
checksums stored in the .sconsign database."
/Johan Holmberg
More information about the Scons-users
mailing list