diff options
author | Guy Harris <guy@alum.mit.edu> | 2018-10-12 12:11:06 -0700 |
---|---|---|
committer | Guy Harris <guy@alum.mit.edu> | 2018-10-12 19:11:43 +0000 |
commit | 01ed5b84f394dfd5b414e181d8f6d7b62c528cac (patch) | |
tree | 954e2e3cf08581a411aec008485acfe42c9a626d /docbook/wsdg_src/WSDG_chapter_tools.asciidoc | |
parent | aba59e5973af5e8b2e0705bba3c8f2d47791261b (diff) |
Updates.
We use VS 2017, not VS 2015, for 2.6.x and development builds.
Microsoft's documentation is moving from msdn.microsoft.com to
docs.microsoft.com.
The way you download pre-2017 versions of VS has changed.
Update links to the Android, GNOME, KDE and macOS human interface
guidelines while we're at it.
Change-Id: I1a3973f76aa5b476cb906b8a8604b82d6131e9c5
Reviewed-on: https://code.wireshark.org/review/30168
Reviewed-by: Guy Harris <guy@alum.mit.edu>
Diffstat (limited to 'docbook/wsdg_src/WSDG_chapter_tools.asciidoc')
-rw-r--r-- | docbook/wsdg_src/WSDG_chapter_tools.asciidoc | 34 |
1 files changed, 22 insertions, 12 deletions
diff --git a/docbook/wsdg_src/WSDG_chapter_tools.asciidoc b/docbook/wsdg_src/WSDG_chapter_tools.asciidoc index aaa50d1754..dfcb598d19 100644 --- a/docbook/wsdg_src/WSDG_chapter_tools.asciidoc +++ b/docbook/wsdg_src/WSDG_chapter_tools.asciidoc @@ -343,7 +343,8 @@ _windows.h_, _WSock32.lib_) ==== Official Toolchain Packages And Alternatives -The official Wireshark 2.4.x releases are compiled using Microsoft Visual {cpp} 2015. +The official Wireshark 2.6.x releases are compiled using Microsoft Visual {cpp} 2017. +The Wireshark 2.4.x releases are compiled using Microsoft Visual {cpp} 2015. The Wireshark 2.2.x and 2.0.x releases are compiled using Microsoft Visual {cpp} 2013. The Wireshark 1.12.x and 1.10.x releases were compiled using Microsoft Visual {cpp} 2010 SP1. @@ -365,13 +366,24 @@ package is to be used. See <<msvc-runtime-redistributable>> below for more details. However, you might already have a different Microsoft {cpp} compiler -installed. It should be possible to use any of the following with the considerations listed: +installed. It should be possible to use any of the following with the +considerations listed. You will need to sign up for a +https://visualstudio.microsoft.com/dev-essentials/[Visual Studio Dev +Essentials] account if you don't have a Visual Studio (MSDN) +subscription. The older versions can be downloaded from +https://visualstudio.microsoft.com/vs/older-downloads/[]. -.Visual {cpp} 2013 Community Edition +.Visual {cpp} 2015 Community Edition IDE + Debugger?:: Yes -Purchase required?:: http://www.visualstudio.com/en-us/downloads/download-visual-studio-vs#d-community[Free Download] +SDK required for 64-bit builds?:: No + +CMake Generator: *`Visual Studio 14`* + +.Visual {cpp} 2013 Community Edition + +IDE + Debugger?:: Yes SDK required for 64-bit builds?:: No @@ -381,8 +393,6 @@ CMake Generator: *`Visual Studio 12`* IDE + Debugger?:: Yes -Purchase required?:: http://www.microsoft.com/express/Downloads/#Visual_Studio_2010_Express_Downloads[Free Download] - SDK required for 64-bit builds?:: Yes. CMake Generator: *`Visual Studio 10`* @@ -451,7 +461,7 @@ usage: cl [ option... ] filename... [ /link linkoption... However, the version string may vary. Documentation on the compiler can be found at -http://msdn.microsoft.com/en-us/library/wk21sfcf.aspx[Microsoft MSDN] +https://docs.microsoft.com/en-us/cpp/build/reference/compiling-a-c-cpp-program?view=vs-2017[Microsoft Docs] ==== link.exe (Linker) @@ -475,7 +485,7 @@ Copyright (C) Microsoft Corporation. All rights reserved. However, the version string may vary. Documentation on the linker can be found at -http://msdn.microsoft.com/en-us/library/t2fck18t.aspx[Microsoft MSDN] +https://docs.microsoft.com/en-us/cpp/build/reference/linking?view=vs-2017[Microsoft Docs] [[msvc-runtime-redistributable]] @@ -509,10 +519,10 @@ can't be legally redistributed by third parties like us. ==== -The following MSDN link is recommended for the +The following Microsoft Docs link is recommended for the interested reader: -* http://msdn.microsoft.com/en-us/library/ms235299.aspx[Redistributing Visual C++ Files] +* https://docs.microsoft.com/en-us/cpp/ide/redistributing-visual-cpp-files?view=vs-2017[Redistributing Visual C++ Files] In all cases where _vcredist_x86.exe_ or _vcredist_x64.exe_ is downloaded it should be downloaded to the directory into which the support @@ -524,7 +534,7 @@ It need not, and should not, be run after being downloaded. There are three redistribution methods that MSDN mentions for MSVC 2013 (see: -http://msdn.microsoft.com/en-us/library/vstudio/ms235316(v=vs.120).aspx["Choosing a Deployment Method"]): +https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2013/ms235316(v=vs.120)["Choosing a Deployment Method"]): . _Using Visual {cpp} Redistributable Package._ The Microsoft libraries are installed by copying @@ -692,7 +702,7 @@ debugging with the Visual Studio integrated debugger it can be helpful if you have to debug on a machine where an integrated debugger is not available. You can get it free of charge from Microsoft in several ways, see the -http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063%28v=vs.85%29.aspx)[Debugging tools for Windows] page. +https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/[Debugging tools for Windows] page. You can also use Chocolatey to install WinDbg: |