Hi,
are you using the MITK provided CMake macros for creating applications?
E.g. mitkFunctionCreateBlueBerryApplication for a BlueBerry based
application or similar.
The macros take care of dependencies and additional plug-ins etc.
Best,
Sascha
On 05/17/2018 09:40 AM, Paolo Cabras wrote:
>
>
Hi Sas,
are you looking for a line like this one?
https://github.com/MITK/MITK/blob/v2016.11/Plugins/org.mitk.gui.qt.ext/src/QmitkOpenDicomEditorAction.cpp#L109
Best,
Stefan
-Original Message-
From: regtol...@tut.by [mailto:regtol...@tut.by]
Sent: Mittwoch, 16. Mai 2018 17:11
To:
Hm, it’s hard to say what’s going wrong with a custom application. All I can
say is that the installers work for us with the MitkWorkbench and our
applications. We use the common CMake functionality for packaing. Special rules
are in mitkInstallRules.cmake. One thing that’s a bit different in
I am sorry... I don't know why I took the last version (it was written
to take 2.x).
Now the packaging is done but it seems incomplete : in
_CPack_Packages/win64/NSIS/my_project-0.1.1-win64, only the Microsoft
Visual C++ Redistributable Package (added setting
CPACK_VISUAL_STUDIO_PRODUCT_NAME
Hi Sas,
some of our plugins are not activated by the default build configuration.
However you can activate plugins in CMake. Let's say your binaries from the
Mitk-build are in /somewhere/bin
Then you have to change the binaries folder level in CMake to
/somewhere/bin/MITK-build
Now you
