Quote:
Originally Posted by KevinH
1. bad or incomplete openssl libraries installed by some apps that results in crashes and failures to start. Solution, find and remove these incomplete openssl dlls as they should never have been installed by any program. Sigil does not actually use openssl but Qt5.4 will try to load and use it if it finds it.
There is a thread here about all of this here: (please read it to the end to see if it applies in your case)
https://www.mobileread.com/forums/sho...d.php?t=250921 |
Sometimes, these openssl libraries aren't even bad or incomplete, but rather just an older version of the libraries that can't be utilized by Qt5 because of compiler runtime incompatibilities. These included libraries/runtimes only really become a problem (on Windows) when the directory
containing those libraries gets added to the system path.
That's where some Windows developers need to be waaaay more careful when distributing these libraries if their program's directory needs to be added to the path.
Case in point:
- calibre adds it's program directory to the system path
- calibre includes many libraries (including openssl and a c++ runtime and freetype and expat and others)
but ... Kovid has also wisely and conscientiously tucked those libraries away in subdirectories that are NOT included on the system path. The only files in the directory that calibre adds to the path are exes (most of them calibre-specific) that no other program is going to go searching the system path for anyway.
My apologies for the lengthy sidetrack.
