simexpal uses cache files such as checkedout.simexpal and regenerated.simexpal at the level of each build folder (e.g. develop/benchmark for a build benchmark).
Having these cache files changes the resource (the build). The goal of this issue is to collectively store all cache information at root level of the simexpal project.
First, we should clarify why exactly cache files are written to the build director? Second, change that behaviour and store all caching information on root level. This could be done using a .yml or .json file (see status.cache and validation.cache at root level).
simexpal uses cache files such as
checkedout.simexpalandregenerated.simexpalat the level of each build folder (e.g.develop/benchmarkfor a buildbenchmark).Having these cache files changes the resource (the build). The goal of this issue is to collectively store all cache information at root level of the simexpal project.
First, we should clarify why exactly cache files are written to the build director? Second, change that behaviour and store all caching information on root level. This could be done using a
.ymlor.jsonfile (seestatus.cacheandvalidation.cacheat root level).