Static builds are not supported.
The requirements for building Qt modules from source are listed separately for each supported platform:
In addition, the following tools are required for building the Qt WebEngine module:
On all platforms, the following tools are required at build time:
On Windows, the following additional tools are required:
Note: It is not recommended to use tools from msys2 or cygwin to build Qt WebEngine as it may result in build errors.
On Linux, Clang or GCC version 10 or later is required.
Qt WebEngine requires pkg-config to detect most of its dependencies. The following pkg-config files are required:
dbus-1fontconfigIf Qt was configured for xcb, the following pkg-config files are also required:
libdrmxcompositexcursorxixrandrxscrnsaverxtstOn macOS, the following are required:
Note: Qt WebEngine cannot be built for the 32-bit mode of macOS (using the macx-clang-32 mkspec).
Building Qt WebEngine with earlier Qt versions (down to the last LTS version) is supported. It means that Qt WebEngine 6.4 can be built with Qt 6.2.x, Qt 6.3.x, and Qt 6.4.
To use an earlier Qt version to build Qt Webengine:
qmake && make (&& make install).Applications using Qt WebEngine are not compatible with the Mac App Store, because:
To make Qt WebEngine work correctly when streaming to an AppleTV from a MacBook that supports GPU switching, it is important to add the NSSupportsAutomaticGraphicsSwitching option to the
application Info.plist file, with the value set to YES. Otherwise rendering issues might occur when creating new web engine view instances after Airplay is switched on or off.
If a new default QSurfaceFormat with a modified OpenGL profile has to be set, it should be set before the application instance is declared, to make sure that all created OpenGL contexts use the same OpenGL profile.
On macOS, if the default QSurfaceFormat is set after the application instance, the application will exit with qFatal(), and print a message that the default QSurfaceFormat should be set before the application instance.
Qt WebEngine provides out-of-the-box sandboxing support for Chromium render processes.
On Linux, note the following restrictions:
/proc/sys/kernel/unprivileged_userns_clone to 1.seccomp-bpf feature (kernel version 3.5 or later).To explicitly disable sandboxing, use one of the following options:
QTWEBENGINE_DISABLE_SANDBOX environment variable to 1.--no-sandbox command line argument to the user application executable.QTWEBENGINE_CHROMIUM_FLAGS to --no-sandbox.For more information, see Using Command-Line Arguments.
When running Qt Web Engine examples in a Docker container and browsing content-heavy sites, BUS errors (SIGBUS) might be reported. Typically, this is caused by Docker running a container with a too small memory space (such as 64MB). To fix this problem, increase the memory space size.
Qt WebEngine enables accessibility support for web pages when the following conditions are met:
On some old Linux configurations, accessibility can cause a significant slowdown on large HTML pages.
Because of that, Qt WebEngine accessibility support can be disabled on Linux, by setting the QTWEBENGINE_ENABLE_LINUX_ACCESSIBILITY environment variable to 0.
Because of a limitation in the Windows compositor, applications that show a fullscreen web engine view will not properly display popups or other top-level windows. The reason and workaround is described in Fullscreen OpenGL Based Windows.
A manifest is an XML file that is read when the program starts and informs Windows how to run the program. Some Qt WebEngine features may require adding a manifest file for the user application to work correctly on Windows.
The following snippets show the manifest file's structure and how to embed it into the program.
Note: These code snippets are taken from the WebEngine Quick Nano Browser example.
The manifest file defines which Windows versions the application supports. httpUserAgent needs this information to report the correct Windows version.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
<application>
<!--The ID below indicates application support for Windows Vista -->
<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
<!--The ID below indicates application support for Windows 7 -->
<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
<!--The ID below indicates application support for Windows 8 -->
<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
<!--The ID below indicates application support for Windows 8.1 -->
<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
<!--The ID below indicates application support for Windows 10/11 -->
<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
</application>
</compatibility>
</assembly>
To embed the file into the executable, add it to the sources:
...
qt_add_executable(quicknanobrowser
main.cpp
utils.h
)
if(WIN32)
set_property(
TARGET quicknanobrowser
APPEND PROPERTY
SOURCES quicknanobrowser.exe.manifest)
endif()
...
For more information, see the Application manifest documentation page.
