Page MenuHomePhabricator

Should be possible to build MITK statically
Closed, WontfixPublic

Event Timeline

New remote branch pushed: bug-16926-StaticMitk

Current release is finished. Resetting target milestone

User neher has pushed new remote branch:

bug-16926-StaticMitkIntegration

User neher has pushed new remote branch:

bug-16926-StaticMitkNew

Which components may, conceptually, be linked statically? Qt,VTK, ITK, boost, the MITK modules, Blueberry (except for the plugins)?

External dependencies which should just work:

  • ITK
  • VTK
  • Boost
  • ann
  • tinyxml
  • gdcm
  • dcmtk
  • Eigen
  • OpenCV

Qt can in principal be linked statically, but you need to carefully read the Qt license implications.

All MITK modules should in principal be buildable statically. Because some MITK applications require functionality from "auto-loaded" (CppMicroServices terminology) modules, these need to be "imported" in the main executable by using special macros. This was ongoing work and should partly be contained in the linked branch.

Thinks which will not work

  • CTK
  • All CTK base MITK plug-ins, hence BlueBerry and the MITK Workbench

@Peter: is this something that is still mergeable? In general I think this is an important feature, especially for MiniApps. Could you give a status update?

kislinsk added a subscriber: kislinsk.
This task was automatically closed because it wasn't updated at least since July 2016 (over 2 years). Please re-open this task if you think that it is still relevant. This most probably means that you will resolve it.