I’ve been working with scons for the first time and I’m making changes to source code.
The problem is after compilation finishes if i close the command prompt and reopen it to compile changes, it starts compiling all source codes again.
p.s. : keeping cmd open doesn’t trigger the issue
Is this windows linux or mac?
Im not sure how the mechanism works to sense file changes, but my guess is that maybe there are environment variables lost when you close and open a new terminal. Or something touches a file in a way that tricks the build system to redo everything.
Here are the docs that describe how scons can sense file changes.
1 Like
Could it be an issue with the Python installation? Did you install it for the current user only or the whole system?
Its Windows. and yes ive read the scons documentation but it seems its describing how single file compilitation works couldnt figure out how project should be managed
current user I guess, I use single(Admin) User but I think that might be relevant cuz after I’ve installed scons I had to add its environment variable manually due to an error I was facing at the beginning.
so do u think re installing python+Scons might solve it ?
The decider can be set for the whole project in the SConstruct and can be overrided in individual modules SCsub. See the last section of the doc.
Looking at the scons there is only one build option to modify the Decider from its default (md5 checksum).
I think the python environment is probably the better lead though. I couldn’t find anything interesting in scons build system.
1 Like
ok i dont know if i did the right thing or not but changing the the argument of decider in Sconstruct to “content” seems to be working now. as what has been written in scons docs “MD5-timestamp” seems to be depricated.
thanks for your respond @pennyloafers
env.Decider(“MD5-timestamp”)
to
env.Decider(“content”)
1 Like