![]() Put different types of plugins (libwiretap, libwireshark) in different subdirectories, give libwiretap and libwireshark init routines that load the plugins, and have them scan the appropriate subdirectories so that we don't even *try* to, for example, load libwireshark plugins in programs that only use libwiretap. Compiled plugins are stored in subfolders of the plugin folders, with the subfolder name being the Wireshark minor version number (X.Y). There is another hierarchical level for each Wireshark library (libwireshark, libwscodecs and libwiretap). The folder names are respectively plugins/X.Y/{epan,codecs,wiretap}. Currently we only distribute "epan" (libwireshark) plugins. Change-Id: I3438787a6f45820d64ba4ca91cbe3c8864708acb Reviewed-on: https://code.wireshark.org/review/23983 Petri-Dish: João Valverde <j@v6e.pt> Tested-by: Petri Dish Buildbot Reviewed-by: João Valverde <j@v6e.pt> |
||
---|---|---|
.. | ||
Makefile.am | ||
README | ||
configure.ac | ||
hello.c |
README
This is an example of how to build a Wireshark plugin out-of-tree. Tested on Linux using GCC 7. Note this builds against Wireshark's *installed* version. You should of course adapt to your own needs. To build/install the plugin: $ autoreconf -v -i $ PREFIX=/usr/local $ ./configure --prefix="$PREFIX" PKG_CONFIG_PATH="$PREFIX/lib/pkgconfig" $ make $ sudo make install # or single-user: make install-home