Re: report from the bleeding edge (VS 2017)

[Anders Broman <anders.broman () ericsson com>]

Hi,
Also remember we are not dropping support for building with older/other Visual Studio versions per-se, just not 
producing packages/verifying them at this point.
We will not pick up breakage ourselves though. I guess it will be a problem if we update any of the support libraries ☹ 
But we could let them stay at the current level.
If there is people interested in the 32bit version they can perhaps assist in checking 32bit builds and help update the 
support libraries?
Regards
Anders

From: Wireshark-dev [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Roland Knall
Sent: den 14 februari 2018 11:29
To: Developer support list for Wireshark <wireshark-dev () wireshark org>
Subject: Re: [Wireshark-dev] report from the bleeding edge (VS 2017)

The question from me would be, would this also mean dropping support for older Windows versions?

It will definitely cut off WinXP, but could also cut off a Win7-32bit version? Not sure if such a version exists, but 
those are also applicable to their Windows Server counter-part.

I am all for dropping support on older versions, but some users might never be able to switch, as they are fixed to 
their Windows version. (ISS for a more fun and exotic example, ;-) )

Just something to discuss I guess.



On Wed, Feb 14, 2018 at 11:24 AM, Graham Bloice <graham.bloice () trihedral com<mailto:graham.bloice () trihedral com>> 
wrote:


On 14 February 2018 at 06:24, Anders Broman <a.broman58 () gmail com<mailto:a.broman58 () gmail com>> wrote:


Den 14 feb. 2018 6:58 fm skrev "Pascal Quantin" <pascal.quantin () gmail com<mailto:pascal.quantin () gmail com>>:


Le 14 févr. 2018 02:24, "Gerald Combs" <gerald () wireshark org<mailto:gerald () wireshark org>> a écrit :
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.

The availability of a 32bits Qt package for MSVC2017? I would find it a bit weird to use MSVC2015 for the x86 binary 
and MSVC2017 for the x64 one.

Do we still need to build for 32 bits?


Personally I'd be happy to drop the 32 bit version, what the rest of the world would make of it, I'm not so sure.

--
Graham Bloice

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org<mailto:wireshark-dev () wireshark org>>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org<mailto:wireshark-dev-request () wireshark 
org>?subject=unsubscribe


On Wed, Feb 14, 2018 at 11:27 AM, Pascal Quantin <pascal.quantin () gmail com<mailto:pascal.quantin () gmail com>> 
wrote:


2018-02-14 11:24 GMT+01:00 Graham Bloice <graham.bloice () trihedral com<mailto:graham.bloice () trihedral com>>:


On 14 February 2018 at 06:24, Anders Broman <a.broman58 () gmail com<mailto:a.broman58 () gmail com>> wrote:


Den 14 feb. 2018 6:58 fm skrev "Pascal Quantin" <pascal.quantin () gmail com<mailto:pascal.quantin () gmail com>>:


Le 14 févr. 2018 02:24, "Gerald Combs" <gerald () wireshark org<mailto:gerald () wireshark org>> a écrit :
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.

The availability of a 32bits Qt package for MSVC2017? I would find it a bit weird to use MSVC2015 for the x86 binary 
and MSVC2017 for the x64 one.

Do we still need to build for 32 bits?


Personally I'd be happy to drop the 32 bit version, what the rest of the world would make of it, I'm not so sure.

I guess a good indicator would be how often the x86 variant is downloaded. Gerald, do you have this number?

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org<mailto:wireshark-dev () wireshark org>>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org<mailto:wireshark-dev-request () wireshark 
org>?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe