Cdash Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES OFF Question
Created by: MicheldeMessieres
This question is about the intended behavior of Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES for cdash tests.
Summary:
Is the intention that EXTRA_CONFIGURE_OPTIONS can be used to turn off Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES? I think this is the intention but the current setup seems to override this with a hard coded ON setting in TribitsCTestDriverCore.cmake.
This apparently means we cannot run a manual configuration build with Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES OFF which will behave identically to a cdash test run with Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES OFF.
Details:
TribitsCTestDriverCore.cmake explicitly sets this value to ON: SET(${PROJECT_NAME}_ENABLE_ALL_OPTIONAL_PACKAGES ON)
Then package dependencies are calculated which depend on that value: TRIBITS_ADJUST_AND_PRINT_PACKAGE_DEPENDENCIES()
Then EXTRA_CONFIGURE_OPTIONS are applied. I believe EXTRA_CONFIGURE_OPTIONS is the proper place we would want to turn Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES off but the above sequence means that the dependencies are calculated before reading this value.
An example would be running a cdash test with Zoltan2 and Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES set OFF in EXTRA_CONFIGURE_OPTIONS. This will still result in attempts to build Thyra which would not occur for a manual configuration build. Note this then leads to some build errors for cdash only which I haven't looked into yet but I expect are directly related to this setting.
Amending my own comment here: Simply removing the hard-coded Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES=ON setting probably does not work as expected - I will have to investigate that further.
There are only a few cases of EXTRA_CONFIGURE_OPTIONS using Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES OFF currently in the repo.