MADNESS executables (both unit test and ad hoc tests, examples, and applications) are created with CMake property EXCLUDE_FROM_ALL set. This prevents their building by default (which is typically desired when MADNESS is built as a subproject), but this breaks the install target from working unless other targets building these executables have been built.
effectively, MADNESS installation only works "correctly" when it's configured with MADNESS_BUILD_MADWORLD_ONLY=ON. This is not sufficient when other MADNESS libraries are used but MADNESS is used as a subproject, e.g. in MPQC.
Need to support building of all libraries only (without non-unit-test executables) with functional install target. Also need to be able to test that the install target works.
evaleev
commented
1 year ago
MADNESS executables (both unit test and ad hoc tests, examples, and applications) are created with CMake property
EXCLUDE_FROM_ALLset. This prevents their building by default (which is typically desired when MADNESS is built as a subproject), but this breaks theinstalltarget from working unless other targets building these executables have been built.effectively, MADNESS installation only works "correctly" when it's configured with
MADNESS_BUILD_MADWORLD_ONLY=ON. This is not sufficient when other MADNESS libraries are used but MADNESS is used as a subproject, e.g. in MPQC.Need to support building of all libraries only (without non-unit-test executables) with functional
installtarget. Also need to be able to test that theinstalltarget works.