Maybe down in tools somewhere.
Ok, next week when you merge the two versions of packet-h225.c then we
checkin the changed packet-h225.c and the packet-h235* files.
Then we can also create a subdirectory down in tools for the per2ethereal
compiler
and another subdirectory below that where we store the h235 specific input
files and the generation script for the h235 stuff.
I noticed that you do a lot of #include "" of source files and definitions.
(i find #include's of code to be confusing)
Can the build script be changed to collapse all these things so that the
output is only one packet-h235.c and one packet-h235.h ?
Also add a GPL boilerplate on the output files under the comment that this
is a machinegenerated file.
----- Original Message -----
From: "Tomas Kukosa"
Sent: Friday, April 09, 2004 8:46 PM
Subject: Re: [Ethereal-dev] Fwd: H.235 protocol
> Ronnie Sahlberg wrote:
> > Can you regenerate it with a new version of packet-h225.c from CVS (you
will
> > need to remove some h235 stuff from the cvs version of h235)
> > or does the included packet-h225.c also include the changes to add the
> > missing h225 stuff like CryptoH323Token?
> Yes, it was necessary to add CryptoH323Token into packet-h225.c.
> I can look at it next week what is the best way for merging your and my
changes.
>
> > Does it dissect properly the recent ClearToken rescently sent to the
list?
> See attached ouptuts.
>
> What would be the best place in the CVS tree for the asn2eth.py compiler?
> Should we put into the CVS the PLY package too (two files lex.py, yacc.py)
or should we
> leave it "external" and each developer has to copy it himself?
>
>
