![]() ![]()
Did you have to do anything to get around the Python 3.10 incompatibility issue?ĮDIT2: Partial success! If I get a version of api-ms-win-core-path-l1-1-0.dll from here - and copy it to Calibre\app\bin, then Calibre will indeed launch. (Was that the ONLY file that needs VxKex enabled?) Again, nothing happens when I try to launch the app. I replaced the Qt files with the latest patched Qt 6.3.1 files from then enabled VxKex for Calibre\calibre.exe and set it for Win 10 compatability. Autopatcher for windows 7 64 how to#Are you talking about running the portable version of Calibre (I hope)?ĮDIT: I THINK I figured out how to install VxKex v0.0.0.2. At least it starts for - Please forgive my ignorance, but can you explain in detail, or point me to some detailed instructions, of how exactly to run Calibre using that project? And please be clear. Thanks in advance for any help you might be able to said in Qt Creator 6.0.1 and Qt 6.2.2 running on Windows and the QT6 files from the link above (great work btw) and then run Calibre using this: in Win10 compatibility for calibre.exe It should work now just fine. I am hoping that some kind soul can either provide a set of patched Qt 6.3.1 files and/or provide a set of Qt 6.3.0 original files necessary to "downgrade" my portable application to use Qt 6.3.0, or suggest another solution to my problem. I am assuming that is because the portable application was built using Qt 6.3.1, and the latest patched files are for Qt 6.3.0? When I saw this thread with a simple set of 3 patched files, I thought this was great, but unfortunately, when I replace the 3 files in my portable application, nothing at all visibly happens when I try to launch the app. Applications which have been built using Qt 5.x still work perfectly fine, but ones built with Qt 6 do not. I often use portable applications which have been built using Qt, such as Calibre. I've not developed Qt applications (yet :) ), but am just a user and am still primarily using Windows 7 (don't judge or comment, I understand the arguments of why I shouldn't). I realize that this topic is a bit old, but I'm hoping that either or is still around. REM Keeps the command line open when this script is run. REM Set Windows version macros to Windows 7 Autopatcher for windows 7 64 code#REM Edit this location to point to the source code of Qt REM Set up Microsoft Visual Studio 2019, where is amd64, x86, etc.ĬALL "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64 Purely for experimental/"at your own risk" use of course :)ĭownload for DLLs (also contains diff file showing the modifications needed to the original source files): ĮDIT: Here is the batch file I used to setup my environment for building: off With some initial guidance from (thanks!), I have managed to create Windows 7-compatible DLLs for Qt 6.3.0 (QtCore, QtGui, qwindows). Autopatcher for windows 7 64 windows 10#They are a bit rough around the edges so only use them on a Windows 7 PC, on a Windows 10 PC use the real stuff. Autopatcher for windows 7 64 zip#So the Xmas gift is a zip with the 3 patched dlls if you're feeling adventurous. ![]() However since I only work with widgets this problem has low priority.) That plugin dll also needs some patching for Windows7. (I also tested a qtquick program but got the error "Cannot load library C:\Qt\6.2.2\msvc2019_64\qml\QtQuick\qtquickplugin.dll: file not found" Then if you replace Qt6Core.dll, Qt6Gui.dll and qwindows.dll in C:\Qt\6.2.2\msvc2019_64 compiling and building widgets based programs seems to work fine. So I installed MSVC 2019 64-bit 6.2.2 on my Windows 7, late in the installation process it stops with a qmake error (because qmake runs on an unpatched qt6core.dll) but if you click Ignore 2 times it will install anyway. Next step was to be able to build and run Qt 6.2.2 apps on Windows 7. When I replaced both Qt Creator's dlls in C:\Qt\Tools\QtCreator\bin and the qwindows.dll in C:\Qt\Tools\QtCreator\bin\plugins.\platforms, voila! It started just fine: Some hacking/backporting later I had new versions of them. ![]() Turns on there are 3 showstoppers: qt6core.dll, qt6gui.dll and the platforms plugin qwindows.dll. Today I spent some time debugging how much trouble it would be to make Qt 6.2.2 run on Windows 7. Why cannot Qt Creator issue the same kind of warning and install anyway, instead of exiting with an 0xC0000005 error? Because it is based on Qt 6.2.2 which by design will not run on Windows 7 :-( You can still install it but." Anyway it seems to work nicely on my Windows 7 PC. Recently I installed Microsoft's new Visual Studio 2022 on my Windows 7 PC, when you install it you get a warning "We haven't designed this version of Visual Studio to work with this operating system. Hi, Christmas is soon upon us, I thought I should bring a gift to those poor souls (like me) that are stuck/prefer working with Qt on Windows 7 instead of 10 or 11. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |