Wireshark · Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 27500: /trunk/ /trunk/epan/dissectors/: Makefile.common

[Jaap Keuter <jaap.keuter@xxxxxxxxx>]

Hi,

It is of little use to keep single file dissectors as plugins. Also little or no 
development is going into these. In order to cut down the number of plugins 
these are incorporated into the build in collection.
What is left is:
1. gryphon, as the most senior plugin providing an example for new developers.
   It is referenced in doc/README.plugins.
2. Multiple file dissector plugins (like profinet) are left as they are, since
   the explicit collection of relevant source files has its pros.

Thanx,
Jaap

Ulf Lamping wrote:
> jake@xxxxxxxxxxxxx schrieb:
> > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=27500
> >
> > User: jake
> > Date: 2009/02/22 02:05 AM
> >
> > Log:
> >  Incorporate plugin dissector into build in collection.
> >
> > Directory: /trunk/epan/dissectors/
> >   Changes    Path               Action
> >   +2 -0      Makefile.common    Modified
> >   +792 -0    packet-opsi.c      Added
> >   +129 -0    packet-opsi.h      Added
> >
> > Directory: /trunk/packaging/nsis/
> >   Changes    Path              Action
> >   +0 -1      Makefile.nmake    Modified
> >   +0 -1      wireshark.nsi     Modified
> >
> > Directory: /trunk/plugins/
> >   Changes    Path              Action
> >   +0 -1      Makefile.am       Modified
> >   +0 -4      Makefile.nmake    Modified
> >
> > Directory: /trunk/
> >   Changes    Path            Action
> >   +0 -1      Makefile.am     Modified
> >   +0 -1      configure.in    Modified
>
> Just out of interest: Is there a specific reason to incorporate the 
> dissectors?
>
> BTW: Could you keep the PROFINET dissector as a plugin?
>
> Regards, ULFL