Doc: Updated the deployment docs

Added info. about the need to deploy
QtWebEngineProcess.exe.

Change-Id: I5634e503ecc292fdd8c33b2638e8f3aac56e9eec
Task-number: QTBUG-44222
Reviewed-by: Andy Shaw <andy.shaw@digia.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>

1 files changed, 24 insertions, 7 deletions

diff --git a/doc/src/platforms/windows.qdoc b/doc/src/platforms/windows.qdoc
index 27aba60a..db382a56 100644
--- a/doc/src/platforms/windows.qdoc
+++ b/doc/src/platforms/windows.qdoc
@@ -597,23 +597,40 @@
     as well as the executable to the same directory tree in the \c release
     subdirectory.
 
-    In contrast to user plugins, Qt plugins have to be put into subdirectories
+    In contrast to user plugins, Qt plugins must be put into subdirectories
     matching the plugin type. The correct location for the platform plugin
     is a subdirectory named \c {platforms}. \l{Qt Plugins} section has
     additional information about plugins and how Qt searches for them.
 
-    Qt relies on the \l{ICU} library for unicode support. Therefore, you must
+    Qt relies on the \l{ICU} library for unicode support. You must
     include the ICU DLLs that are located in the \c bin directory of your Qt
     installation if Qt was configured to use ICU. The Qt version bundled in
     the Qt5 package uses ICU, so deployment is needed there. The ICU DLLs are
     version dependent and have to match the ones your Qt version was linked
     against.
 
-    If you are using \l{ANGLE} (the default) then you additionally
-    need to include both libEGL.dll and libGLESv2.dll from Qt's 'lib'
-    directory as well as the HLSL compiler from DirectX. The HLSL
-    compiler library is called d3dcompiler_XX.dll where XX is the
-    version number that ANGLE (libGLESv2) was linked against.
+    If \l{ANGLE} (the default) is used, you additionally need to include both
+    \c libEGL.dll and \c libGLESv2.dll from Qt's 'lib' directory as well as
+    the HLSL compiler from DirectX. The HLSL compiler library,
+    d3dcompiler_XX.dll, where XX is the version number that ANGLE (libGLESv2)
+    was linked against.
+
+    If your application depends on Qt WebEngine, you must deploy
+    \c{<Qt install path>/bin/QtWebEngineProcess.exe} to the application install
+    path. If you chose to deploy the binary to a different path, set the
+    \c QTWEBENGINEPROCESS_PATH environment variable to the binary's absolute
+    path (including its file name). This enables the application to find the
+    binary and execute it for every instance of QWebEngineView or
+    WebEngineView created. For example, a browser application with two tabs
+    open should have two separate processes of \c QtWebEngineProcess.exe
+    running. This is a common approach used by most modern web engines to
+    provide a stable browsing experience.
+
+    \note To support HTML5 videos, you must additionally deploy
+    \c ffmpegsumo.dll (WebM codec plugin) into the \c qtwebengine directory
+    under the application install path, and ensure that \c Prefix or
+    \c PluginsPath variable is set to "." in
+    \c{<Qt install path>/<Qt version>/msvc2013/qt.conf}.
 
     Remember that if your application depends on compiler specific
     libraries, these must be redistributed along with your