Wireshark-dev: Re: [Wireshark-dev] report from the bleeding edge (VS 2017)
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 13 Feb 2018 17:24:23 -0800
On 2/13/18 8:26 AM, Anders Broman wrote:
> 
> For what it's worth I have been building and distributing for VS 2017 for almost a year on Win7
> Cygwin and python set up as per developers guide from way back. 
> I have the following batch script I run in my cmd window 
> **********************************************************************
> ** Visual Studio 2017 Developer Command Prompt v15.5.6
> ** Copyright (c) 2017 Microsoft Corporation
> **********************************************************************
> [vcvarsall.bat] Environment initialized for: 'x64'
> 
> set CYGWIN=nodosfilewarning
> set WIRESHARK_BASE_DIR=C:\Development
> set QT5_BASE_DIR=C:\Qt\5.9.4\msvc2017_64
> set WIRESHARK_TARGET_PLATFORM=win64
> set PATH=path=%PATH%;C:\cygwin64\bin;C:\Program Files\CMake\bin;C:\Python27
> 
> Then
> cmake -DENABLE_CHM_GUIDES=on -G "Visual Studio 15 Win64" ..\wireshark
> and
> msbuild /m /p:Configuration=RelWithDebInfo Wireshark.sln 2>&1 > log.txt

Is there any reason we shouldn't switch to VS 2017 before the 2.6 release?
It's installed on the main and PD Windows builders.