On Wed, Jul 6, 2022 at 1:43 AM Guy Harris <gharris@xxxxxxxxx> wrote:
>
> 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
>
> And the Windows builder on GitLab says
>
> cmake -G "Visual Studio 17 2022" -A x64 -DUSE_qt6=ON -DENABLE_LTO=off ..
> -- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.17763.
> -- The C compiler identification is MSVC 19.31.31106.2
> -- The CXX compiler identification is MSVC 19.31.31106.2
>
> So should people doing development work switch to VS 2022?
>
> And try to get SDK 10.0.22000.0 (or later) installed?
I upgraded to a more recent SDK but that did not fix the problem:
-------
-- Selecting Windows SDK version 10.0.22621.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
--------
So, it seems that a more recent version of Visual Studio may be needed.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)