Mats Wichmann

> > [@asqui](https://github.com/asqui) - Please try the latest SCons verison 4.8.1 and let us know if that resolves it or not. > > Confirmed that this issue is reproducible on...

Okay, here's a capture of running through the original script again on my dev box (Fedora 40, Python 3.12, SCons master (which is 4.8.1+whatever changes have happened since). I've added...

My rebuild of the new example after modifying looks like this: ``` $ scons --tree=all --debug=explain scons: Reading SConscript files ... scons: done reading SConscript files. scons: Building targets ......

Okay, I can see the behavior you're seeing now. Looks to me because the content signatures are the same and the build signatures are the same, that there's indeed "nothing...

@cslamber do you mind if I move this to a different issue? It doesn't seem to be caused by using a timestamp-then-hash decider, which the original problem in this issue...

Meanwhile... in *this* case, if the timstamp-content decider is used, this particular example does detect a need to rebuild: ``` scons: building `SOURCE_Z.txt' because it doesn't exist CacheRetrieve(SOURCE_Z.txt): 1d73c40c0445892329f62492f64c1bd1 not...

> When using MSVSSolution with a variant build directory, the actual solution file is generated in the build directory instead of the source directory. There are seemingly endless cases of...

The problem is we're writing those files for something external to consume, and they have to go where it makes sense for that tool. To visual studio, it would make...

if you build a project file, it's for vs to use and includes how it calls scons to build. tbh I don't know what restrictions it has, but we do...

It seems other caching solutions do support hardlinking (see `ccache`, for example) - with caveats. Compression is not allowed when hard links are used - SCons doesn't do compression of...