Move deploying Qt WebEngine apps on Windows to Qt WebEngine module

Placing all Qt WebEngine deployment information in the module docs
makes it easier for the team to keep the information up to date.

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

1 files changed, 2 insertions, 16 deletions

diff --git a/doc/src/platforms/windows.qdoc b/doc/src/platforms/windows.qdoc
index 612ba59a..70a161b7 100644
--- a/doc/src/platforms/windows.qdoc
+++ b/doc/src/platforms/windows.qdoc
@@ -705,22 +705,8 @@
     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 or under the path that the
-    \c PluginsPath variable was set to in
-    \c{<Qt install path>/<Qt version>/msvc2013/qt.conf}.
+    \note \l{Qt WebEngine} applications have additional requirements that are
+    listed in \l{Deploying Qt WebEngine Applications}.
 
     Remember that if your application depends on compiler specific
     libraries, these must be redistributed along with your