Hi,
when you switch to v2018.04.2, your application can benefit from the new MITK extension mechanism [1], which is basically able to blend in an external directory into the MITK source tree. This way you can add applications, modules, plugins, and external projects to MITK without touching the MITK source code. The new MITK-ProjectTemplate contains example modules, plugins, and external projects, even though the latter one is a rather simple example (Microsoft Guidelines Support Library). However, it is documented to show you how to add an external project and you can also have a look at the old CMakeExternals/VMTK.cmake to get things up and running again. Best, Stefan [1] https://github.com/MITK/MITK-ProjectTemplate ________________________________ Von: José Alonso Solís Lemus <[email protected]> Gesendet: Dienstag, 2. April 2019 12:33 An: [email protected] Betreff: [mitk-users] VMTK support for MITK v2018 Dear MITK developers, We have an application built over MITK v2016.3. One of our modules uses VMTK, which in v2016.3 was included in the MITK superbuild. We're in the process of updating our app from MITK v2016.03 to v2018, however v2018 does not include VMTK in the superbuild, something our implementation 'assumes', as it is only explicitly called once in the following way: MITK_CREATE_MODULE(MyLib DEPENDS MitkQtWidgetsExt MitkQtWidgets MitkAlgorithmsExt MitkCore PACKAGE_DEPENDS VMTK ITK ) Is there a way to change the above code so that CMake is able to link the external VMTK? What would you advice be the optimal course of action to include VMTK into our app externally? Thanks for the advice! -- - José Alonso Solís Lemus -
_______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
