DICOM @ OFFIS

You probably need to modify the environment variable LD_LIBRARY_PATH to include your /bin directory. Alternatively/additionaly you probably need to modify the java classpath/library path. It has been some time since I did something similiar using java, so google can probably help you better than I (...

Please note that the tutorial does not really apply for newer versions of OpenSSL (but can still be used to get some ideas).

I plan on writing a tutorial for that, but I have currently no idea when I'll find the time for it. The existing tutorial in our wiki is now completely outdated since we modified the way DCMTK is build for Android in DCMTK 3.6.2. I'll point you to this for starters: https://cmake.org/cmake/help/v3.7...

You perhaps need to reverse the link order of ofstd and oflog.

You probably need to also link against the zlib, i.e. should do the trick.

The relevant option should be as you see it defaults to ON.
You could check whether WITH_THREADS is #defined in the generated dcmtk/config/osconfig.h

You could test to simply remove the "+0" and see whether that gives us any better error output (or just works). DCMTK 3.6.2 uses a newer version of log4cplus than 3.6.0, so this perhaps explains it, still seems strange to me though. EDIT: In case you don't enable multi threading, DCMTK_LOG...

This looks strange, the code seems to add zero to the pointer returned from the new statement, meaning this is a pointer offset operation and no conversion should be necessary. Two explanations come to my mind regarding that: 1. Your compiler does not understand C++, what compiler are you using? (lo...

We have exactly that (continuous integration, implementation details are different) up and running for quite some time now, but did not make it official yet. The last step I did was to automate creation of the support libraries for win32 and win64 ;-). Maybe we can merge our approaches, but I'm quit...

That's for you to answer. One can see in that output that dcmtk links the following libraries in the following order: ../../lib/libdcmnet.a ../../lib/libdcmdata.a ../../lib/liboflog.a ../../lib/libofstd.a ../../lib/libdcmtls.a ../../lib/libdcmnet.a -lwrap ../../lib/libdcmdata.a ../../lib/liboflog.a ...

Perhaps have a look at how dcmtk links one of its own applications, e.g. storescu. If you are using CMake, after building DCMTK go to dcmnet/apps and execute 'make clean'. Then run 'make VERBOSE=1 storescu'. You should be able to see the exact command lines how storescu is compiled and linked.

J. Riesmeier wrote:Jan, you mean this commit? Seemed to be an issue for CMake configurations only, right? Autoconf should always have worked since this was tested for the previous releases of the DCMTK.

I don't think Autoconf ever worked for MinGW...

It seems that you configured DCMTK to use the ICU library for character set conversions. That means you will also have to link the ICU library to your application.

zack wrote:When comes the new release? June is already over.

Soon. We are currently performing last minute fixes and checks.

It seems to me that your DCMTK falsely uses ':' as the path separator although it should be ';' on Windows. Are you perhaps using MinGW? It was like this for MinGW until I recently fixed it.