Wireshark-dev: Re: [Wireshark-dev] Go to Qt 5.9 on Windows build bots?

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 14 Jun 2017 13:44:16 -0700
The Windows builders are now using the following compiler and Qt versions:

master:     Visual Studio 2015 + Qt 5.9.0
master-2.4: Visual Studio 2015 + Qt 5.6.2
master-2.2: Visual Studio 2013 + Qt 5.6.2
master-2.0: Visual Studio 2013 + Qt 5.3.2

Qt 5.9.1 is scheduled to be released this month. We might want to switch master-2.4 to Qt 5.9 when that happens.

I haven't done any extensive testing, but 5.9 is working fine for me here on macOS and Windows.

On 6/14/17 5:36 AM, Roland Knall wrote:
> +1 Linux and Mac build fine already with 5.9
> 
> Regards
> 
> Am 14.06.2017 um 14:09 schrieb Graham Bloice <graham.bloice@xxxxxxxxxxxxx
> <mailto:graham.bloice@xxxxxxxxxxxxx>>:
> 
>>
>>
>> On 14 June 2017 at 12:55, Pascal Quantin <pascal.quantin@xxxxxxxxx
>> <mailto:pascal.quantin@xxxxxxxxx>> wrote:
>>
>>     Hi Anders,
>>
>>     Le 14 juin 2017 13:49, "Anders Broman" <anders.broman@xxxxxxxxxxxx
>>     <mailto:anders.broman@xxxxxxxxxxxx>> a écrit :
>>
>>         Hi,____
>>
>>         Should we go to Qt 5.9 on the build bots before SharkFest? I have
>>         used t without noticing any problems.
>>
>>
>>     Given that it's the new LTS, it probably makes sense. master-2.0 and
>>     master-2.2 should stay on the previous Qt version to avoid any bad
>>     surprise.
>>
>>
>> +1
>>
>> If only the Qt folks would make VS2017 32 bit builds available. 
>>
>>
>>         ____
>>
>>         This should allow us to decide if we want to switch to MSVC 2015
>>         or 2017 easily. I think Stig has tried it on____
>>
>>         MAC OS too if we want to update that too.____
>>
>>         Regards____
>>
>>         Anders____
>>
>>
>>
>> -- 
>> Graham Bloice
>> ___________________________________________________________________________
>> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx
>> <mailto:wireshark-dev@xxxxxxxxxxxxx>>
>> Archives:    https://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>>             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
> 
> 
> ___________________________________________________________________________
> 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@xxxxxxxxxxxxx?subject=unsubscribe
>