On 13.10.2011 18:34, Sascha Zelzer wrote: > Hi Thomas, > > The CTK CMake macros handling the building and dependency checking for > the plug-ins have not been tested with multiple directories containing > plug-ins. I assume that is what you have: the MITK Modules/Bundles > directory and your own plug-in directory, all in the same CMake project, > right? > > This line: > > https://github.com/MITK/MITK-ProjectTemplate/blob/master/CMakeLists.txt#L324 > > > tells the CTK macros which plug-ins are "yours" (build in your CMake > project). All plug-ins not matching the regular expressions are > considered "external". Usually, the MITK plug-ins are pulled into > external projects using this: > > https://github.com/MITK/MITK/blob/master/MITKConfig.cmake.in#L134 > > whereas the "plugin-use-file" is generated here: > > https://github.com/MITK/MITK/blob/master/CMakeLists.txt#L556 > > > Using MITK and the CTK plug-ins the way I assume you do is actually not > supported (read: not tested). I am pretty sure you can make it work if > you know what you are doing, but MITK really is designed to be used as a > third-party toolkit using find_package(MITK) with MITK_DIR pointing to a > separate build tree. > > Best, > Sascha > >
Hi Sascha, thanks for the info, this really helped. The problem was that the plugins wren't known at this moment. Using the data in MITKConfig.cmake solved it. Thank you very much & Regards, Thomas ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
