Wireshark-dev: Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Graham Bloice <graham.bloice@xxxxxxxxxxxxx>
Date: Thu, 31 Jul 2014 22:19:27 +0100
On 31 July 2014 22:14, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:
On 31 July 2014 17:34, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:
On 7/31/14 6:08 AM, Graham Bloice wrote:
> On 31 July 2014 11:42, Bálint Réczey <balint@xxxxxxxxxxxxxxx
> <mailto:balint@xxxxxxxxxxxxxxx>> wrote:
>
>     +1 for dropping autotools in favor of CMake. CMake already covers all
>     my use cases.

Same here except for Windows. I've been doing most of my Qt development
using Qt Creator + CMake. It doesn't have all the conveniences of Qt
Creator + QMake but it works well enough.

>     I also support dropping nmake, but since I'm not building on Windows I
>     can't tell if CMake is complete enough.
>
> Not yet.  Working on it though.

I added "msbuild" steps to the Windows buildslaves after the "cmake"
steps. The 32-bit build succeeds although I haven't tried running it.
The 64-bit build passes /MACHINE:X86 to the linker which then fails.


The buildslaves are failing to build the solution.  I think the arguments to the msbuild step should be modified to be "msbuild" "/m" "/p:Configuration=RelWithDebInfo" "Wireshark.sln".



And the x86 buildslave CMake still isn't locating a viable Python Interpreter.



--
Graham Bloice