MattTroke
July 10, 2019, 12:12pm
1
Can you explain how Slicer_QTLOADABLEMODULES_ENABLED/Slicer_QTLOADABLEMODULES_DISABLED works? If the Slicer_QTLOADABLEMODULES_ENABLED list is empty, does it enable all modules excepting those in Slicer_QTLOADABLEMODULES_DISABLED? And if one or more modules are listed in Slicer_QTLOADABLEMODULES_ENABLED are all others disabled by default?
jcfr
July 10, 2019, 12:39pm
2
Reading the documentation associated with the SlicerCheckModuleEnabled module should help.
#
# This CMake module provides functions allowing to check if a given Slicer built-in module
# should be enabled or disabled.
#
# Definitions:
#
# * A Slicer built-in module is a module whose source code is found under one of the
# "Slilcer/Modules/*" subdirectories. These do not include Slicer remote modules or
# modules associated with bundled extensions.
#
# * Enabling (or disabling) a module means that it will (or will not) be built.
#
# * Building a module means that the corresponding directory is added using the add_subdirectory
# CMake command and that the associated CMakeLists.txt is processed.
#
# By default, all built-in Slicer modules are assumed to be enabled. Then, based on Slicer
# build options, built-in module may be disabled.
#
# Setting any of these variables allows to explicitly disable modules of the
# corresponding module type ignoring effect of Slicer build options:
show original