Re: [Wireshark-dev] Supported Python versions?

2015-03-26 Thread Christopher Maynard
Bálint Réczey writes: > Since we use Python with verified input and only for building > Wireshark the security concerns don't apply here. > Otherwise I think it would be OK to move to newer Python version. Not that we must, but maybe we could plan on bumping minimum required versions (Python, Qt

Re: [Wireshark-dev] CMake on Windows - Can build, but not run executable

2015-03-26 Thread Roland Knall
Hi The 32bit is not working either. I am not trying to upgrade my Qt version (although I really can't figure out what the issue should be here for tshark and wireshark-gtk, and if this is not working, I'll try your debug scenario. VS2013 is unfortunately not allowed in our company, not even the C

Re: [Wireshark-dev] CMake on Windows - Can build, but not run executable

2015-03-26 Thread Graham Bloice
I seem to remember earlier issues with other folks using VS2012 and wanting a 64 bit build, due to qt support problems. VS2013 CE is available for free, you might want to consider that. As for CMake build instructions did you look at README.cmake in the top level sources? When we get CMake total

Re: [Wireshark-dev] CMake on Windows - Can build, but not run executable

2015-03-26 Thread Roland Knall
Hi I have only VStudio 2012 available here at my workplace. Using CMake 3.0.2, msvc2012_64_opengl. The error log (in german) produces the following output: = Startet die Generierung des Aktivierungskontextes. Eingabeparameter: Flags = 0 ProcessorArchitecture = AMD64 CultureFallBa

Re: [Wireshark-dev] Supported Python versions?

2015-03-26 Thread Bálint Réczey
Hi Peter, 2015-03-24 18:17 GMT+01:00 Peter Wu : > On Sun, Mar 22, 2015 at 04:58:14PM +0100, Pascal Quantin wrote: >> 2015-03-22 16:48 GMT+01:00 Peter Wu : >> >> > Hi, >> > >> > Triggered by a build error due to html2text.py, I have recently started >> > with adding Python 3 support to various Pyth