[Scons-users] Handling deleted source files

[Tom Tanner (BLOOMBERG/ LONDON)]

Is it possible your SConscript is accessing the .o files with a Glob or an explicit Depends(target, thing.o) or something similar.

It should only look at the .o files if you have a dependency and if you don't, they're just rubbish lying around.


----- Original Message -----
From: scons-users at scons.org
To: scons-users at scons.org
At: Jun 27 2013 13:15:45

Hi,

Whenever somebody deletes (or renames) a source file in our project, scons
will fail the next build because it finds the existing .o file in the
variant directory, but doesn't know how to create it as the .cpp file has
disappeared underneath it.

scons -c before updating from source control does fix it but:
  1. This causes a full rebuild which is very slow
  2. You have to know that somebody else has deleted a file before you
update your source

Is there a SCons way around this?

Googling "scons deleted source files" didn't find me anything so I suspect
this is a failing in my usage of SCons rather than with SCons itself.

Thanks,

Dan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 8690517976555002.txt
Type: application/octet-stream
Size: 149 bytes
Desc: not available
Url : http://four.pairlist.net/pipermail/scons-users/attachments/20130627/410d2bb9/attachment.obj