DICOM @ OFFIS

OFBitmanipTemplate still exists, see ofstd/include/dcmtk/ofstd/ofbmanip.h.
There never was DIMSE_DATASET_NONE, as far as I know. It is called DIMSE_DATASET_NULL and still exists.

The INSTALL file does not document library dependencies at all. If you port from a library version published in 2005 to one published in 2023, it should not be too surprising that some things have changed since then

We have removed some compatibility code for ancient C++ compilers that did not support the C++98 standard. This has standard now been available for 25 years, so it is probably safe to exclude compilers that do not support <cctype> and require <ctype.h> instead.

In this case I completely misunderstood your initial post, sorry. In order to convert DICOM images to JPEG 2000 files, you should use class DicomImage, which also allows you to perform those pre-processing steps that DICOM requires but that are not possible in JPEG 2000. Look at the implementation o...

We use a CMake script that modifies the makefile after OpenSSL's Perl configure script has generated it. Here are the relevant parts: file(READ "makefile" MAKEFILE) if(DEBUG) string(REGEX REPLACE "lib(crypto|ssl)([^ \n\t\r]*\\.)(dll|lib|def|pdb)" "dcmtk\\1_d\\2\\3" MAKE...

We are actually talking about JPEG 2000 decoding here, which is good, because per-frame encoding is not supported in DCMTK, while per-frame decoding is. Loading the file with DcmFileFormat::loadFile() is a "lazy" operation that will leave the compressed pixel data in the file until it is a...

When building the OpenSSL library, the library files will be named "libcrypto" and "libssl". We rename these in
our support library build to avoid the situation where a different application installs these DLLs in an
incompatible version and our binaries then load the wrong DLL.

I cannot say what "nmake install" will do. We never use that, but manually copy the files needed by DCMTK into the directory structure that you find in our pre-compiled libraries (actually, nowadays there is a build script for that, but I used to do it manually for years. It's not that dif...

The header and library files should be sufficient for DCMTK's configure tests. Make sure to create a new build directory since DCMTK will not notice that some header files have changed and some configure tests now may have different outcome. This has been tested and works with DCMTK 3.6.8 and OpenSS...

To my knowlege, setting set(CMAKE_SUPPRESS_REGENERATION true) should suppress the generation of the ZERO_CHECK target, which might be preferrable over manually tinkering with the list of build targets in the solution file.

Yes. If you select a Visual Studio version as a generator, the dialog will display a selection list named "optional platform for generator". There you can select Win32, x64, and some ARM varieties.

Thank you for pointing this out. I just updated the page to show the versions of Visual Studio supported in the current version (2015 to 2022).

In essence, it's cmake [options] -S <path-to-source> -B <path-to-build>. <path-to-source> should be the directory into which the developed has cloned the Git repository, <path-to-build> the directory into which the Visual Studio files will be written.

Can we use CMake during an automated build process? Yes, definitely. We do this in our automated nightly builds. If you run cmake.exe with the required command line options (selecting compiler, build options, source directory etc.), the tool will display no GUI. It will just generate the Visual Stu...

We don't provide pre-built DCMTK libraries for Visual Studio. Compiling that by yourself should be easy enough.