Issue with Including Scripted Module in Custom Slicer-Based Application

software
Wed, 18 Jun 2025 14:02:09 +0000
Development

Hi all,

I’ve developed a custom Slicer-based application and included a custom scripted module called HemisphereVolumeCalculator
In my top-level CMakeLists.txt, I’ve added it using:

set(Slicer_EXTENSION_SOURCE_DIRS
  ${Safe_SOURCE_DIR}/Modules/Scripted/HemisphereVolumeCalculator
)

The module runs fine when I add its path through the application settings → Additional Module Paths. However, after building my application from the generated Safe.sln (on Windows), the module does not appear in the application interface by default.

Questions:

1. Is there anything else I need to do beyond setting Slicer_EXTENSION_SOURCE_DIRS to ensure the module gets built and bundled?

2. How can I confirm whether the module was recognized or included during the build?

3. Are there any additional flags (e.g., Slicer_QTSCRIPTEDMODULES_ENABLED) that I need to set manually?

7 posts - 2 participants