MSVC_BATCH retrieves unnecessary files from CacheDir() #2503
Labels
batch build
bug
cachedir
has patch
Issue has attached Patch
Op Sys: Windows
Version: 1.2.0.d20090905
Milestone
This issue was originally created at: 2009-10-19 14:04:27.
This issue was reported by:
djvanmaren
.$CHANGED_SOURCES
with$(
and$)
in$CXXCOM
& friends seems to fix this problem, so that only the changed file (or the file with the missing.obj
) gets compiled.CacheDir
is in use, all the.obj
files will be retrieved from the cache (when only one should need to be).The (soon to be) attached zip of source files and an SConstruct file can reproduce these problems:
cd scons-test-case
scons .
should buildtestlib.lib
,a.obj
, andb.obj
a.obj
.scons .
should build onlya.obj
and be done, but it builds botha.obj
andb.obj
.Then, to reproduce problem 2:
env.CacheDir(cache)
scons . --cache-force
should copy*.obj
,testlib.lib
tocache
subdirectory.a.obj
scons .
should retrieve onlya.obj
from cache, but it retrievesb.obj
as well.Created an attachment (id=638)
Sample test case to reproduce problem
Created an attachment (id=639)
Patch apparently addressing first problem
Created an attachment (id=640)
Patch that seems to fix first part of issue.
Use later version of scons-batch-patch.diff, as it fixed a small typo. Sorry for confusion.
See discussion for more details:
http://scons.tigris.org/ds/viewMessage.do?dsForumId=1272&dsMessageId=2408284 (dead link)
SK to research, then 2.1 p3 if fix needs work
actually assign to SK
I can not reproduce problem #1 with either the current trunk (r4591) or with 1.2.0.d20090905 (r4346):
Putting
$( $)
around$CHANGED_SOURCES
should not have any effect on what$CHANGED_SOURCES
expands to, so there must be something else going on there.The second problem (pulling too much from cache) is easily reproducible and needs a little more investigation. Changing the Summary to reflect that problem and setting priority and milestone per bug triage.
Should this be returned to issues@scons so someone else can possibly have a crack at it?
Bumping all old issues targeted for past releases to 2.x.
Sample test case to reproduce problem
Patch apparently addressing first problem
Patch that seems to fix first part of issue.
The text was updated successfully, but these errors were encountered: