Yes,
and even better, have the first file (the dependencies) auto-generated
by parsing the variuous packet-xxx.c/.h and check for #includes of other
packet-xxx.h ?
But that is the easy part.
The difficult is that some of the wireshark core files and/or tap
listeners also depend on some of the packet-xxx.h files.
br,
Lars
Kukosa, Tomas wrote:
Hi,
what about having two new files?
One defining dependencies among dissectors and one where it would be
posiible to tell what dissectors should be included/excluded in
compilation.
Then some new tool (probably written in Python) would create list of
necessary files for compilation and linking.
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Lars Ruoff
Sent: Monday, February 12, 2007 4:32 PM
To: Wireshark-dev
Subject: [Wireshark-dev] Lightweigth tshark anybody?
Hi list!
I would like to compile my own light-weight version of tshark, with only
a minimum of protocols enabled (basically all i need is
Frame,etherent,IP,UDP/TCP,RTP,RTCP + some dependencies).
The goal is to substantially reduce the size of libwireshark.dll .
I remember running into dependency problems when i tried to kick out
some of the packet-xxx.c last time i tried that.
Anyone knows a way (or has it done already) to throw out unneccessary
stuff easily?
best regards,
Lars Ruoff
_______________________________________________
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
