Wireshark-dev: Re: [Wireshark-dev] Problems building Wireshark under Windows

From: Guy Harris <gharris@xxxxxxxxx>
Date: Wed, 6 Jul 2022 00:01:56 -0700
On Jul 5, 2022, at 11:20 PM, Guy Harris <gharris@xxxxxxxxx> wrote:

> On Jul 5, 2022, at 10:54 PM, Richard Sharpe <realrichardsharpe@xxxxxxxxx> wrote:
> 
>> C:\Development\wsbuild64>cmake -G "Visual Studio 16 2019" -A x64
>> C:\Users\Richard.Sharpe.A00187\source\wireshark-gl-ds
>> -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19043.
>> -- The C compiler identification is MSVC 19.29.30145.0
>> -- The CXX compiler identification is MSVC 19.29.30145.0
> 
> And mine says
> 
> -- Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.19044.
> -- The C compiler identification is MSVC 19.29.30145.0
> -- The CXX compiler identification is MSVC 19.29.30145.0
> 
> So same compiler, and I have an *older* SDK.

For those who are curious, https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/ says that:

Windows 10 SDK, version 2004 (10.0.19041.0) was "Released in conjunction with Windows 10, version 2004";

Windows 10 SDK, version 1903 (10.0.18362.1) was "Released in conjunction with Windows 10, version 1903."

"Properties" for "This PC says it's running "Windows 10 Pro" version "21H2" build "19044.1766".

Microsoft appear to have little interest in making any of that make sense; fortunately, some Wikipedia editors have made somewhat of an effort to hammer sense into it with a sledgehammer on

	https://en.wikipedia.org/wiki/Windows_10_version_history

so:

	"version 1903" is the "May 2019 Update", codenamed "19H1", build 10.0.18362;

	"version 2004" is the "May 2020 Update", codenamed "20H1", build 10.0.19041;

and 21H2 drops the version numbers in favor of the YYHn code name.  The latest build is 10.0.19044.1806, which is not being offered to me at this point, for some unknown reason.

So it appears that there are a bunch of mysterious rules governing what Microsoft does, and doesn't, offer as updates.

Just for fun, try updating your machine to the latest shiniest Windows 10, and then running the VS updater to see what the latest compiler and SDK you can get is.

Then do a build from scratch, so there's no old CMake or build crufty lying around.