DICOM @ OFFIS

This is a (from my perspective) strange way to disable tiff and jpeg. I would have thought you would have to use the CMake variable DCMTK_WITH_TIFF for that, but, as long as it works. Regarding your question: I would expect this to disable reading and writing tiff images, jpeg will most likely still...

It seems that you have a x86_64 version of the tiff and jpeg libraries installed and CMake found and tried to use them although you are building for i386. Possible solutions: 1. Disable the use of libtiff and libjpeg in the DCMTK CMake Cache 2. Point CMake to the i386 version of both libraries (may ...

Or, the more complete answer would probably be to write a systemd unit so that it is e.g. automatically started during boot, restarted in case an error occured etc. See e.g. here: https://wiki.archlinux.org/index.php/systemd#Writing_unit_files (from my experience the Arch Linux Wiki is often very go...

Hi Chris,

we had a problem with the server the wiki is running on. It is currently rebooting and should be back in a few minutes (hopefully).

Best
Jan

By the way, I' ve known v3.6.1 doesn' t support Unicode. That's not correct, alt least some of the DCMTK 3.6.1 versions support conversion between e.g. ISO Latin 1 and UTF-8 etc. IFF you link the correct support libraries (GNU iconv or ICU). It is the same for DCMTK 3.6.2. What is not supported is ...

It prevents an error that could otherwise occur if there was a print job with a file name that is effictively a prefix of the file name of another print job. In that case one of the print jobs could be processed twice while the other one would not be processed at all, leading to an error and a dealo...

Sorry, if adding 'public:' doesnt help I have no idea how to get the compiler to allow access to types defined inside structs/classes outside of them. Perhaps changing struct -> class will trigger different compiler behavior (although that would be idiotic, but the current behavior already is idioti...

I'm really not an expert when it comes to Visual Studio, but, as far as I know the .pdb files contain debugging information, so, the warning most likely means you would have a hard time debugging an error inside the zlib. As I don't expect you would ever need to do that, you can safely ignore the wa...

I fear one needs the fitting support libraries for the compiler, which we did not provide since we don't have the 64 bit version of Visual Studio 2010. Using a newer version of Visual Studio is probably the easiest solution.

To me it looks (at the first glance) like the compiler does not correctly apply the default public access rights to type members of structs, try adding 'public:' in lines 62 and 86 and see if the compliler understands that.

Btw, you saw these, right? Did we miss to create binaries for your specific Compiler/Settings? If so, I might be able to add them (the files are auto generated using a script; I'm also thinking about making the script public but it would need some polishing first).

Don't let him teach you bad practice (new operator), use an std::vector!

The file is generated by CMake while running it before compiling DCMTK. So it seems that our scripts don't understand how multi threading works on Fedora 25 (which seems strange, since it is a rather normal Linux distribution, however, we currently do not test it in our nightly builds - maybe we sho...

I'm not sure I understand your question entirely, but, you can ONLY compress the dataset, not the whole DICOM file. The DcmFileFormat consists of two components: the meta header and the actual file (data set). So I guess that what happens is that you "accidentally" also compress the meta h...