Ninth DCMTK snapshot version 3.6.1

Today, a new development snapshot of the DCMTK has been made available. This is the ninth snapshot after the official release of version 3.6.0. Again, a couple of minor issues have been fixed that were detected after the publication of the previous version.

These are the main changes of this snapshot:

  • Added various helper functions for speeding up common tasks to “dcmrt“. This was known as the “medium-level API“.
  • Added support for new Return Key Attributes to the Modality Worklist Management SCP “wlmscpfs“, which are required for the IHE Eye Care Workflow.
  • Further enhanced support for building shared libraries on Windows: Now a single “dcmtk.dll” can be build (if needed).

All details on what has changed can be found in the corresponding CHANGES file. If you are interested in the differences on a source code level, please check the web interface of our public git repository.

This entry was posted in DICOM, English and tagged , , , , , , . Bookmark the permalink.

4 Responses to Ninth DCMTK snapshot version 3.6.1

  1. nkp says:

    I am trying to download the latest version from following location but it gives me error. 425: Failed to establish connection.

    I want to write an application which will be consuming dcmtk library to get data. Could you please guide me how can I go forward and what is needed.

  2. Piet says:

    Hello Jörg,

    I am working with the graphical programming language LabVIEW (G) and the Vision Libraries for Image processing (LabVIEW & Vision are from National Instruments, TX,USA). With LabVIEW its possible to call shared libraries, active x com. .net ond more.

    DCMTK is a very powerful library and I like to use the functions of DCMTK via a shared library (windows dll). You write that … “Now a single “dcmtk.dll” can be build (if needed)” …! I am mainly interested in Dicom File handling with dcmtk.
    Do you have a description “How to make a shared dcmtk.dll”?
    Is it also possible to build only a shared dcmdump.dll (for example)?

    Are the functions, parameters, and datatypes of the shared library</ well described?

    Thanks a lot for your help!
    I´ve made a DICOM course at Offis few years ago. I really liked it!

    Best regards from Goettingen.

  3. Hello Peter,

    first of all, thank you for your kind words on our training courses 🙂

    Regarding your main question, I refer to the INSTALL file that is shipped with the source code package:

    CMake and shared libraries

    The CMake build system allows building shared libraries instead of static libraries. On Windows systems, these are dynamic link libraries (.dll). On Unix systems, these are shared objects (.so). To enable this, set the “BUILD_SHARED_LIB” option to “ON”. Please note that this is currently not supported because it might conflict with the use of external libraries.

    Additionally, it is possible to produce a single shared library for the whole toolkit. This mode is controlled by the “BUILD_SINGLE_SHARED_LIBRARY” option. If you don’t want the whole toolkit in a single shared library, the “DCMTK_MODULES” cache variable can be modified to select a subset of the available modules. Please note that this option is marked as advanced and thus is hidden by default. Also, when building a single shared library, applications and tests cannot be built.

    Further technical questions should be posted/discussed in the public DCMTK forum at

Leave a Reply