#1086: Cactus REQUIRES should not introduce a build order ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: optional | Milestone: Component: Cactus | Version: Keywords: | ----------------------+----------------------------------------------------- If thorn A requires B, then thorn A needs to be configured after B, and its libraries need to be listed before B. However, there is no reason why A should be built after B.
#1086: Cactus REQUIRES should not introduce a build order -----------------------+---------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: optional | Milestone: Component: Cactus | Version: Resolution: | Keywords: -----------------------+----------------------------------------------------
Comment (by rhaas):
In the case of a thorn providing Fortran module files (eg. the Fortran thorn) then build order needs to be imposed I believe since the module files are only created when the source is compiled not already at configuration time (as is eg. the case for ExternalLibraries).
#1086: Cactus REQUIRES should not introduce a build order -----------------------+---------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: closed Priority: optional | Milestone: Component: Cactus | Version: Resolution: invalid | Keywords: -----------------------+---------------------------------------------------- Changes (by eschnett):
* status: new => closed * resolution: => invalid
trac@lists.einsteintoolkit.org
-
Einstein Toolkit