I used Qt 5.7 to build on Windows, 64-bit, yesterday and today. Should it be avoided, in favor for Qt 5.6 ?
Gilbert On Mon, Sep 12, 2016 at 5:06 PM, Graham Bloice <graham.blo...@trihedral.com> wrote: > > > On 12 September 2016 at 20:22, Bill Meier <wme...@newsguy.com> wrote: > >> On 9/12/2016 3:11 PM, Bill Meier wrote: >> >>> I'm finally getting around to building Wireshark (Windows 7 32 bit) >>> again. >>> >>> What version of QT should be used ? >>> >>> WSDG sec 2.2.4 doesn't really say (although shows 5.5 in the example). >>> WSDG sec 2.2.10 (which I just happened to see) says 5.6.1 >>> The Master buildbot seems to be using 5.3 >>> >>> Also: wdsg sec 2.2.4 implies that the "OpenGL" version should be used. >>> Is this correct ? >>> >>> >> Update: I now see that master is actually using QT 5.6 so I'll use that >> version. (I was wrongly looking at a Wireshark 2.2 builder). >> >> Still not sure about Open-GL vs not Open-GL ? >> >> > As per the WSDG, Sect 2.2.10, 5.6.1 is recommended, although there is a -1 > build out now from Qt. > > I don't think you get the choice of non Open GL for 5.6 onwards. > > The docs could be cleaned up a bit here, they should list the recommended > Qt versions for each release and all the examples should be consistent. > > Windows is actually a bit further forwards here in the Qt version used, > because of no in-built distribution inertia. > > -- > Graham Bloice > > ____________________________________________________________ > _______________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@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-requ...@wireshark.org?subject=unsubscribe
