Qt Creator 6.0.1 and Qt 6.2.2 running on Windows 7

[hskoglund]

Hi, even though you've downloaded Qt 6.5.1, no Qt Creator is built with it yet (unless you build Qt Creator yourself :-)

For example Qt Creator 10.0.2 is built with Qt 6.4.3:

(QT Creator 11.0 beta is also built with Qt 6.4.3)

The error box you get is because the function evaluateRecursive() is changed from returning a void (in Qt 6.4.3) to returning a bool (in Qt 6.5.1) But even if you patched that you'd get Qt runtime mismatch errors.

You could try a previous version of @dmginc's dlls and a matching Qt Creator, I use his patched version of Qt 6.4.2 (you'll find the link previously in this topic) and Qt Creator 10.0.0:
https://download.qt.io/official_releases/qtcreator/10.0/10.0.0/qt-creator-opensource-windows-x86_64-10.0.0.exe

[crystalidea]

I've made Qt 6.6.0 available for Windows 7 here
https://github.com/crystalidea/qt6windows7

It's qtbase with all source modifications already applied. Approach is based on previous posts here but better: many improvements and most noticably fallbacks to default Qt 6.6.0 behaviour when running on newer Windows.

The only issue I noticed with all Qt Windows7 backports is that scalled UI is somewhat too big for my 125% scalling option in Windows 7. Something should be tweaked with dpi settings probably.

[WRYYYYYYYY]

Hey @hskoglund @dmginc @crystalidea

Hope you're all doing awesome. 🚀 Huge shoutout to you guys who've been working magic with those QT6 DLL patches for Windows 7! You folks are the real MVPs, and you're making a lot of people happy.

I'm not a QT developer, but I wanted to share a thought – a bunch of QT-based apps that used to run like a dream on Windows 7 suddenly hit a brick wall after they upgraded to QT6. These patched DLLs aren't just for Windows 7 devs; they're also a lifeline for end-users who just want to keep using their favorite apps.

I've noticed the list of patched versions is growing, but I'm thinking, why stop there? Windows 7 users are still rocking it, and there's a bunch of QT6 versions that could use some love. Here's what we've got so far:

6.0.0
6.0.1
6.0.2
6.0.3
6.0.4
6.1.0
6.1.1
6.1.2
6.1.3
6.2.0
6.2.1
6.2.2 hskoglund
6.2.3
6.2.4
6.3.0 dmginc
6.3.1 dmginc
6.3.2
6.4.0 dmginc
6.4.1
6.4.2
6.4.3
6.5.0
6.5.1 dmginc
6.5.2
6.5.3 crystalidea
6.6.0 crystalidea

I believe that extending this compatibility to cover the remaining versions of QT6 would be immensely beneficial for the Windows 7 user base. But I get that this isn't a walk in the park, so maybe we can chip away at it bit by bit. No rush, just a gradual, awesome expansion of compatibility. What do you guys think?

Cheers to keeping the Windows 7 flame alive! 🔥

WRYYYYYYYY

[Linkh]

@WRYYYYYYYY
Hi
I cannot find 6.5.3 by crystalidea actually :/ was the post updated to 6.6.0?

[crystalidea]

Here are 6.5.3 binaries:
https://github.com/crystalidea/qt6windows7/releases/tag/6.5.3-win7

6.6.0 binaries:
https://github.com/crystalidea/qt6windows7/releases/tag/v6.6.0

[Bojo5150]

@crystalidea @dmginc @hskoglund

Folks, I've stumbled onto this thread while searching alternatives to my problem and having read through all of the posts I'm really really hoping one of you can help!

Long story short is I built an Arcade machine years back which is based on Win 7 x64. Its been highly modified / customized over the years and upgrading windows would be devastating and requires massive rework. Recently one application I use to run some games changed to use Qt 6.6.1 x64. vs Qt5. I downloaded and tried the 6.6.1 files linked herein but came across another error and I was wondering if some kind soul could add the missing libraries. I've attached 3 pictures, 1) the Qt files found in the game.exe folder, & 2) the error I'm currently receiving. Its worth noting that some files are different from the 6.6.1 download here and the Qt6 files found in the game.exe's directory.

Would any of you be willing to help me out? Many many thanks in advance!!

[WRYYYYYYYY]

Running QT6 applications on Windows 7 is now a walk in the park, thanks to the recent release of https://github.com/vxiiduu/VxKex/

[5taras]

@dmginc Do these libraries work on Windows 8.1?

[5taras]

@crystalidea Does it work on Windows 8.1?

[hskoglund]

Hi, they should work on Windows 8.1, Windows 10 and Windows 11.

[5taras]

@hskoglund Sorry for asking, do you know how to compile own Qt6svg.dll in Windows 8.1?

[hskoglund]

If Qt6svg.dll is not dependent on any Windows 10/11 features, then you should be able to compile it, say like this:

1. Install a vanilla Qt 6.7.3 on your Windows 8.1 (should be possible)
2. Download a patched Qt 6.7.3 from https://github.com/crystalidea/qt6windows7
3. Replace the vanilla 6.7.3 files with the patched ones from @crystalidea's github
4. Try building Qt6svg :-)

[5taras]

This post is deleted!

[crystalbit]

Qt 6.8.0 is also back-ported to Windows 7/8
https://github.com/crystalidea/qt6windows7

[5taras]

@crystalbit Sorry for asking. I am trying to compile qt dll myself on Windows 8.1.
I have to use Visual Studio Build Tools 2022 17.6 instead of Visual Studio Community Edition 2022 since it's not available anymore on microsoft.com. I had to change PATH in compile_win.bat as vcvarsall.bat is in different folder. I get errors: mv, rm, perl is not an internal or external command.
I have Strawberry Perl installed.

[hskoglund]

At least for me it's available at the usual address: https://visualstudio.microsoft.com/vs/community/

[5taras]

@hskoglund Latest one is incompatible with Windows 7, 8, 8.1.

[hskoglund]

Indeed. previous versions of Visual Studio 2022 worked on Windows 7, you got a warning when you installed but you could proceed anyway, but now you get an error instead :-(
You can still download Visual Studio 2019 Community Edition from here: https://aka.ms/vs/16/release/vs_community.exe

[5taras]

@5taras If I understand correctly I need gnuwin32 package to run mv, rm commands from compile_win.bat which is missing in qt-build-tools folder from github. In script I see "SET PATH %ROOT%\gnuwin32\bin;"

[5taras]

@hskoglund In any case I'd have to correct compile_win.bat as it is oriented for 2022 VS.