ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] QT graphics version for Windows

From: Pascal Quantin <pascal.quantin@xxxxxxxxx>
Date: Tue, 18 Nov 2014 18:35:49 +0100


Le 18 nov. 2014 18:28, "Gerald Combs" <gerald@xxxxxxxxxxxxx> a écrit :
>
> On 11/18/14 4:54 AM, Pascal Quantin wrote:
>>
>> 2014-11-18 13:35 GMT+01:00 Graham Bloice <graham.bloice@xxxxxxxxxxxxx>:
>>>
>>> I just noticed that the buildbots (and presumably the releases) are using the opengl version of QT, whereas I've always used the angle version in my local builds.
>>>
>>> The QT page on the choice (http://qt-project.org/wiki/Qt-5-on-Windows-ANGLE-and-OpenGL) implies that the angle version is more general purpose and required if you want to use RDP or QTMultimedia video.
>>>
>>> Has there been an explicit discussion on the QT version that I've missed, or should we discuss this now?
>>
>>
>> Hi Graham,
>>
>> I don't think this was ever discussed. As RDP is a quite common usage on Windows (as seen with the GTK2 specific memory bug reports we got), ANGLE would seem to be the best choice. The drawback of dropping Windows XP support is not an issue as we already decided to stop supporting it officially.
>
> We fall under the " Your application does not use OpenGL at all" case described in the page linked above, so I followed their recommendations and installed the OpenGL packages. If anyone plans on adding an RTP video player or using QGLWidget I can switch to the ANGLE packages.
>
> Are there issues with using our current packages over RDP? It's been working fine here, even at low color depths.

I did not check it myself and just assumed that what was written on the Qt page was right. If it works with OpenGL and RDP,  that's fine! (and I will change my local configuration).

> BTW, there are unofficial Chocolatey packages for the Qt SDK and Creator: https://chocolatey.org/packages?q=qt-sdk, although 64-bit VS2013 support seems to be missing. It might be feasible to create a wireshark-build-essentials metapackage at some point.
>