Page MenuHomePhabricator
Create Task
Maniphest T18100

Qwt and Qxt is not optional
Closed, InvalidPublic
Actions

Description

Qwt and Qxt seem to be automatically built when MITK is built with Qt. There seems to be no way to disable Qwt and Qxt although there is no real dependency in the core and most modules (except QtWidgetsExt, diffusion, ToFUI).

Is there a possibility to disable Qwt and Qxt that I have missed? It should be possible to build MITK without these external projects.

Related Objects

Event Timeline

engelm added projects: MITK, Bugzilla.Sep 16 2014, 9:02 AM
zelzer added a subscriber: zelzer.Sep 16 2014, 3:47 PM

Qwt and Qxt have always been mandatory for MITK builds with MITK_USE_QT ON (I am not saying that this is a good thing).

QtWidgetsExt contains a few classes depending on Qwt and Qxt. The module is unfortunately used in a couple of essential plug-ins. I am not sure how we should handle it in the build system if Qxt and Qwt are explicitly disabled... maybe forcing it to on if MITK_USE_BLUEBERRY is ON.

nolden added a subscriber: nolden.Sep 16 2014, 5:07 PM

Proposed solution from the MITK meeting:

  • add two options MITK_USE_Qwt and MITK_USE_Qxt on superbuild level, default ON, marked as advanced
  • they should be passed to the MITK-build but without further error handling, so the workbench build may fail if someone turns them off
• git-user added a subscriber: • git-user.Oct 2 2014, 9:59 AM

User engelm has pushed new remote branch:

bug-18100-make-qwt-and-qxt-optional
engelm added a subscriber: engelm.Oct 27 2015, 11:30 AM

This is no longer an issue

kislinsk changed the task status from Invalid to Spite.Jun 27 2018, 1:33 PM
kislinsk added a project: Bulk Edit.
kislinsk changed the task status from Spite to Invalid.Jun 27 2018, 1:37 PM
kislinsk removed a project: Bulk Edit.
kislinsk mentioned this in T27033: Clean up stale remote branches.Jan 25 2020, 9:01 PM
MITK · MIC · IMSY · DKFZ