Page MenuHomePhabricator

Modules selection should be configurable directly
Closed, ResolvedPublic


the MitkRegistration module is built, also if no bundle or dependent module seems to require it.

  • Sample setup at my workstation mint01:
  • no blueberry
  • no bundles
  • no other naming of the bundle name in any CMakeLists.txt

Event Timeline

This is a design "feature" of the module system. The application configuration is determined by the bundle selection. For non-BlueBerry applications the application should take care of a mechanism to select which modules are required, e.g. by super build configuration.

I will still leave this open since it will be a feature of the next build system rework.

Discussed with Daniel and Sascha today. I will extend the CREATE_MODULE macro in a way that it checks an optional CMake variable that contains a positive list of modules to include in the MITK build.

[e1a340]: Merge branch 'bug-5524-explicit-modules-selection'

Merged commits:

2011-06-20 14:42:46 Marco Nolden [688f17]
Remove DCMTK 3.5.4 messages

Not strictly related to this branch ...

2011-06-20 13:58:03 Marco Nolden [d56d46]
Allow explicit specification of MITK Modules to build

Use the MITK_MODULES_TO_BUILD internal variable on superbuild level