Hi Nil, after you have a successfull superbuild of MITK, you can choose your plugins with CMake on the MITK-build level (not the superbuild-level)
For example, let's look at this directory tree: src - .git - ... bin - ep - MITK-build - ... In CMake you want to set the binary path to the MITK-build directory. Then you can set CMake variables for the plugins like MITK_BUILD_org.mitk.gui.measurementtoolbox and more Then do Configure & Generate and build MITK. So you don't need a clean rebuild, you can customize your working MITK build at any time with more or less plugins. Best, Tobias -----Ursprüngliche Nachricht----- Von: Nil Goyette [mailto:nil.goye...@imeka.ca] Gesendet: Donnerstag, 13. Juni 2019 15:06 An: mitk-users@lists.sourceforge.net Betreff: [mitk-users] Not all plugins Hi all, How can I build the plugins I want without using MITK_BUILD_ALL_PLUGINS? Our in-house application requires more plugins, such as "org.blueberry.core.jobs", "org.mitk.core.jobs", "org.mitk.gui.qt.segmentation", etc. I tried setting some to ":ON" in PluginList.cmake and adding some in Workbench/target_libraries.cmake, but visual studio wasn't compiling anything more. Maybe I just need to start from a clean build, but the question is worth asking anyway. Nil Goyette _______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users _______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
