[Wireshark-dev] QT graphics version for Windows
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? -- Graham Bloice ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] QT graphics version for Windows
2014-11-18 13:35 GMT+01:00 Graham Bloice graham.blo...@trihedral.com: 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. Regards, Pascal. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] QT graphics version for Windows
On 11/18/14 4:54 AM, Pascal Quantin wrote: 2014-11-18 13:35 GMT+01:00 Graham Bloice graham.blo...@trihedral.com: 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. 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. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] QT graphics version for Windows
Le 18 nov. 2014 18:28, Gerald Combs ger...@wireshark.org a écrit : On 11/18/14 4:54 AM, Pascal Quantin wrote: 2014-11-18 13:35 GMT+01:00 Graham Bloice graham.blo...@trihedral.com: 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. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] QT graphics version for Windows
On 18 November 2014 17:35, Pascal Quantin pascal.quan...@gmail.com wrote: Le 18 nov. 2014 18:28, Gerald Combs ger...@wireshark.org a écrit : On 11/18/14 4:54 AM, Pascal Quantin wrote: 2014-11-18 13:35 GMT+01:00 Graham Bloice graham.blo...@trihedral.com: 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). I didn't check either, just read the page and thought the angle version was best for us. -- Graham Bloice ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] QT graphics version for Windows
On 18 November 2014 17:27, Gerald Combs ger...@wireshark.org wrote: 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. That was on my long list, but might move it up so that it could be invoked by CMake. I'm likely to change my Windows build approach in CMake a bit for the final step as well where we copy all the third party libs into the run directory, by wrapping all that up in a PowerShell script and invoking that from CMake as a custom build task. -- Graham Bloice Software Developer Trihedral UK Limited ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
