Deploying Qt WebEngine ProcessesQt WebEngine takes advantage of the multi-process model that the Chromium project offers. The multi-process model requires that the Qt WebEngine Process executable be deployed alongside your application.
The WebEngine process is executed for each
QWebEngineView or
WebEngineView instance. For example, a browser application with two tabs open should have two separate instances of the process running. This is a common approach used by most modern web engines to provide a stable browsing experience.
At runtime, Qt WebEngine looks for the
QtWebEngineProcess executable in the directory that
QLibraryInfo::location(
QLibraryInfo::LibraryExecutablesPath) returns. For Qt installations, this is
QTDIR/libexec (
Linux) or
QTDIR\bin (
Windows). The path can be changed by defining a
qt.conf file, for example. Alternatively, an executable path can be set as a value of the
QTWEBENGINEPROCESS_PATH environment variable. On
macOS, Qt WebEngine looks for the executable in
.app/Helpers/QtWebEngineProcess.
Deploying ResourcesQt WebEngine requires the following resource files:
- qtwebengine_resources.pak contains the resources needed by Chromium.
- qtwebengine_devtools_resources.pak contains tools for remote debugging.
- qtwebengine_resources_100p.pak contains images suitable for low resolution displays.
- qtwebengine_resources_200p.pak contains images suitable for high DPI displays.
- icudtl.dat provides support for International Components for Unicode (ICU). It is the Chromium version of ICU, which is not needed if Qt WebEngine was configured to use the system ICU.
Resources are searched from the following locations:
TranslationsLocale data (such as
en-US.pak) is searched form the following locations:
