Bug #879
closed
DLLs are ABI incompatible when compiled with / without OpenSSL
Added by Jan Schlamelcher over 6 years ago.
Updated over 4 years ago.
Assignee:
Jan Schlamelcher
Description
The resulting dcmtls.dll (and potentially others) are ABI incompatible between two compiled versions of DCMTK when one was translated with- and the other one without OpenSSL. This leads to strange application behavior when mixing files from different builds: not only crashes but also ignoring some command line arguments and 'acting wired', making the issue not that easy to diagnose.
- Status changed from New to Closed
- Assignee set to Jan Schlamelcher
This issue was fixed with the release of DCMTK 3.6.5. Starting with this release, the Windows DLLs that have different ABIs with/without OpenSSL, are shipped in two versions, named "dcmnet.dll" and "dcmnet-openssl.dll", respectively. The affected libraries (as of DCMTK 3.6.5) are:
- dcmnet
- dcmtls
- dcmpstat
- dcmdsig
- % Done changed from 0 to 100
- Status changed from Closed to Reopened
- Priority changed from High to Normal
- % Done changed from 100 to 80
Sadly, so far the fix is only a patch that is applied automatically as part of our release process. We still need to incorporate that patch into the public DCMTK so that other people outside our team can use it, which is why I did not close this issue yet.
- Target version set to 3.6.6
- Target version changed from 3.6.6 to 3.6.7
- Status changed from Reopened to Closed
- % Done changed from 80 to 100
Closed by commit #a1615b246fe5837 and documented in commit #56a75cde9af405.
Also available in: Atom
PDF
Updated by 
Updated by Jan Schlamelcher 
Updated by