Hi Nil,

switching them on in CMake and regenerating should be enough. If they do not 
appear in VS, please try a clean rebuild. It never happened to me and it could 
be related to some customizations maybe.

It is also worth mentioning the CMake/BuildConfigurations directory. Just have 
a look at the files in there and you get the idea. It's a very easy way to 
completely configure MITK and the only thing you would have to do is to set the 
build configuration in the superbuild (MITK_BUILD_CONFIGURATION, combobox in 
CMake GUI filled with all the configurations found in said directory). Also 
works with the new 2018.04 ProjectTemplate, as long as you follow the same 
directory structure as MITK.

Best,
Stefan

-----Original Message-----
From: Nil Goyette [mailto:[email protected]] 
Sent: Thursday, June 13, 2019 3:06 PM
To: [email protected]
Subject: [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
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users


_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to