["Steve Grinwis" <sgrinwis@xxxxxxx>]

Yes.  It's a sparse file with two lines of working code.  I did notice
however that I don't have a Makefile.am or Makefile.in.  Is that
important?  I'm compiling on Windows

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jaap Keuter
Sent: Tuesday, July 25, 2006 10:07 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Ethereal to Wireshark issues

Hi,

Did you add a correctly filled in makefile.common as well?

Thanx,
Jaap

On Tue, 25 Jul 2006, Steve Grinwis wrote:

> My makefile didn't have any of the python plugin.c stuff.  I
essentially
> copied the sbus makefile and pasted it overtop of mine  I did notice
> that I had to manually add all of the *.obj files to the objects list
> myself or it wouldn't compile correctly meaning that the line:
>
> DISSECTOR_OBJECTS = $(DISSECTOR_SRC:.c=.obj)
>
> Wasn't working as advertised.
>
> I can put a different plugin in myself and it will work fine.  My
> registration routines are similar to the ones I looked at.  Anyone
have
> any ideas?  Or am I on my own with this?
>
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jaap Keuter
> Sent: Tuesday, July 25, 2006 9:34 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Ethereal to Wireshark issues
>
> Hi,
>
> It would be a good idea to compare a makefile from a plugin from the
> distribution to the makefile of your plugin. It shows you the
> differences.
>
> Thanx,
> Jaap
>
> On Tue, 25 Jul 2006, Steve Grinwis wrote:
>
> > I modified the makefile by hand.  Esentially all I did was remove
all
> > instances of Ethereal and replaced it with Wireshark.  Is there more
> to
> > do?
> >
> > -----Original Message-----
> > From: wireshark-dev-bounces@xxxxxxxxxxxxx
> > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jaap
Keuter
> > Sent: Tuesday, July 25, 2006 9:22 AM
> > To: Developer support list for Wireshark
> > Subject: Re: [Wireshark-dev] Ethereal to Wireshark issues
> >
> > Hi,
> >
> > Did you modify the plugins'  makefile to match the current plugin
> build
> > method?
> >
> > Thanx,
> > Jaap
> >
> > On Tue, 25 Jul 2006, Steve Grinwis wrote:
> >
> > > Yes.  I built Wireshark from source, so that I know that my build
> > > environment is sane, then built my plug-in.
> > >
> > >
> > > -----Original Message-----
> > > From: wireshark-dev-bounces@xxxxxxxxxxxxx
> > > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jaap
> Keuter
> > > Sent: Tuesday, July 25, 2006 4:53 AM
> > > To: Developer support list for Wireshark
> > > Subject: Re: [Wireshark-dev] Ethereal to Wireshark issues
> > >
> > > Hi,
> > >
> > > Did you recompile them? See http://wiki.wireshark.org/KnownBugs
> under
> > > the
> > > header "Not a Bug"
> > >
> > > Thanx,
> > > Jaap
> > >
> > > On Mon, 24 Jul 2006, Steve Grinwis wrote:
> > >
> > > >
> > > > Hi,
> > > >
> > > > I'm still having issues with getting my plug-in, which worked
fine
> > > with
> > > > Ethereal, to work with Wireshark.  I keep getting the error
> > > > "Couldn't load module (path)\xxxx.dll:  The specified module
could
> > not
> > > > be found.
> > > >
> > > > The only thing I can think of is that there was no
> "plugins\0.99.2"
> > > > directory. So I made it myself and put my plug-in inside it.
> > > >
> > > > Does that make sense?  Any potential ID10T errors to watch out
for
> > > with
> > > > this kind of thing?  I've been pounding away at this for like 2
> days
> > > on
> > > > and off, and nothing so far.
> > > >
> > > > Thanks
> > > >
> > > > Steve
> > >
> > > _______________________________________________
> > > Wireshark-dev mailing list
> > > Wireshark-dev@xxxxxxxxxxxxx
> > > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > This transmission (including any attachments) may contain
> confidential
> > information, privileged material (including material protected by
the
> > solicitor-client or other applicable privileges), or constitute
> > non-public information. Any use of this information by anyone other
> than
> > the intended recipient is prohibited. If you have received this
> > transmission in error, please immediately reply to the sender and
> delete
> > this information from your system. Use, dissemination, distribution,
> or
> > reproduction of this transmission by unintended recipients is not
> > authorized and may be unlawful.
> > > _______________________________________________
> > > Wireshark-dev mailing list
> > > Wireshark-dev@xxxxxxxxxxxxx
> > > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> > >
> >
> > _______________________________________________
> > Wireshark-dev mailing list
> > Wireshark-dev@xxxxxxxxxxxxx
> > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> >
> >
> >
> >
---------------------------------------------------------------------
> > This transmission (including any attachments) may contain
confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute
> non-public information. Any use of this information by anyone other
than
> the intended recipient is prohibited. If you have received this
> transmission in error, please immediately reply to the sender and
delete
> this information from your system. Use, dissemination, distribution,
or
> reproduction of this transmission by unintended recipients is not
> authorized and may be unlawful.
> > _______________________________________________
> > Wireshark-dev mailing list
> > Wireshark-dev@xxxxxxxxxxxxx
> > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> >
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public information. Any use of this information by anyone other than
the intended recipient is prohibited. If you have received this
transmission in error, please immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful.
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.