From c162c4b5a56604da898078635466e2b1e44b965d Mon Sep 17 00:00:00 2001
From: Oliver Wolff <oliver.wolff@qt.io>
Date: Tue, 4 Dec 2018 12:13:00 +0100
Subject: [PATCH] windows: Fix origin of environment setup script
The mentioned setup scripts are part of the Visual Studio installation.
Change-Id: I8cbb3867f892b6baee0d1e09fce89d36faae173a
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
---
doc/src/platforms/windows.qdoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/platforms/windows.qdoc b/doc/src/platforms/windows.qdoc
index 458a7016..4b6047c0 100644
--- a/doc/src/platforms/windows.qdoc
+++ b/doc/src/platforms/windows.qdoc
@@ -1057,7 +1057,7 @@
We recommend creating a desktop link that opens a command
prompt with the environment set up similar to the
- \uicontrol{Command Prompt} menu entries provided by the Windows SDKs.
+ \uicontrol{Command Prompt} menu entries provided by Visual Studio.
This is done by creating an application link passing a \c .cmd file setting
up the environment and the command line option \c /k (remain open)
to \c cmd.exe.
@@ -1081,7 +1081,7 @@
\note Setups for MinGW are similar; they differ
only in that the \c bin folder of the installation should be added to the
- path instead of calling the Windows SDK setup script. For MinGW, please make
+ path instead of calling the Visual Studio setup script. For MinGW, please make
sure that no \c sh.exe can be found in the path, as it affects \c {mingw32-make}.
Settings required by the additional libraries (see \l{Qt for Windows - Requirements})
--
GitLab