Wireshark-dev: Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
From: Paul Offord <[email protected]>
Date: Fri, 5 Aug 2016 09:33:36 +0000

Hi Roland,

 

The dissector is called Syncro and it allows a remote process to access the WS plugin_if extensions through a TCP connection.  We wanted to be able to achieve this without building a custom version of WS and so built it as a dissector.  We don’t use any of the GUI stuff from Qt, just the TCP server functionality, multi-threading functions and Signals & Slots to communicate between threads.

 

Best regards…Paul

 

From: [email protected] [mailto:[email protected]] On Behalf Of Roland Knall
Sent: 05 August 2016 10:25
To: Developer support list for Wireshark <[email protected]>
Subject: Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies

 

Paul, could you give an example, why you chose Qt libraries over Gtk? Was it not possible, or is it a personal choice?

 

I do have plugins for WS, which use Qt, but not for dissectors, so I am just curious, what was missing.

 

regards

Roland

 

On Fri, Aug 5, 2016 at 11:20 AM, Graham Bloice <[email protected]> wrote:

On 5 August 2016 at 07:54, Paul Offord <[email protected]> wrote:

Hi,

 

I have written a plugin dissector that uses some Qt5 functions.  To build with Visual Studio 2013 I have to manually add some Qt5 libs via Project -> Properties -> Linker -> Input -> Additional Dependencies.  This works OK but whenever I run:

 

cmake -D ENABLE_CHM_GUIDES=on -G "Visual Studio 12 Win64" ..\

 

to prepare the environment the Qt5 additional Dependencies are deleted.  How can I add my additional libs to the Cmake process in a way that won’t interfere with the standard build process?  Or should I be doing this some completely different way?

 

Thanks and regards…Paul

 

 


Although I'm suspicious of why a dissector should need anything from Qt, have a look at the CMake wiki page for "Finding a library" at https://cmake.org/Wiki/CMake:How_To_Find_Libraries

 

Basically add the appropriate find_package(), include_directories() and target_link_libraries() calls to the CMakeLists.txt of your plugin for the QT library you want.

 

Note that this behaviour is by design, CMake generates the Visual Studio solutions and projects from the info in the CMakeLists.txt files, there is no way to make changes in the VS IDE and push them back into the CMakeLists.txt files (except if you open the file in the VS editor).

 

You might also have to add steps to the CMakeLists.txt to copy the required Qt DLL to the staging directory and the update the packaging scripts to put it into an installer (packaging\nsis\custom_plugins.txt).

 

--

Graham Bloice


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

 


______________________________________________________________________

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________