#1897: MPI thorn builds when it shouldn't ------------------------------------+--------------------------------------- Reporter: hinder | Owner: Type: defect | Status: review Priority: blocker | Milestone: ET_2016_05 Component: EinsteinToolkit thorn | Version: development version Resolution: | Keywords: MPI ------------------------------------+---------------------------------------
Comment (by knarf):
Any new ideas about how to fix this?
Trying to summarize, we need:
a) a file that indicates to Cactus that something in the library configuration changed, especially after a re-build of the library by Cactus. So far, this is called 'done'.
b) a file that indicates that the library needs to be build. This is thorn-internal, and only passes that information from detect.sh to build.sh.
c) a file that 'saves' the last build date, to be able to skip build if build.sh wasn't updated (no new version available). This is also thorn- internal.
Initially, I tried to combine b) and c) into one file, 'available', but that was shown to be not sufficient. As it stands now, we don't have a solution which would combine b) and c) into one file. It would be nice to have only two files (simpler), but in absence of a solution using only two files, but the need for a solution in general, I only see one way forward: three files.
a) 'done': would not change from current behavior. Created/removed by detect.sh (but not updated), created/removed(?)/updated by build (if run). b) 'build_not_needed' (?): created/updated/removed by detect.sh c) 'last_build' (?): created/updated by build.sh
If b) exists after detection, build doesn't need to run. If c) is newer than build.sh, build doesn't need to run. Otherwise: build and update c).