Wireshark mailing list archives
Re: [External] Re: Problem building a dissector for 2.6
From: "Maynard, Chris" <Christopher.Maynard () IGT com>
Date: Tue, 22 May 2018 13:32:54 +0000
Yes, that’s the right place to put plugin dissectors now. In general, I think it’s a good idea to revisit your plugins whenever there’s a minor (or major) version update, because things often do change. I recommend a review and comparison of your files vs. those of a Wireshark-supplied plugin such as gryphon, since that’s the one referenced in doc/README.plugins. $ grep "gryphon epan" CMakeLists.txt add_plugin_library(gryphon epan) target_link_libraries(gryphon epan) install_plugin(gryphon epan) - Chris From: Wireshark-dev [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Andy Ling Sent: Tuesday, May 22, 2018 5:58 AM To: 'Developer support list for Wireshark' <wireshark-dev () wireshark org> Subject: Re: [Wireshark-dev] [External] Re: Problem building a dissector for 2.6 From: Wireshark-dev [mailto:wireshark-dev-bounces () wireshark org] 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 CONFIDENTIALITY NOTICE: This message is the property of International Game Technology PLC and/or its subsidiaries and may contain proprietary, confidential or trade secret information. This message is intended solely for the use of the addressee. If you are not the intended recipient and have received this message in error, please delete this message from your system. Any unauthorized reading, distribution, copying, or other use of this message or its attachments is strictly prohibited.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Problem building a dissector for 2.6 Andy Ling (May 21)
- Re: Problem building a dissector for 2.6 Graham Bloice (May 21)
- Re: [External] Re: Problem building a dissector for 2.6 Andy Ling (May 21)
- Re: [External] Re: Problem building a dissector for 2.6 Andy Ling (May 21)
- Re: [External] Re: Problem building a dissector for 2.6 Graham Bloice (May 21)
- Re: [External] Re: Problem building a dissector for 2.6 Andy Ling (May 21)
- Re: [External] Re: Problem building a dissector for 2.6 Maynard, Chris (May 21)
- Re: [External] Re: Problem building a dissector for 2.6 Andy Ling (May 22)
- Re: [External] Re: Problem building a dissector for 2.6 Maynard, Chris (May 22)
- Re: [External] Re: Problem building a dissector for 2.6 Andy Ling (May 21)
- Re: Problem building a dissector for 2.6 Graham Bloice (May 21)
- Re: [External] Re: Problem building a dissector for 2.6 Graham Bloice (May 21)