Debian Packaging

Status

There is an experimental debian package here: http://packages.qa.debian.org/c/ctk.html

The current Debian sources for CTK are here: http://anonscm.debian.org/viewvc/debian-med/trunk/packages/ctk/trunk/debian/

Some experimental changes are published here: https://github.com/nolden/ctk-debian and https://github.com/nolden/CTK/commits/debian-patches

Open Issues and Pull Requests on Github

https://github.com/commontk/CTK/issues/65 https://github.com/commontk/CTK/pull/158

Working configuration

This is a working subset (possibly not complete) of CTK that builds with Debian Unstable on 12/14/2012:

CTK_APP_ctkCommandLineModuleExplorer:BOOL=ON
CTK_APP_ctkDICOM:BOOL=ON
CTK_APP_ctkPluginBrowser:BOOL=ON
CTK_APP_ctkPluginGenerator:BOOL=ON
CTK_BUILD_QTDESIGNER_PLUGINS:BOOL=ON
CTK_ENABLE_DICOM:BOOL=ON
CTK_ENABLE_PluginFramework:BOOL=ON
CTK_ENABLE_Widgets:BOOL=ON
CTK_LIB_CommandLineModules/Backend/FunctionPointer:BOOL=ON
CTK_LIB_CommandLineModules/Backend/LocalProcess:BOOL=ON
CTK_LIB_CommandLineModules/Core:BOOL=ON
CTK_LIB_CommandLineModules/Frontend/QtGui:BOOL=ON
CTK_LIB_CommandLineModules/Frontend/QtWebKit:BOOL=ON
CTK_LIB_Core:BOOL=ON
CTK_LIB_DICOM/Core:BOOL=ON
CTK_LIB_DICOM/Widgets:BOOL=ON
CTK_LIB_PluginFramework:BOOL=ON
CTK_LIB_Visualization/VTK/Core:BOOL=ON
CTK_LIB_Visualization/VTK/Widgets:BOOL=ON
CTK_LIB_Widgets:BOOL=ON
CTK_PLUGIN_org.commontk.log:BOOL=ON
CTK_PLUGIN_org.commontk.plugingenerator.core:BOOL=ON
CTK_PLUGIN_org.commontk.plugingenerator.ui:BOOL=ON

Of course you shuld set

CTK_SUPERBUILD:BOOL=OFF

Proposed package structure

/usr/lib/:
  # CTK libraries
  libCTKCore.so
  libCTKDICOM.so
  ...
/usr/lib/ctk-plugins/:
  # CTK plugin framework plugins
  liborg_commontk_eventadmin.so
  liborg_commontk_dah_core.so
  ...
/usr/lib/x86_64-linux-gnu/qt4/plugins/designer/:
  # Qt designer plugins
  libCTKWidgetsPlugins.so
  libCTKDICOMWidgetsPlugins.so
/usr/include/ctk/:
  # all public library headers
  ctkUtils.h
  ctkComboBox.h
  ctkDICOMDatabase.h
  ...
/usr/include/ctk/org.commontk.dah.core/: 
  # public plugin headers
  ctkDicomAppInterface.h
  ...
/usr/bin:
  # executables (separate package "ctk" or "ctk-utils"?)
  ctkDICOM
  ctkCommandLineModuleExplorer
  

Open issues

• CTK side
  • installation of CMake files: make CTKConfig.cmake and UseCTK.cmake relocatable (after some cleanup)
  • make DGraph work for external projects without a CTK source tree
  • test whether CTK CMake macros work with an installation tree depicted above
  • install support for Qt plugins and CTK plugins
• Debian side
  • do we want to create separate packages for the various topics? (libctk-core, libctk-dicom, libctk-cli, ... )
  • currently the installation paths are changed in the debian/rules files, e.g. removing the "ctk-0.1" part of the path. Is that ok or should we try to solve this as well upstream?

Dependencies with potential problems

DCMTK

CTK is using a recent snapshot in the superbuild, but Debian includes the latest stable release 3.6.0 . Since the Bologna Hackfest in December 2012 CTK builds (again) with DCMTK 3.6.0, using one backported class that is included conditionally (scu.cc)

Log4Qt

Log4Qt is in general not used by CTK anymore. There is one plugin left using it but this is more of a technical study and can be turned of:

CTK_PLUGIN_org.commontk.log4qt:BOOL=OFF

PythonQt

Several patches have been submitted to upstream, some are left, a summary can be found here. If this is resolved more features of CTK can be enabled for the Debian package.

Update 11/05/2013: one header is missing: ctkAbstractPythonManager.cpp:31:33: fatal error: PythonQt_QtBindings.h .

VTK

CTK Visualization Core compiles with VTK 5.8, just missing one small functionality.

QtSoap

There is a debian package called libqtsolutions-soap-2.7-1, but there is no development package so it's unclear if this can be useful.