Using QT under the LGPL?

Question

Qt

As a matter of fact, there was a question related to the use of QT in proprietary software. As the license says:
GNU LGPL - for developing software with a proprietary license, but without making changes to Qt.
But there is a main limitation - the program itself must consist of a single file, and under the LGPL license, I must use dynamic linking.
And here is the main question: will such a loophole work as: DLL QT is in the program resources, when the program starts, the DLL is extracted to temp and is already used from there. At the same time, the program license mentions that QT is used, distributed under the LGPL?
those. in fact, nothing seems to be broken (dynamic linking + the library itself remains unchanged), but who knows whether it is possible to use the DLL in this way or not.

Answer 1

Vsmysle from one file?

Answer 2

The point of dynamic linking is that the user can, for example, replace a library. So it's better not to pace, but to some application support, and not every time at startup, but only if it's not there yet.
Otherwise, in my opinion, it is quite possible just like that, it turns out as a distribution kit, but you never know who has any distribution features. (I also have the plugin to be one file, and there I have a whole Python, so I pack it into an archive and attach it to the DLL; I deploy it at the first start. True, I don’t have LGPL libraries yet, but I don’t see any obstacles to that. )