ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (developme

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Sat, 06 Oct 2012 14:40:59 -0700
It looks like it's possible to do this with qmake using a custom target,
at least according to this qt-interest mailing list post:
http://lists.trolltech.com/qt-interest/2008-01/thread00516-0.html

I added a similar target to QtShark.pro in r45356.

On 10/6/12 2:08 PM, Evan Huus wrote:
> This was caused by my removing the qm files in revision 45351. I
> believe the buildbot needs to be calling `lrelease QtShark.pro` to
> generate them before it calls `qmake QtShark.pro`?
> 
> Evan
> 
> On Sat, Oct 6, 2012 at 4:52 PM,  <buildbot-no-reply@xxxxxxxxxxxxx> wrote:
>> The Buildbot has detected a new failure on builder Ubuntu-12.04-x64 while building Wireshark (development).
>> Full details are available at:
>>  http://buildbot.wireshark.org/trunk/builders/Ubuntu-12.04-x64/builds/2091
>>
>> Buildbot URL: http://buildbot.wireshark.org/trunk/
>>
>> Buildslave for this Build: ubuntu-12.04-x64
>>
>> Build Reason: scheduler
>> Build Source Stamp: 45353
>> Blamelist: eapache
>>
>> BUILD FAILED: failed qt make
>>
>> sincerely,
>>  -The Buildbot
>>
>>
>>
>> ___________________________________________________________________________
>> Sent via:    Wireshark-commits mailing list <wireshark-commits@xxxxxxxxxxxxx>
>> Archives:    http://www.wireshark.org/lists/wireshark-commits
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits
>>              mailto:wireshark-commits-request@xxxxxxxxxxxxx?subject=unsubscribe
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>