Can you explain the CMake variables Slicer_<moduleType>MODULES_DISABLED|ENABLED?

jcfr · July 10, 2019, 12:39pm

Reading the documentation associated with the SlicerCheckModuleEnabled module should help.

Slicer/Slicer/blob/3e0ea48e078f2f0b9d501e2ada70d292e96d1de4/CMake/SlicerCheckModuleEnabled.cmake#L21-L62


#
# 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:

This file has been truncated. show original

Topic		Replies	Views
Simplify Slicer or Remove some modules from Slicer Support	3	2287	July 15, 2019
SlicerCustomAppTemplate build fails on Loadable Module Development bug	1	326	August 27, 2022
Loadable module questions: `setBuiltIn()` and set module active Development	2	232	August 16, 2021
Modify Slicer_DEFAULT_HOME_MODULE and Slicer_DEFAULT_FAVORITE_MODULES Development	4	270	September 16, 2022
Detecting and loading Loadable modules Development	7	720	February 7, 2019

Can you explain the CMake variables Slicer_<moduleType>MODULES_DISABLED|ENABLED?

Related topics