[GNUnet-SVN] [gnurl] 66/178: winbuild: updated the documentation

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnurl.

commit 73070e82423aa64b381fa4bf51ea7ad380c538fc
Author: kdekker <address@hidden>
AuthorDate: Mon Apr 9 10:42:14 2018 +0200

    winbuild: updated the documentation
    
    The setenv command no longer exists and visual studio build prompts got
    changed. Used Visual Studio 2015/2017 as reference.
    
    Closes #2472
---
 .mailmap                   |  1 +
 winbuild/BUILD.WINDOWS.txt | 26 ++++++++++++++++++--------
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/.mailmap b/.mailmap
index 0e173c059..44f1020f6 100644
--- a/.mailmap
+++ b/.mailmap
@@ -40,3 +40,4 @@ Dan Fandrich <address@hidden>
 Henrik S. Gaßmann <address@hidden>
 Jiří Malák <address@hidden>
 Nick Zitzmann <address@hidden>
+Kees Dekker <address@hidden>
diff --git a/winbuild/BUILD.WINDOWS.txt b/winbuild/BUILD.WINDOWS.txt
index 98deed01e..76887dcda 100644
--- a/winbuild/BUILD.WINDOWS.txt
+++ b/winbuild/BUILD.WINDOWS.txt
@@ -12,7 +12,7 @@ Building with Visual C++, prerequisites
 
    The latest Platform SDK can be downloaded freely from:
 
-    https://msdn.microsoft.com/en-us/windows/bb980924
+    https://developer.microsoft.com/nl-nl/windows/downloads/sdk-archive
 
    If you are building with VC6 then you will also need the February 2003
    Edition of the Platform SDK which can be downloaded from:
@@ -44,15 +44,25 @@ Building straight from git
 Building with Visual C++
 ========================
 
-Open a Visual Studio Command prompt or the SDK CMD shell.
+Open a Visual Studio Command prompt:
 
-    Using the CMD Shell:
-     choose the right environment via the setenv command (see setenv /?)
-     for the full list of options. setenv /xp /x86 /release for example.
+     Using the 'Developer Command Prompt for VS <version>' menu entry:
+       where version is the Visual Studio version. The developer prompt at 
default
+       uses the x86 mode. It is required to call Vcvarsall.bat to setup the 
prompt
+       for the machine type you want, using Vcvarsall.bat.
+       This type of command prompt may not exist in all Visual Studio versions.
 
-    Using the Visual Studio command prompt Shell:
-     Everything is already pre-configured by calling one of the command
-     prompt.
+       For more information, check:
+         
https://docs.microsoft.com/en-us/dotnet/framework/tools/developer-command-prompt-for-vs
+         
https://docs.microsoft.com/en-us/cpp/build/how-to-enable-a-64-bit-visual-cpp-toolset-on-the-command-line
+
+     Using the 'VS <version> <platform> <type> Command Prompt' menu entry:
+       where version is the Visual Studio version, platform is e.g. x64
+       and type Native of Cross platform build.  This type of command prompt
+       may not exist in all Visual Studio versions.
+
+       See also:
+         https://msdn.microsoft.com/en-us/library/f2ccy3wt.aspx
 
 Once you are in the console, go to the winbuild directory in the Curl
 sources:

-- 
To stop receiving notification emails like this one, please contact
address@hidden