Referenced from THIRD-PARTY-NOTICES.txt
V:I:I:Y distributes the Qt 6.11.1 libraries unmodified and links to them
dynamically. The Qt DLLs are installed as separate files next to
VIIY.exe; nothing about them is statically bound into the application.
msvc2022_64)v6.11.1The version is also shown inside the application, in SETUP → About. If the copy you have reports a different Qt version, use the page for that version instead, or write to us — the source must match the binary you were given, not a later release.
The complete corresponding source code for exactly this release, together with all applicable license texts, is published by The Qt Company in its permanent archive:
qt-everywhere-src-6.11.1.tar.xz (a .sha256 checksum
file is published next to it in the same directory).v6.11.1.Because we ship Qt unmodified, the archive above is the corresponding source for the binaries we distribute. We have made no patches to it.
The Licensor hereby offers to any person who received V:I:I:Y, for a period of three years from the date that copy was distributed, to provide the complete corresponding source code of the Qt libraries distributed with it, under the terms of the GNU Lesser General Public License version 3.0, for no more than the cost of physically performing the distribution.
Write to legal@viiy.tech naming your V:I:I:Y version. The offer stands on its own and does not expire if any link on this page moves.
The LGPL gives you the right to modify the Qt libraries and to run V:I:I:Y against your
modified version. Because the libraries are dynamically linked and shipped as ordinary DLLs
in the installation folder, exercising that right needs no special tooling from us: build the
corresponding Qt libraries from the source above with a compatible ABI (same major version,
same compiler and architecture — MSVC 2022, x86-64) and replace the matching
Qt6*.dll files in the V:I:I:Y installation folder, together with any plugins
under plugins/ and QML modules under qml/ that you rebuilt.
Doing so is entirely your prerogative under the LGPL. It is, naturally, not a supported configuration: we cannot diagnose or warrant a V:I:I:Y installation running against libraries we did not build. Nothing in our End User License Agreement is intended to restrict this right, and where the two would conflict, the LGPL controls for the Qt components.
The applicable texts are installed with V:I:I:Y in the licenses folder:
LGPL-3.0.txt, GPL-3.0.txt (incorporated by reference from the
LGPL), Apache-2.0.txt and Qt-license-overview.txt.