Re: Switch master and master-2.4 to Visual Studio 2015?

[Roland Knall <rknall () gmail com>]

Jumping to 2017 would bring some advantages in building, as well as
build-system integration, native cmake integration for instance. But I
would only jump for the master.

We also would have to consider, a lot of people building on company PCs may
not have the option to switch to 2017, as they are set on a version by
their IT departments. Therefore we would have to keep compatibility to
older versions (2015 at least), but this could be handled by cmake.

cheers
Roland

On Wed, Jun 7, 2017 at 11:03 AM, Graham Bloice <graham.bloice () trihedral com>
wrote:

> On 7 June 2017 at 00:11, Gerald Combs <gerald () wireshark org> wrote:
>
> > We currently build all of our Windows packages using Visual Studio 2013.
> > Unless anyone has any objections I'd like to switch the master and
> > master-2.4 builders to Visual Studio 2015 Update 3 ahead of the 2.4 release.
> No objections, although I was considering a jump straight to 2017 once I
> work out how to get the Qt 5.9 build for 2017.
>
> --
> Graham Bloice
>
> ____________________________________________________________
> _______________
> 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
___________________________________________________________________________
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