This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

I am finally able to build Wirshark 2.X. Now it absolutely refuses to find my dissector.

In the past I simply deleted register.c, added things to Makefile.Common and python magically created register.c with my dissector. That doesn't work anymore.

I'm doing my best not to go on a rant about the new build process.

Thanks, Brian

asked 22 Jan '16, 13:07

brwiese's gravatar image

brwiese
26111211
accept rate: 50%

Rather than rant, maybe let us know if there anything wrong with the documentation?

The Developers Guide section on Packet Dissection directs readers to README.dissector, and README.dissector Section 1.8 notes, as @Guy Harris answered, that a built-in dissector has to be added to epan/CMakeLists.txt.

(24 Jan '16, 07:29) grahamb ♦

To which "new build process" are you referring? Building with CMake? On UN*Xes, you can still use autotools rather than CMake; are you building on Windows?

If you're building with CMake, add your dissector to the DISSECTOR_SRC variable in epan/CMakeLists.txt; you'll need to put dissector/ in front of the name.

permanent link

answered 22 Jan '16, 13:32

Guy%20Harris's gravatar image

Guy Harris ♦♦
17.4k335196
accept rate: 19%

edited 22 Jan '16, 13:32

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×1,620
×637
×8
×3

question asked: 22 Jan '16, 13:07

question was seen: 972 times

last updated: 24 Jan '16, 07:29

p​o​w​e​r​e​d by O​S​Q​A