Re: [Wireshark-dev] 1.11.0 release
On 10/09/13 05:47, Bálint Réczey wrote: Hi Gerald, 2013/10/8 Gerald Combs ger...@wireshark.org: I've scheduled the release of 1.11.0 for next Tuesday, October 15. Corrections and additions for the release notes are welcome. Unfortunately the transitional state of our UI will be reflected in the release packages: Windows 32-bit: GTK3 and Qt Windows 64-bit: GTK2 and Qt OS X 64-bit: Qt OS X 32-bit: GTK2 Source: GTK3 Hopefully this won't cause too much confusion. I'll probably enable Qt by default in the sources in the next few days, so at least the Windows and source tarball will match. Do you mean enabling Qt and GTK in CMake builds? How about dropping the automake based and nmake based makefile systems and replacing both with CMake? CMake should be available on every platform where Qt builds. I think our CMake stuff has a ways to go before it's ready. Someone already mentioned needing to generate the source tarball but another issue is cross compilation. It looks like CMake supports that from v2.6 but I suppose we'd have to do some work to get it working (and who here actually cross compiles? There are users who do but it seems no developers). ___ 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] 1.11.0 release
On 10/09/13 09:15, Bálint Réczey wrote: Hi Guy, 2013/10/9 Guy Harris g...@alum.mit.edu: I think nowadays almost no one builds Wireshark for their own (apart from Developers) and those who do can easily install the tools for it. Hmmm, I'm not so sure about that statement. I've seen (questions from) plenty of folks using Redhat EL/CentOS who compile their own Wireshark because what comes from the vendor is too old. Maybe things have improved in the Solaris world but last time I tried using a package system I gave up and went back to compiling my own. The package system was pulling in too much junk I didn't want/need, it often just plain didn't work, and after all that the Wireshark package was still too old. Of course things are relative: if you compare the hundreds of thousands of downloads a month of the Windows installers against those who compile their own, yes, almost no one compiles their own. ;-) But I suspect among non-Linux *NIX users there are a fair number who still compile their own. ___ 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] 1.11.0 release
On 10/10/13 9:45 AM, Graham Bloice wrote: On 10 October 2013 01:33, Gerald Combs ger...@wireshark.org For people doing development on Windows, would you rather have the Qt SDK in a central location on your system (I've been using c:\Qt) or in WIRESHARK_LIB_DIR with everything else (which means taking up a lot of space if you have multiple WIRESHARK_LIB_DIRs)? I'm the odd one out on this it seems, I have no use for QT5 apart from Wireshark, so would like them in the WIRESHARK_LIB_DIR. I've only ever had two lib dirs, one for x86 and one for amd64. It looks like we can support arbitrary locations, at least with the official Qt installer. Qt binaries on Windows have their path hard-coded although it's possible to change them: http://stackoverflow.com/questions/913642/qmake-and-qt-install-prefix-how-can-i-select-a-new-location-for-qt-library The official installer adjusts the prefix automatically when you install in a non-standard location. The packages I built don't and would require manual adjustment. I checked in a change to look for Qt in both C:\Qt and WIRESHARK_LIB_DIR. The next step is to get it installed without too much fuss. I don't think we should add it to the list of libraries handled by process_libs since that would mean waiting for half a GB to unpack every time you run setup. ___ 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] 1.11.0 release
My vote would be to install in a central location and make it just another step in http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html, just like installing Visual Studio. -Original Message- From: Gerald Combs ger...@wireshark.org To: Developer support list for Wireshark wireshark-dev@wireshark.org Sent: Wed, Oct 9, 2013 8:36 pm Subject: Re: [Wireshark-dev] 1.11.0 release For people doing development on Windows, would you rather have the Qt SDK in a central location on your system (I've been using c:\Qt) or in WIRESHARK_LIB_DIR with everything else (which means taking up a lot of space if you have multiple WIRESHARK_LIB_DIRs)? Also, should we dump the Qt ZIP archives into SVN or distribute them separately? Or tell people to download the official version from qt-project.org? I've signed the DLLs and executables in the archives above with the Wireshark Foundation key. I'm not sure if Digia does the same for the official distribution. ___ 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] 1.11.0 release
On 10/10/2013 10:56 AM, mman...@netscape.net wrote: My vote would be to install in a central location and make it just another step in +1 http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html, just like installing Visual Studio. -Original Message- From: Gerald Combs ger...@wireshark.org To: Developer support list for Wireshark wireshark-dev@wireshark.org Sent: Wed, Oct 9, 2013 8:36 pm Subject: Re: [Wireshark-dev] 1.11.0 release For people doing development on Windows, would you rather have the Qt SDK in a central location on yoursystem (I've been using c:\Qt) or in WIRESHARK_LIB_DIR with everything else (which means taking up a lot of space if you have multiple WIRESHARK_LIB_DIRs)? Also, should we dump the Qt ZIP archives into SVN or distribute them separately? Or tell people to download the official version from qt-project.org? I've signed the DLLs and executables in the archives above with the Wireshark Foundation key. I'm not sure if Digia does the same for the official distribution. ___ 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 ___ 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] 1.11.0 release
Hi Gerald, 2013/10/8 Gerald Combs ger...@wireshark.org: I've scheduled the release of 1.11.0 for next Tuesday, October 15. Corrections and additions for the release notes are welcome. Unfortunately the transitional state of our UI will be reflected in the release packages: Windows 32-bit: GTK3 and Qt Windows 64-bit: GTK2 and Qt OS X 64-bit: Qt OS X 32-bit: GTK2 Source: GTK3 Hopefully this won't cause too much confusion. I'll probably enable Qt by default in the sources in the next few days, so at least the Windows and source tarball will match. Do you mean enabling Qt and GTK in CMake builds? How about dropping the automake based and nmake based makefile systems and replacing both with CMake? CMake should be available on every platform where Qt builds. Cheers, Balint ___ 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] 1.11.0 release
On Oct 9, 2013, at 2:47 AM, Bálint Réczey bal...@balintreczey.hu wrote: How about dropping the automake based and nmake based makefile systems and replacing both with CMake? So do you propose that people who are building from source only because they don't have binary packages available for their platforms should be required to install not only make and a C compiler but also CMake? ___ 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] 1.11.0 release
On Oct 8, 2013, at 12:21 PM, Gerald Combs ger...@wireshark.org wrote: I've scheduled the release of 1.11.0 for next Tuesday, October 15. Meaning we'll no longer be offering a development release that's older than the current stable release? (We should probably drop the development release from the download page once it turns into a stable release, and then reinstate it once we have a development release again.) ___ 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] 1.11.0 release
On 9 October 2013 11:21, Bálint Réczey bal...@balintreczey.hu wrote: 2013/10/9 Guy Harris g...@alum.mit.edu: On Oct 9, 2013, at 2:47 AM, Bálint Réczey bal...@balintreczey.hu wrote: How about dropping the automake based and nmake based makefile systems and replacing both with CMake? So do you propose that people who are building from source only because they don't have binary packages available for their platforms should be required to install not only make and a C compiler but also CMake? Building Wireshark already needs way more tools than just make and a C compiler. IMO with shipping CMake only we could ship something we can reliably maintain finally. I also can't name any platform we would like to support but where CMake is not available easily (like apt-get/yum/etc. install cmake). Although there are binary packages of Wireshark available for Windows, building is a different story. CMake is available for Windows, but the CMake build of Wireshark is still at an early alpha and a fair bit more needs to be done yet. Also the build environment setup still runs as part of the nmake build so that's another blocker. Graham ___ 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] 1.11.0 release
On Oct 9, 2013, at 3:21 AM, Bálint Réczey bal...@balintreczey.hu wrote: Building Wireshark already needs way more tools than just make and a C compiler. Perhaps we should fix that, so that the release tarball includes all generated source. I'd prefer not to require Flex, yacc/Bison, Perl, or Python, ideally. I also can't name any platform we would like to support but where CMake is not available easily (like apt-get/yum/etc. install cmake). http://hpux.connect.org.uk/hppd/cgi-bin/search?term=CMakeSearch=Search although http://hpux.connect.org.uk/hppd/cgi-bin/search?term=QtSearch=Search so maybe they need to add a more modern version of Qt (which may require CMake). cmake.org does have 2.6.4 binaries for HP-UX: http://www.cmake.org/cmake/resources/software.html so hopefully that will be good enough. The HP-UX Porting and Archive Centre does have binaries of Wireshark; whether they'll stop doing so for 1.12 is another matter - hopefully, they won't. (I consider *all* currently-developed UN*Xes as platforms we should at least support to the extent of having third parties be able to package it. The only platforms I see us supporting *directly* are Windows and OS X, because I suspect only a minority of potential users of Wireshark would want to be forced to add on some Linux/BSD-style packaging system just to get Wireshark. Solaris, at least as of Solaris 11, has a Shiny New Packaging System built in, and has Wireshark in that packaging system; HP-UX has the Porting and Archive Centre, and they offer Wireshark and hopefully will continue to do so; AIX, there's The Written Word's packages.) ___ 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] 1.11.0 release
Hi Guy, 2013/10/9 Guy Harris g...@alum.mit.edu: On Oct 9, 2013, at 3:21 AM, Bálint Réczey bal...@balintreczey.hu wrote: Building Wireshark already needs way more tools than just make and a C compiler. Perhaps we should fix that, so that the release tarball includes all generated source. I'd prefer not to require Flex, yacc/Bison, Perl, or Python, ideally. From packaging POV not having generated sources is better, since the packagers needs to be sure that the generated files can be re-generated. In Debian, the policy dictates removing all the generated files from the source before generating packages, for example. I think nowadays almost no one builds Wireshark for their own (apart from Developers) and those who do can easily install the tools for it. Since most of our users use packages I think making packaging easier (i.e. dropping generated files), would be a reasonable way to go. I also can't name any platform we would like to support but where CMake is not available easily (like apt-get/yum/etc. install cmake). http://hpux.connect.org.uk/hppd/cgi-bin/search?term=CMakeSearch=Search although http://hpux.connect.org.uk/hppd/cgi-bin/search?term=QtSearch=Search so maybe they need to add a more modern version of Qt (which may require CMake). cmake.org does have 2.6.4 binaries for HP-UX: http://www.cmake.org/cmake/resources/software.html so hopefully that will be good enough. According to our CMakeList.txt it will be: ... project(Wireshark C CXX) cmake_minimum_required(VERSION 2.6) set(CMAKE_BACKWARDS_COMPATIBILITY 2.6) ... The HP-UX Porting and Archive Centre does have binaries of Wireshark; whether they'll stop doing so for 1.12 is another matter - hopefully, they won't. (I consider *all* currently-developed UN*Xes as platforms we should at least support to the extent of having third parties be able to package it. This is my point, too. I think our CMake build system is more future-proof and is easier to maintain than the autotools-based one. The only platforms I see us supporting *directly* are Windows and OS X, because I suspect only a minority of potential users of Wireshark would want to be forced to add on some Linux/BSD-style packaging system just to get Wireshark. Solaris, at least as of Solaris 11, has a Shiny New Packaging System built in, and has Wireshark in that packaging system; HP-UX has the Porting and Archive Centre, and they offer Wireshark and hopefully will continue to do so; AIX, there's The Written Word's packages.) I don't work with the mentioned systems, but I think the preferred way of installing programs is through packages and not compiling manually from source. Cheers, Balint ___ 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] 1.11.0 release
On Wed, Oct 09, 2013 at 03:15:41PM +0200, Bálint Réczey wrote: According to our CMakeList.txt it will be: ... project(Wireshark C CXX) cmake_minimum_required(VERSION 2.6) set(CMAKE_BACKWARDS_COMPATIBILITY 2.6) ... Unless you want to build with Qt5: http://qt-project.org/doc/qt-5.0/qtdoc/cmake-manual.html states: CMake is a 3rd party tool with its own documentation. The rest of this manual details the specifics of how to use Qt 5 with CMake. The minimum version required to use Qt5 is CMake 2.8.3, but 2.8.9 is recommended. So people who want a Qt5 version will not be happy with an old cmake. On the other hand: The setup script for macos has an option to add cmake to the list of tools/libs to download and build, so it isn't a really unusual situation and it isn't hard to handle either. Ciao Jörg -- Joerg Mayer jma...@loplof.de We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___ 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
[Wireshark-dev] 1.11.0 release
I've scheduled the release of 1.11.0 for next Tuesday, October 15. Corrections and additions for the release notes are welcome. Unfortunately the transitional state of our UI will be reflected in the release packages: Windows 32-bit: GTK3 and Qt Windows 64-bit: GTK2 and Qt OS X 64-bit: Qt OS X 32-bit: GTK2 Source: GTK3 Hopefully this won't cause too much confusion. I'll probably enable Qt by default in the sources in the next few days, so at least the Windows and source tarball will match. ___ 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
