crystalidea / qt6windows7 Goto Github PK

cannot load sql driver

The procedure entry point ??1QRhiVulkanInitParams@@qeaa@XZ could not be located in the dynamic link library Qt6Gui.dll

It would be cool to have a version of QT6 that could work on XP. It would actually interest me into trying to port some apps like nheko.

^^Title

I came across this bug a couple of days ago:
https://bugreports.qt.io/browse/QTBUG-127644

Perhaps, it migrated here too:

Is there any way to fix this? Thanks a lot.

Could you explain this please?

Is this simply a case of replacing qt6 files, with these files to make something run on Win 7, or is it more involved than that.

For example, I have a programme, CopyQ version 8 which doesn't run on Win 7. It has various QT6 files.
Can I just replace the original QT6 files, with your QT6 files?

Hope that makes sense.

Thanks

Hi, I saw from the commit history that at some point you were maybe working on a 6.5.3 release but then jumped to 6.6.0. Any chance you could release that still? Its what the new verion of Calibre is using. I use the modified .dlls to keep it running on Windows 8.1. Thanks!

Hi there, great work u are doing, its a unfortionate Qt6 dropped support for windows 7 and make extra work for people that still have to use it for one reason or another

was wondering if its possible to patch QtQuick
to work on Qt 6.6.1 somehow

since some apps sadly use this for their UI design, they won't run without it

Thanks for the great work u are doing

Please support the MinGW compiler.

Do you mind doing same for 6.4.3?

I have a some apps that stuck on using 6.4.3 and i'd love to use the update on my Win 7 box.

Hello,

I created a Qt application compiled with Qt 6.6.0 and MSVC 2019 64-bit. Following the instructions, I replaced the related .dll files with the originals, including qwindows.dll. The application works fine on Windows 10, but on Windows 7, it encounters an issue:

"Entry Point Not Found: The procedure entry point CreateDXGIFactory2 could not be located in the dynamic link library dxgi.dll."

Thank you for any help or suggestions you can provide.

https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.7.0/release-note.md

https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.6.3/release-note.md

Dear crystalidea,

I am interested in using the qt6windows7 library for my personal business project and would like to ensure compliance with the appropriate licensing terms. Could you please clarify the licensing terms under which the qt6windows7 library is distributed? Specifying a license would greatly help in understanding how this library can be legally used and distributed.

Thank you for your work and I look forward to your response.

Best regards

Could you compile 6.5.2.0, please?

Would it help if the error is about missing entry point for CreateDXGIFactory2 in dxgi.dll?

Hello,
Your Qt6 project for Windows 7 is pure gold.

The only issue is that by default Qt6 apps use highly specific export function names, which also end up in the import table of compiled Qt EXE files too.

However, there's for example IDA Pro which cans demangle function names automatically (generating clean function names, without prototype info).

If you could perhaps even create a tool that demangles the names of exported functions in any Qt6 DLL, then we could automatically sanitize the function names of your DLL files.

Then we would also be able to run that tool on a target Qt6 program (e.g. XCA.exe, X-Certificate Authority, an x509 cert management utility), and it would look for imported DLLs names that start with "Qt6" or "qwindows".

If any such imported DLL names are found, then the names of the imported functions would also be sanitized and we would end up with matching DLL exports, without all the compiler-specific prototypes which seem to break direct DLL swapping.

For the rest of the DLL calls, we could use either VxKex or we can redirect all missing DLL files to their appropriate real DLL.

(e.g. almost all the Win10 exclusive "api-ms-win-core-synch-2-1-0.dll" calls are actually already in Win7's kernel32.dll)

Thanks for the Qt6 DLLs nonetheless, it's already a great start.
They just need a way to simplify the exported function names.

References:

XCA: https://github.com/chris2511/xca
VxKex: https://github.com/vxiiduu/VxKex