Wireshark mailing list archives
Re: Wireshark support for Qt4.8
From: Michał Łabędzki <michal.tomasz.labedzki () gmail com>
Date: Tue, 25 Jul 2017 07:31:35 +0200
+1 for drop Qt4.8 (about 6 years old lib... enough time to upgrade it https://en.wikipedia.org/wiki/Qt_version_history) What about new Qt5 version? Qt5.2 to support Ubuntu 14.04 LTS? (however it seems to be not a problem to have newer one https://wiki.qt.io/Install_Qt_5_on_Ubuntu ) CentOS? http://wiki.qt.io/How_to_Install_Qt_5_and_Qwt_on_CentOS_6 Maybe something like Docker saves the day? One thing about dropping practise - it is good to write about that to some file "requirements.txt?" It may greatly help some people to port or get last available Wireshark for theirs environment. For example: "4th July 2018 - drop Qt 4.8 support, git sha: 4ff4ff4ff4..." PS. Traditionally +1 for drop others build systems (autotools?). [but, +1 also for drop cmake and keeps only autotools...] 2017-07-24 16:06 GMT+02:00 Alexis La Goutte <alexis.lagoutte () gmail com>:
On Mon, Jul 24, 2017 at 3:34 PM, Roland Knall <rknall () gmail com> wrote:Hi Wireshark master currently does not build with Qt 4.8. The reason for that, can be seen in https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13909 These issues should be fixed in the near future. But it raises the bigger topic, if Qt 4.8 should be supported in whatever version comes after 2.4. Are there any big reasons or support cases, where Qt 4.8 is a definite requirement and going to Qt 5.x is not an option? The list on https://wiki.wireshark.org/Development/Support_library_version_tracking is a starting point for discussion I would assume, but as we no longer support Qt 4.6, SLES 12 and RHEL/CentoOS 7 would be my point of reference, and both support Qt 5. Am I missing some references here? An can we start to discuss moving the Qt version to 5.x+1 for may be drop 4.x support if i remember there is some -(core)dev using some old (CentOS?) linux system and don't have Qt 5 support...cheers Roland ___________________________________________________________________________ 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
-- Michał Łabędzki ___________________________________________________________________________ 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
Current thread:
- Wireshark support for Qt4.8 Roland Knall (Jul 24)
- Re: Wireshark support for Qt4.8 Alexis La Goutte (Jul 24)
- Re: Wireshark support for Qt4.8 Michał Łabędzki (Jul 24)
- Re: Wireshark support for Qt4.8 Graham Bloice (Jul 25)
- Re: Wireshark support for Qt4.8 Michał Łabędzki (Jul 24)
- Re: Wireshark support for Qt4.8 Alexis La Goutte (Jul 24)