Quote:
Originally Posted by waterqds
So it is recommended to bundle a correct version ssleay32.dll with Sigil too.
|
Actually, a better recommendation would be for application developers to not include crippled or highly altered versions of OpenSSL components with their packages--especially when their program's directory needs to be included in the PATH for it to function.
Another recommendation would be for Sigil to custom compile a version of Qt5 with openssl support turned off (PeterT beat me!).
As I don't see either of those happening in the near future, I'd say the best recommendation is a note describing how to work around the relatively rare situation, if one should find themselves afflicted by it.
I just don't see why Sigil should have to bundle dlls that it doesn't actually require to function.