Wireshark · Wireshark-dev: Re: [Wireshark-dev] report from the bleeding edge (VS 2017)

[Roland Knall <rknall@xxxxxxxxx>]

Should start to bookmark that page ;-)

Just saying, we have to support 2.2 until the end of the year, so removing libraries might lead to issues.

But otherwise, I think we can handle dropping 32bit support, and just note in the building instructions, that people cannot rely on the fact, that we have tested the versions for 32bit.

cheers

Roland

On Wed, Feb 14, 2018 at 11:56 AM, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:

On 14 February 2018 at 10:29, Roland Knall <rknall@xxxxxxxxx> wrote:

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.

The last version to officially support XP was 1.10.  The last version to support Server 2003 was 1.12.  The last version to officially support vista was 2.2.  The last 32 bit OSX version was 2.0.

See the lifecycle page for more info: https://wiki.wireshark.org/Development/LifeCycle.

 

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

On 14 February 2018 at 06:24, Anders Broman <a.broman58@xxxxxxxxx> wrote:

Den 14 feb. 2018 6:58 fm skrev "Pascal Quantin" <pascal.quantin@xxxxxxxxx>:

Le 14 févr. 2018 02:24, "Gerald Combs" <gerald@xxxxxxxxxxxxx> 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

On Wed, Feb 14, 2018 at 11:27 AM, Pascal Quantin <pascal.quantin@xxxxxxxxx> wrote:

2018-02-14 11:24 GMT+01:00 Graham Bloice <graham.bloice@xxxxxxxxxxxxx>:

On 14 February 2018 at 06:24, Anders Broman <a.broman58@xxxxxxxxx> wrote:

Den 14 feb. 2018 6:58 fm skrev "Pascal Quantin" <pascal.quantin@xxxxxxxxx>:

Le 14 févr. 2018 02:24, "Gerald Combs" <gerald@xxxxxxxxxxxxx> 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?

--

Graham Bloice

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
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