Installation and Deployment

@SGaist hi I didn't open it with the Administrator user for Windows, and when I opened it with that user, I downloaded it successfully

Have a look at https://doc.qt.io/qt-5/qtwebengine-webenginewidgets-html2pdf-example.html it uses neither QDocument nor QPdfPrinter

@rey1996 Unfortunately, I am still struggling with the same issue. I've tried using QT_EXCLUDE_FROM_TRANSLATION to no avail. However, I stumbled on the following bug report: https://bugreports.qt.io/browse/QTBUG-126040 It seems we are not the only one :)

@SGaist It's resolved ! Finally ! Disabling my antivirus, firewall, and clearing the cache fixed the issue. Thanks for the help! Now I have other problems with WebEngine, haha. (Check this topic: https://forum.qt.io/topic/161756/issues-with-qwebengineview-and-chromium-integration-errors-and-crashes-in-debug-mode)

Hello, do you still need help now? You seem to be using Windows. Maybe setting architecture environment will solve it? Search for vcvarsall.bat and use it to initialize environment, before running anything: path/to/vcvarsall.bat x64 You also need to do this when building qtbase (if you build it from source). Though you have not encountered it yet, make sure your installed clang's architecture matches too. Otherwise, you may encounter lots of strange linker errors like "unresolved symbol __imp_xxxxx". You can change x64 to some other architecture, but make sure the architecture is consistent. Similar answer

I have the same issues about two days now, I had clean the registry, also all qt settings on other locations that isn't the drive c qt installation, uninstall qt, I did this many times and I also have a working qt install on another computer which I exchange the install qt folder and in my problem computer it won't work and the qt installation folder works on another computer, system oaths is the same, so I came down to operating system issues, I use dependency walker to see what uic.exe requires and in my computer about 4 ot 5 dll it calls and the other computer It call a number of windows kit dll, installing the kit disnt help, I am currently running windows repairs well I will update you guys of my findings

@Nguyen-Thang-Phong This page contains instructions for installing the dependencies. Regards

Hi @SlySven, perhaps the issue has been resolved already? I just did a complete run of 146 builds, and they all passed correctly. You can see the builds here. That said, on Ubuntu (only) I don't rely on install-qt-action to install Python, so perhaps that gets around the issue you mentioned? eg, I do this for Ubuntu runners (not macOs nor Windows): - uses: actions/setup-python@v5 with: python-version: '>=3.9' - uses: jurplel/install-qt-action@v4 with: ... setup-python: false Cheers.

Hi @qtSucks, So why does it say it has found the package, then state wayland_found is set to false? It doesn't say it has found the package, it says it has found the Find Module. They way CMake find_package works is like so: when you request a package, CMake looks for a Find Module. once found, CMake executes the Find Module to locate the actual package. the Find Module sets variables (eg Wayland_FOUND) to indicate if Find Module found the package you're looking for (and where the libs are, etc). So here: find_package considered the following paths for FindWayland.cmake: ... The file was found at ... CMake is telling that the it found a Find Module at that location. CMake then should have evaluated the module, and that module reported that it can't find one or more of the libs you requested (ie set Wayland_FOUND to false). It might help if you show the output that came after your snippet above. Cheers.

Hi, just a guess but try to reset the Scale to 100% (in Settings, System, Display)

I would guess Qt6.x compiles fine with 32bits but it's not tested in the CI so officially unsupported.

@Steve-ONeill Shouldn't you install Qt on the new laptop anyway? Or how are you "transferring"?

@Noobish If you want to be clean: target_link_libraries(fooserver Qt${QT_VERSION_MAJOR}::Core Qt${QT_VERSION_MAJOR}::Network)

@Nguyen-Thang-Phong make sure to call perl init-repository in QT main repo. Make sure everywhere are similar branches. for QT i build like this in D:\qt\qt_test_s\qt5\qt5-build i create script and run it for STATIC QT (to make dynamic build you need to remove flag -static from configure call. call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x86 10.0.17763.0 SET _ROOT=D:\qt\qt_test\qt5\ SET PATH=%_ROOT%\qtbase\bin;%_ROOT%\gnuwin32\bin;%PATH% SET PATH=%_ROOT%\qtrepotools\bin;%PATH% SET _ROOT= call ..\configure -prefix %CD%\qtbase -static -opensource -confirm-license -platform win32-msvc2017 -release ^ -nomake examples -nomake tests -skip qtwebengine -no-openssl -opengl desktop && -developer-build ^ call nmake module-qtbase module-qtdeclarative module-qttools module-qttranslations module-qtwinextras && ^ call nmake install After build is successful I create new script in D:\qt\qt_test_s\installer-framework to build installer framework Make sure installer framework is in correct branch also. You can take a look in installer-framework\INSTALL minimal required version of QT to build IF call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x86 10.0.17763.0 SET QTDIR=D:\qt\qt_test_s\qt5\qt5-build\qtbase SET QTDIR_LIB=%QTDIR%\lib SET PATH=%QTDIR%\bin;%QTDIR%\..\..\gnuwin32\bin;%QTDIR_LIB%;D:\qt\qt_test_s\installer-framework\lib;%PATH% call qmake.exe && ^ call nmake && ^ call nmake install

@JonB Xcode is the macOS IDE offering for development for ANY Apple OS. I have been using it, on and off, since 2006 without too much in the way of problems but Xcode has changed a lot since I last used it in 2021 hence my rustiness. :-)

The code of the installer framework is under the GPLv3. Any changes you do to the installer framework also need to be under the same license. However, any apps that are put into the installer can have any license. The GPL does not apply to the apps.

@Christian-Ehrlicher Well, I tried the obvious, i.e. adding the option -Wno-dev to the two lines with 'cmake' in the configure script. That didn't work. Hopefully, somebody who understands Qt's cmake-building can do it.