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

On Feb 14, 2018, at 5:15 PM, Gerald Combs wrote: > As far as library compatibility goes, according to > > https://docs.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017 > > we *should* be able to build using Visual C++ 2017 and use libraries compiled > with Visual

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

I'd second the shorter lifespan of 3.0. It also emphasizes the point, that this is a major change release, and it should mature over time. Roland On Thu, Feb 15, 2018 at 6:55 PM, Anders Broman wrote: > > > Den 15 feb. 2018 6:41 em skrev "Gerald Combs"

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

Den 15 feb. 2018 6:41 em skrev "Gerald Combs" : On 2/14/18 11:08 PM, Alexis La Goutte wrote: > > 2.6 is TLS release ? i think it will be nice to kept support of 32bits and > drop for 3.0 I think it makes sense to extend the release lifetime of 2.6 to 30 months. At the same

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

On 2/14/18 11:08 PM, Alexis La Goutte wrote: > > 2.6 is TLS release ? i think it will be nice to kept support of 32bits and > drop for 3.0 I think it makes sense to extend the release lifetime of 2.6 to 30 months. At the same time I'd like to avoid having more than three active stable releases

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

On Thu, Feb 15, 2018 at 2:15 AM, Gerald Combs wrote: > On 2/14/18 2:27 AM, Pascal Quantin wrote: > > > > > > 2018-02-14 11:24 GMT+01:00 Graham Bloice > >: > > > > > > > > On 14 February 2018 at 06:24,

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

On 2/9/18 8:51 AM, Ed Beroset wrote: > > Specifying platform > === > I used this command for CMake: > > cmake -DENABLE_CHM_GUIDES=on -G "Visual Studio 15 2017 Win64" .. > > I found that I had to explicitly specify the platform when using msbuild.  > For example, to build a

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

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

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

On 14 February 2018 at 10:29, Roland Knall 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

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

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

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

2018-02-14 11:24 GMT+01:00 Graham Bloice : > > > On 14 February 2018 at 06:24, Anders Broman wrote: > >> >> >> Den 14 feb. 2018 6:58 fm skrev "Pascal Quantin" > >: >> >> >> >> Le 14 févr. 2018 02:24, "Gerald Combs"

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

On 14 February 2018 at 06:24, Anders Broman wrote: > > > Den 14 feb. 2018 6:58 fm skrev "Pascal Quantin" >: > > > > Le 14 févr. 2018 02:24, "Gerald Combs" a écrit : > > On 2/13/18 8:26 AM, Anders Broman wrote: > > > > For

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

Den 14 feb. 2018 6:58 fm skrev "Pascal Quantin" : Le 14 févr. 2018 02:24, "Gerald Combs" 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 >

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

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

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

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 >

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

-Original Message- From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Ed Beroset Sent: den 9 februari 2018 17:52 To: wireshark-dev@wireshark.org Subject: [Wireshark-dev] report from the bleeding edge (VS 2017) On 04/24/2017 01:01 PM, Graham Bloice wrote: >