Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (developme
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Evan Huus <eapache@xxxxxxxxx>
Date: Mon, 9 Sep 2013 22:30:02 -0400
On 2013-09-09, at 10:20 PM, Guy Harris <guy@xxxxxxxxxxxx> wrote:

> 
> On Sep 9, 2013, at 1:20 PM, buildbot-no-reply@xxxxxxxxxxxxx wrote:
> 
>> The Buildbot has detected a new failure on builder Windows-7-x64 while building Wireshark (development).
>> Full details are available at:
>> http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/7000
>> 
>> Buildbot URL: http://buildbot.wireshark.org/trunk/
>> 
>> Buildslave for this Build: windows-7-x64
>> 
>> Build Reason: scheduler
>> Build Source Stamp: 51888
>> Blamelist: alagoutte,cmaynard,jmayer
>> 
>> BUILD FAILED: failed nmake all
> 
> I give up.
> 
> It appears not to be finding <gcrypt.h>.
> 
> I suspect the problem is that qmake isn't telling the Windows C compiler where to find the libgcrypt header files.
> 
> I tried checking in something to ui/qt/QtShark.pro to make it do so, but I guess it needs MOAR CHANGES to work.
> 
> (I am *so* glad we can build the Qt versions on UN*X with the autotools and, I think, CMake.)

I am becoming more convinced that Joerg's plan to cmake-all-the-things is a good one. This is reaching unmanageability of epic proportions.