Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Qt not found

From: Vishnu Bhatt <vishnu.bhatt@xxxxxxxxxxx>
Date: Tue, 9 Dec 2014 11:07:47 +0000

Thanks for the reply Pascal. So for now I am ignoring this warning but it would be a great help if you could please give a step by step procedure to make it working with Qt. I read the developers guide but am not clear on this one.

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Pascal Quantin
Sent: Tuesday, December 09, 2014 4:28 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Qt not found

 

2014-12-09 11:47 GMT+01:00 Vishnu Bhatt <vishnu.bhatt@xxxxxxxxxxx>:

Hello,

 

I am trying to build 1.12.2 on windows 7 machine (both 32-bit and 64-bit). I am getting the following warning:

 

nmake -f Makefile.nmake verify_tools

 

Can't find Qt. This will become a problem at some point.

 

What should be the solution to it?

 

Hi Vishnu,

as stated in the warning, it will be a problem *at some point* but we have not reached this point yet (Qt GUI is simply not mature in the 1.12 branch). So you can safely ignore this warning (even the official 1.12.2 does not bundle Qt GUI anymore) as it will not prevent to build the GTK UI and installer.
Maybe we should remove this warning in master-1.12 branch to avoid confusion.

Pascal.

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."