KitwareMedical / KitwareMedical/SlicerCustomAppTemplate
Configuring `Slicer_DEFAULT_HOME_MODULE` with "DICOM" fails to bring up Dicom module on startup
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 71
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
when implementing set(Slicer_DEFAULT_HOME_MODULE "DICOM") in the toplevel CMAKE file the application fails to enter the DICOM module on startup, conversely if the module is set in DefaultSettings.ini the module correctly comes up.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare how set(Slicer_DEFAULT_HOME_MODULE "DICOM") in the top-level CMAKE file is propagated with the working setting in DefaultSettings.ini. Reproduce the startup behavior and trace the configuration path; done means the custom application opens the DICOM module when the CMake setting is used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100