Wireshark · Wireshark-dev: Re: [Wireshark-dev] [External] Re: Problem building a dissector for 2.6

[Andy Ling <Andy.Ling@xxxxxxxxx>]

 

 

From: Wireshark-dev [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Maynard, Chris
Sent: Mon 21 May 2018 20:41
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] [External] Re: Problem building a dissector for 2.6

---

You could also try explicitly building the documentation, i.e., with all_guides.vcxproj

 

 

I thought I didn’t have that file, but found it in docbook.

 

Installing Asciidoctorj has fixed the problem. Thanks.

 

If you didn’t install asciidoctorj, then it might be worth re-reading Section 2.2, “Win32/64: Step-by-step Guide”, from the Wireshark Developer’s Guide (https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html); asciidoctorj is mentioned in section 2.2.8.

 

 

Yes, I missed that bit. It wasn’t needed in the version I last built.

 

Regarding custom_plugins.txt, you’re almost right.  The example should read:

 

;File "${STAGING_DIR}\plugins\${VERSION_MAJOR}.${VERSION_MINOR}\epan\foo.dll"

 

 

Assuming the plugins are in the epan directory. Is that the “right” place to put them? As I said previously, they seem to have to be in a sub-directory as the CMakeLists.txt format seems to insist e.g for my cnad plugin.

 

add_plugin_library(cnad epan)

 

target_link_libraries(cnad epan)

 

install_plugin(cnad epan)

 

 

Thanks for the help

 

Andy Ling

 

---

This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com

---