#1173: ExternalLibraries build environment problems ------------------------------------+--------------------------------------- Reporter: hinder | Owner: Type: defect | Status: reviewed_ok Priority: major | Milestone: ET_2013_05 Component: EinsteinToolkit thorn | Version: Resolution: | Keywords: zlib hwloc ------------------------------------+---------------------------------------
Comment (by hinder):
Replying to [comment:13 eschnett]:
The meaning of NO_BUILD is that the configure.sh script should (a) not
search for the library (since MPI_DIR is not empty), and (b) it should not be built either. Presumably, the system knows how to find/use MPI in some other way. The variables MPI_INC_DIRS should be left empty in this case.
Would it be possible to have MPI_DIR = NO_BUILD and *still* use the MPI_INC_DIRS options? What should I set MPI_DIR to if there is no single MPI directory which makes sense, and all the other options are necessary and sufficient to build with MPI? I think it makes sense to set MPI_DIR = NO_BUILD in that case; it is certainly intuitive. Is there a place where we document the behaviour of the ExternalLibraries thorns, along the lines of comment:13? We started a page (https://docs.einsteintoolkit.org/et- docs/Improving_the_treatment_of_external_libraries) on the wiki where we tried to rationalise the whole system, but it is meant to be suggestive of a new way of doing things, rather than a documentation of the current system.