Hi,
See it as a tradeoff.
Option 1 is to add your dissector build in.
This means that you'll have to rebuild register.c and relink
libwireshark every time you change your dissector. With a ton of
dissectors this takes a while.
Option 2 is to add your dissector as a plugin.
This takes some work
___
> Date: Tue, 6 Nov 2007 11:42:14 -0800
> From: [EMAIL PROTECTED]
> To: wireshark-dev@wireshark.org
> Subject: [Wireshark-dev] what are the steps needed to add a plugin
>
>
>
> Greeting folks,
>
> I am a newbie to the wireshark deve
Hello,
I have written 2 plugins and I did exactly the same way twice.
I don't think there is another possibility.
Pascal
Date: Tue, 6 Nov 2007 11:42:14 -0800
From: [EMAIL PROTECTED]
To: wireshark-dev@wireshark.org
Subject: [Wireshark-dev] what are the steps needed to add a plugin
Gre
On Tue, Nov 06, 2007 at 11:42:14AM -0800, jaydeep chokshi wrote:
> I am a newbie to the wireshark development. I created a plugin *foo
> *(in Linux) that comes into action after Ethernet header has been
> dissected.
>
> In order to compile wireshark with the plugin, I had to make following
> addi
Greeting folks,
I am a newbie to the wireshark development. I created a plugin *foo *(in
Linux) that comes into action after Ethernet header has been dissected.
In order to compile wireshark with the plugin, I had to make following
additions/changes,
1. In the *foo* directory,
1.1 Edit Makefil
