When you run make, a nifty Python script should generate a new
register.c containing your dissector.
Cheers
> -----Original Message-----
> From: ethereal-dev-bounces@xxxxxxxxxxxx
> [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Alex Kirk
> Sent: Monday, January 24, 2005 2:15 PM
> To: Ethereal development; Ulf Lamping
> Subject: Re: [Ethereal-dev] New Dissector: Dumb Question
>
>
>
> > That not sounds to bad for a first try, you've looked at the usual
> > suspects ;-)
> >
> > So your question isn't too dumb at all...
>
> Glad to hear it... :-)
>
> > If the register.c file doesn't contain your dissector, that's the
> > place
> > to look at first. Unless you build a plugin, it has to
> appear in that file.
> >
> > Did you place your dissector file in epan/dissectors? It won't be
> > searched somewhere else.
>
> Yes, I sure did. In fact, I was basing my dissector file
> partially on packet-msn-messenger.c, which I've made some
> improvements to (I'll be submitting them once I have the last
> bugs worked out there). The only difference is, that file was
> already all registered, so I didn't have that problem there.
>
> > Does it get (re-)compiled when you change your packet-wins.c (or
> > whatever name you'd chosen) file? So your makefile is ok.
>
> No, there's no re-compiliation when I make changes to this file.
>
> > Did you tried simply deleting the register.c file, as it's possibly
> > (re-)generated?
>
> I just did this (for the second time, just to make sure), and
> I'm still getting no results -- while packet-wins.c is in
> Makefile.common in epan/dissectors, my registration function
> is not added to register.c.
>
> I can attach Makefiles, the source file, whatever if it would
> be helpful; for now I'll not spam the list. :-)
>
> Alex Kirk
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ether> eal-dev
>
