Quote:
Originally Posted by DiapDealer
Interesting.
When profiling on my system, I saw the same request for those two dlls (they're located in Windows/system32 on my computer), but when I rename those two dlls, profiling with Dependency Walker turns up no request for those dlls and no errors/ warnings about not being able to find them.
I can only assume they're not a make/break dependency on Windows (Linux and OS X come with openssl)... but that Qt will try to hook them if they're available. Perhaps on the systems where Sigil is failing to launch, Qt5 is simply finding incomplete/faulty implementations of OpenSSL (delivered with many, many Windows programs) in the paths it's hardcoded to search for the optional OpenSSL functionality—and bombing as a consequence. That would explain why putting complete/valid versions of those dlls into Sigil's program directory would appear to "fix" the problem. Sigil's program directory is the first place searched by Qt: if it finds complete/valid versions there, it will never look any farther (thus aborting the search before it has a chance to run across any problematic version of OpenSSL present on the system).
It wouldn't be the first time I've run into troublesome, customized versions of OpenSSL interfering with other programs on Windows. Especially when any of those programs which include problematic/specialized versions of OpenSSL gets it's program directory added to the system %PATH%.
It'd be interesting to see the results of one the users (who can't launch Sigil) carefully renaming any and all occurrences of those two OpenSSL dlls found on their systems (or at least seeing which—if any of them—are in program directories that are on the system %PATH%, and temporarily removing it/them).
|
You are right. It turns out the Sigil 0.8.4 can't launch, it is loading the ssleay32.dll shipped with Php5 on my PC. php5 is in the system path on my PC and the ssleay32.dll bundled with it is old version 0.9.8y. If I rename php5 to php5.old, the Sigil runs normally.
So it is recommended to bundle a correct version ssleay32.dll with Sigil too.