That was me. I spent a few evenings trying to daemonise scons. The idea was to interface with libfam to detect filesystem changes. The time for a repeated build is then O(size of changes) instead of O(size of project). IMHO this is far faster than any caching optimisation could ever be.
Unfortunately, I found it quite difficult because of unfamiliarity with the scons code. When updating a node, it wasn't clear how to notify dependent nodes that they needed rebuilding - there seemed to be several state variables which were cached and no obvious way to reset a node to the 'I potentially need to be rebuilt' state.
Stephen.
Yeah this feature would be cool. There was something along the same lines which popped up long ago, which would be to have scons running as a daemon. It would do the processing of the SConscripts once, or any time it detects a change. That way when you start a compilation it goes directly to scanning targets and doing it's work without the preparatory step of running the SConscripts
bdbaddog
commented
3 years ago
This issue was originally created at: 2003-02-11 04:59:08. This issue was reported by:
stevenknight. stevenknight said at 2003-02-11 04:59:08issues@scons said at 2003-02-11 04:59:08
garyo said at 2008-03-17 20:39:43
Votes for this issue: 3.