no SSL support on Windows just for few users...

SGaist

MSVCR100.dll means that you need to check whether the computer having issue are missing that version of the Microsoft runtime libraries. One other way is to make them part of your application release.

mbruel

@Bob64 said in no SSL support on Windows just for few users...:

I have no insight into the specific problem here but, if you don't get anywhere with Dependency Walker, Process Monitor can also be very useful in tracking down reasons for DLL loading issues.

The problem is that I don't have the issue on my environment. Only one user gets the issue on his computer. He tested on another one (his wife) and it's working fine. So it's pretty difficult to debug...

mbruel

hum, he has errors in WS2_32.DLL...
alt text

So I guess nothing I can do within the app...
He must install MSVC2015 redistributable?
are we sure that this is what's missing? why MSVC2015 and not MSVC2017 or more recent?

Edit: that's crap, is there a way to find dlls (maybe compiled with MinGW) that would not need that?
or can I provide all those api-ms-win-core*.dll within my app?

Bob64

@mbruel If possible, get the user to install Process Monitor in the problematic environment and send you the log. Sometimes this allows you to pinpoint what is failing to load, especially if you can cross reference a log from a successful environment. I wouldn't necessarily recommend this unless you really are stuck, as it can be a lot of work, but it has got me out of a hole on a few occasions.

mbruel

@Bob64 said in no SSL support on Windows just for few users...:

get the user to install Process Monitor in the problematic environment and send you the log

I don't know how to use Process Monitor, on my win7 VM (I'm on Debian), it's failing to open due to lack of drivers.

My user tried to install msvc2015 redistributable, it didn't make the SSL work.
He tried to copy the msvcr100.dll I provided him. and now it is working.

How come libssl v1.1.1 (from 2019) could still depend on msvc 2010? oO
Is there a way to build openssl to not have those msvc dependencies?

SGaist

Why 2010 ? Backward compatibility with really old systems I would guess.

mbruel

@SGaist yeah but then not compatible with newest versions out of the box... :\

mbruel

I suppose Qt MinGW version is built agains this libssl version requiring msvc 2010 right?
So even if I wanted, I couldn't compile it myself (libssl) without msvc and providing it.
Is it right?

stephane78 0

@mbruel Hi ,if you use mingw or mingw-w64 you can compile openssl with it from the sources, and then compile Qt from the sources, with the support of openssl (option in configure of Qt)

Mozi

Hi! @mbruel .

Please try lucasg/Dependencies. It's A rewrite of the old legacy software "depends.exe" in C# for Windows devs to troubleshoot dll load dependencies issues. This tool can resolve dependencies with the dlls from Windows API Sets.

By the way, there are still some bugs in the latest release version (f.e., Dependencies#102). You can checkout the newest build from CI, or wait for the next release.