Hey, Gabor!
> if the addon requirements are not met the code of that module is not > compiled, so there's nothing to clean up. > > Ok, that makes sense. I still don't feel that scons made it clear that that's what it's output meant. Clearly scons knew that there was stuff to clean up as the errors went away after I satisfied those dependencies. The dir I was working from clearly did have something to clean up as I previously compiled that part just fine. To remind you; I was moving files from one installation to another here. > it should not do this. all dependency checks are skipped if the clean > option is specified. about the libtiff issue, it's always good to check your > config.log file to see what went wrong. another thing is, Sorry. I likely flushed that when deleting the old install and starting anew. As I saw it those checks certainly weren't skipped as I got errors on those. The errors were correct as I still lacked some libraries and do want the AR stuff, my issue is (amongst other things) that that I didn't expect those errors there; I was sure those errors would emerge as I was trusting on scons to tell me what I was still missing, just not those parts at that stage, and not at the expense of cleaning. > if you cancel the library detection phase sometimes the data is incorrectly > cached so it's useful to clean the cache files and directories (.sconf_temp > and .sconsign.dblite) manually. > > I'm sure I didn't deliberately cancel any detection. I maintain that if I tell scons to "clean" I expect it to clean everything that was generated by scons, or -to put it in different words- anything not generated by git. The behaviour may be correct, it's just unexpected by me. Yours, Kas.
