Installation and Deployment

The above has been fixed, but now getting different error: /usr/include/nspr4 -isystem/usr/include/libxml2 -isystem/usr/include/libxml2 -Wno-narrowing -Wno-class-memaccess -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -Wno-invalid-offsetof -Wno-return-type -Wno-deprecated-copy -Wno-invalid-offsetof -Wno-deprecated-copy -Wno-expansion-to-defined -std=gnu++20 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c gen/third_party/blink/renderer/core/core_jumbo_291.cc -o obj/third_party/blink/renderer/core/core/core_jumbo_291.o In file included from ./../../../../../../qtwebengine/src/3rdparty/chromium/third_party/blink/renderer/core/xml/xslt_extensions.cc:32, from gen/third_party/blink/renderer/core/core_jumbo_291.cc:11: /usr/include/libxslt/xsltutils.h:292:23: error: ‘XSLT_DEBUG_NONE’ conflicts with a previous declaration 292 | XSLT_DEBUG_NONE = 0, /* no debugging allowed / | ^ In file included from ./../../../../../../qtwebengine/src/3rdparty/chromium/third_party/blink/renderer/core/xml/xsl_style_sheet_libxslt.cc:26, from gen/third_party/blink/renderer/core/core_jumbo_291.cc:10: /usr/include/libxslt/xsltutils.h:292:5: note: previous declaration ‘xsltDebugStatusCodes XSLT_DEBUG_NONE’ 292 | XSLT_DEBUG_NONE = 0, / no debugging allowed */ | ^~~~~~~~~~~~~~~ In file included from ./../../../../../../qtwebengine/src/3rdparty/chromium/third_party/blink/renderer/core/xml/xslt_extensions.cc:32, from gen/third_party/blink/renderer/core/core_jumbo_291.cc:11: /usr/include/libxslt/xsltutils.h:293:5: error: ‘XSLT_DEBUG_INIT’ conflicts with a previous declaration 293 | XSLT_DEBUG_INIT, My configuration options: /usr/bin/cmake ../ -G Ninja -DCMAKE_INSTALL_PREFIX=/dt/temp_nipandey/qt6.9.1 -DCMAKE_C_COMPILER=/tools/install/gcc-10.3.0-rocky8/bin/gcc -DCMAKE_CXX_COMPILER=/tools/install/gcc-10.3.0-rocky8/bin/g++ -DCMAKE_BUILD_TYPE=Release -DQT_FEATURE_opengles2=ON -DQT_FEATURE_x11_xss=OFF -DQT_BUILD_EXAMPLES=OFF -DQT_BUILD_TESTS=OFF -DQT_FEATURE_webengine=ON -DQT_FEATURE_webengine_core=ON -DQT_FEATURE_webengine_widgets=ON -DQT_FEATURE_webgl=ON -DQT_FEATURE_webchannel=ON -DQT_FEATURE_network=ON -DFEATURE_system_xcb_xinput=OFF -DBUILD_SHARED_LIBS=ON -DFEATURE_opengl=ON -DFEATURE_opengl_desktop=ON -DPython3_EXECUTABLE=/tools/install/python-3.8.1-rh7/bin/python3.8 -DCMAKE_PREFIX_PATH=/nipandey/qt/harfbuzz/ -DFEATURE_webengine_system_libxslt=OFF -DFEATURE_webengine_system_libxml2=OFF -DFEATURE_webengine_system_libpng=OFF -DFEATURE_webengine_proprietary_codecs=ON

I built everything that was downloaded in the source folder. Build went fine third time round and once I found "ninja install:Debug" I was able to create and build a new app, and run it in the debugger under Visual Studio. All good. I have raised a bug on the docs and I expect at some point, they will get updated. Edit: Might as well mark this as solved. I have static versions of the libs both debug and release.

I just repeat myself: "24.04 is currently not tested in the ci due to too much failures." - and your output just shows some of them...

When you are selecting the Qt version on the online installer, click "Show" in the top right-> "Archive". Qt5 releases should then be visible.

@Niraj-Pandey said in QtWebengine support on ARM platform: Is that mean we can not build and install QTWebengine module on ARM platform? When chromium does not support arm how should QtWebengine support it?

Hi and welcome to devnet, As silly as it may sound: download their sources and follow their instructions to build them.

Hi, Any particular reason for building all the tests ? If not, then you can still have them configured but not built as part of the rest of the build.

@light_0202 said in Unable to connect to the server: online installation program Do you mean Qt Online Installer? If so then try to set another mirror, see: https://wiki.qt.io/Online_Installer_4.x

I resolved the issue: Previously, I created a folder named 'Qt', but the download consistently failed. Today, I recreated a new folder called 'QtTools', performed a comprehensive cleanup of system junk files and cached data using optimization tools. When I reinstalled Qt, it successfully started downloading and installing!!!!!!!!!!!

Hi, I installed VS2022 "Desktop development with C++" and below choice: MSVC v143 - VS 2022 C++ x64/x86 build tools Windows 10/11 SDK Than I can see 2022 compilers now. Regards, Mucip:)

Hi and welcome to devnet, From a quick look at the tool the -m parameter is what you are looking for the Qt module. As for the WrapVulkanHeaders, you need to install the Vulkan SDK for it to work.

Upgrading to Qt installer framework 4.10 (from 4.9) has solved my problem. For future reference, I have a tag like this in my config.xml: <ControlScript>install.qs</ControlScript>. In the config directory, there must be a install.qs file with the script.

I managed to compile the drivers using thecodemonkey guidlines as hinted by @nyquistjack and other web resources. But a lot is required to make the drivers work for WebAssembley.

Downgraded Qt VS Tools Extension to 3.2.0 and that got it working.

@ValeryK said in Qt Installer Framework: online installation of Matlab Runtime 2020b as a component: What are the QIF capabilities for implementing such behavior? For something as complex as this could you installer.performOperation("Execute", ...), like in https://stackoverflow.com/questions/43901488/how-to-run-an-executable-file-in-qt-installer-framework, a program or script you supply which goes through the various steps? (There are also individual Delete and Extract operations there if wanted.)

It's all documented here and it works out of the box. I personally don't use -skip. I explicitly select the submodules I want to build. I always build w/o prefix into directories outside the source tree. E.g. like that: ../dev/configure -developer-build -xcb -nomake examples -make tests -submodules qtdeclarative ninja