@AlexZhZZ
See QTBUG-120196

@SGaist, the application being developed supports an earlier/lower version of Windows while the IAudioClientDuckingControl requirest at least Windows 10 build 20348 which is a later one. But I have already tested the interface mentioned above and it doesn't have any effect.

Hi and welcome to devnet,

Technically, starting the installer as your user or root is literally two different users. They do not share cache, etc.

However, I currently don't know whether the installer caches anything at all when interrupted and it could be an interesting feature that you can suggest on the bug tracker.

That said, unless you point the installer to a non user accessible folder, it should work just fine and install things in your home directory.

Hi,

I'm the author of QtUsb.
The modular version (0.5) is on beta and not available on ppa (0.4.2) yet. I'll work on that.

Feel free to open issues on github if you find any bugs.

Edit: it should be good for bionic and newer.

@bublee_jessie And what is the problem? On the server side check the client IP which is trying to connect and only accept connection if correct IP and not connected yet.

@SGaist It worked!! 😄😄😄😄 Thanks!!!

So for anyone else who stumbled here, the trick was to get this package from the Qt installer :

And then go in Qt Creator, and use the aforementioned package as a "kit" to compile the project.

@kshegunov I see, now i understand. Thank you for your help and for your patience.

Raised issue https://bugreports.qt.io/browse/QTBUG-49301

Solved from https://forum.qt.io/topic/17139/solved-how-to-use-ssl-support-without-manualy-building-qt-libraries/6

added CONFIG += openssl-linked
copied from the QtSdk the (MingW) libeay32.dll and ssleay32.dll in the same folder as the executable

Well, the plugin name is "simulator"