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

I'm trying to add a custom plugin to a Wireshark built from source for Windows. The plugin has previously been successfully added to a Wireshark built from source for Linux, and the code has not been changed. I've gotten Wireshark to build successfully from source without adding the plugin, and have built it successfully with the plugin in the plugins folder but without any of the changes to add it as an extension.

When I change the custom.example files as directed in the README.plugins file, I immediately run into build errors. There are hundreds of compilation errors not in any of the source files, but in wireshark\epan\proto.h. They're all of the syntax error type, things like missing parenthesis and nonstandard extensions used. The plugin files compiled successfully for linux--why would they not work here? And why would the errors show up in epan\proto.h?

asked 19 Jan '15, 06:49

mehubb985's gravatar image

accept rate: 0%

It's possible the plugin includes header files only found on Linux, or includes something that then breaks subsequent includes, e.g. proto.h.

Redirect the build output to a file, e.g. nmake -f makefile.nmake > test.txt 2>&1 and look at the first errors found, you can post it here as a comment.

permanent link

answered 19 Jan '15, 09:03

grahamb's gravatar image

grahamb ♦
accept rate: 22%

Your answer
toggle preview

Follow this question

By Email:

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



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "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:


question asked: 19 Jan '15, 06:49

question was seen: 1,854 times

last updated: 19 Jan '15, 09:03

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