Doc: Move info about deployment on Windows from qtdoc module

This information was in the "Qt for Windows - Deployment" topic.

Change-Id: I309a53001695f8d287c819852a3457a75ec17657
Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io>

1 files changed, 22 insertions, 0 deletions

diff --git a/src/webengine/doc/src/qtwebengine-deploying.qdoc b/src/webengine/doc/src/qtwebengine-deploying.qdoc
index 4aa57c0df..7286cc780 100644
--- a/src/webengine/doc/src/qtwebengine-deploying.qdoc
+++ b/src/webengine/doc/src/qtwebengine-deploying.qdoc
@@ -41,4 +41,26 @@
 
     For more information on deploying Qt applications, please see
     \l {Deploying Qt Applications}.
+
+    \section1 Deploying Qt WebEngine Applications on Windows
+
+    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 or under the path that the
+    \c PluginsPath variable was set to in
+    \c{<Qt install path>/<Qt version>/msvc2013/qt.conf}.
+
+    For more information about deploying applications on Windows, see
+    \l{Qt for Windows - Deployment}.
 */