Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 29-03-2016 21:46, Roland Knall wrote: Sorry, late over here. You could try with cmake 3.5rc2. But beside that, I did not get WS compile correctly with VS2013 for some time now, need to use VS2015 myself. Just another data point, I tried building on Windows 10 x64 with VS2015 and the

Re: [Wireshark-dev] #ifdef mess

On 29-03-2016 23:48, Joerg Mayer wrote: On Tue, Mar 29, 2016 at 03:34:38PM +0100, João Valverde wrote: On 28-03-2016 23:30, Joerg Mayer wrote: I've been meaning to write this mail for some years now but finally got around to it. Earlier today I committed

Re: [Wireshark-dev] #ifdef mess

On Tue, Mar 29, 2016 at 03:34:38PM +0100, João Valverde wrote: > On 28-03-2016 23:30, Joerg Mayer wrote: > >I've been meaning to write this mail for some years now but finally got > >around to it. > > > >Earlier today I committed 30900b443b85a7e760d703ca3d6efe61df4fe623, which I'm > >incredibly

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

Sorry, late over here. You could try with cmake 3.5rc2. But beside that, I did not get WS compile correctly with VS2013 for some time now, need to use VS2015 myself. regards Roland On Tue, Mar 29, 2016 at 10:04 PM, Michael Mann wrote: > It didn't generate one (otherwise I

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

It didn't generate one (otherwise I would have attached it). When it does, the output (like that below) would include a note about "See also CMakeError.log)" at the last line (right after line about CMakeOutput.log) -Original Message- From: Roland Knall To:

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

Take a look in your build directory, there must be a folder called CMakeFiles. In it, you'll find CMakeError.log. This file should contain, at it's bottom, the call which lead to the error and a more detailed error information in regard to the missing utility. regards Roland On Tue, Mar 29, 2016

[Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

I had gotten CMake to build on my setup a few months back, but it was a bit "quirky" (I had to keep deleting and regenerating the build directory because consecutive rebuilds would fail). I tried again with a more recent version of master (maybe a week old at this point) and can't seem to get

Re: [Wireshark-dev] #ifdef mess

On 28-03-2016 23:30, Joerg Mayer wrote: Hello list, I've been meaning to write this mail for some years now but finally got around to it. Earlier today I committed 30900b443b85a7e760d703ca3d6efe61df4fe623, which I'm incredibly unproud of because of readablity: static void

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

On 29 March 2016 at 15:04, Robert Cragie wrote: > I did the following: > > 1) Merged my fork with the latest upstream > 2) Downloaded and installed Qt > > I tried to rebuild using CMake but it still failed. Note the same code > builds fine using nmake and GTK only.

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

I did the following: 1) Merged my fork with the latest upstream 2) Downloaded and installed Qt I tried to rebuild using CMake but it still failed. Note the same code builds fine using nmake and GTK only. Here are the lines with FAILED and error in from the output of the build: 91>Done

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

It's a fork from 3771a79 with some custom changes. We tend to use the GTK version as it used to be more stable than the Qt version. I am not sure if that still is the case and I know GTK will be deprecated - is it at the point now where Qt version is better maintained, i.e. from the point of view

Re: [Wireshark-dev] #ifdef mess

On Tue, Mar 29, 2016 at 3:48 AM, Guy Harris wrote: > > which is a bit of a greasy hack - appending an empty string to str, just > so it's marked as used - but I suspect the extra CPU time spent doing that, > on platforms unlucky enough not to have zlib, will be lost in the