Thanks, that seems to have fixed it.
I’ve also fixed the link error by adding a #include <stdio.h> to the dissector. So I’ve got everything built.
One other question.
I have some other dissectors that used to live in their own directories in plugins. The changes to CMakeLists.txt seem to enforce these to be in a sub directory
of plugins. Is that right?
Regards
Andy Ling
From: Wireshark-dev [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx]
On Behalf Of Graham Bloice
Sent: Mon 21 May 2018 16:37
To: Developer support list for Wireshark
Subject: [External] Re: [Wireshark-dev] Problem building a dissector for 2.6
This Message originated outside your organization.
Hi,
I am trying to update to Wireshark 2.6 building for Windows 64bit. I have a custom GIOP dissector which was previously built for Wireshark 2.2.5
The dissector is in the file packet-q_quentin.c and I have copied that file to the epan/dissectors directory.
First, adding it to the CMakeListsCustom.txt file in epan/dissectors causes a build error – packet-q_quentin.c does not exist, except it does.
I have run cmake with a clean build directory and it still fails. So there seems to be a problem with the custom cmake list stuff.
Try prefixing your dissector with the cmake source path, e.g.
${CMAKE_CURRENT_SOURCE_DIR}/packet-q_quentin.c
Recent changes to the build infrastructure haven't updated the files not normally used in our builds, i.e. CMakeListsCustom.txt.example
To try and move on, I added my dissector to the CMakeLists.txt file. This now builds the dissector, but I get a link error saying unresolved symbol sprintf (which is used in my dissector).
I’m using Visual Studio 2015
So what do I need to do to make the custom cmake list work and how do I fix the link error.
Thanks for any help
Regards
Andy Ling
--
