Have scan_plugins() take an argument specify what to do on load failures.
authorGuy Harris <guy@alum.mit.edu>
Mon, 5 Sep 2016 23:26:29 +0000 (16:26 -0700)
committerGuy Harris <guy@alum.mit.edu>
Mon, 5 Sep 2016 23:27:02 +0000 (23:27 +0000)
commit2a38dc74ede3eba69f0d73b61f1735a4036528c1
treec03b1f72dcd66c54907d546a45c28315ba35fd27
parentae877942ea507128d3191e17075a26b86e52615d
Have scan_plugins() take an argument specify what to do on load failures.

That's a less gross hack to suppress load failures due to not having
libwiretap than providing a no-op failure-message routine, as it at
least allows other code using a failure-message routine, such as
cmdarg_err() and routines that call it, to be used.

We really should put libwiretap and libwireshark plugins into separate
subdirectories of the plugin directories, and avoid even looking at
libwireshark plugins in programs that don't use libwireshark.

Change-Id: I0a6ec01ecb4e718ed36233cfaf638a317f839a73
Reviewed-on: https://code.wireshark.org/review/17506
Reviewed-by: Guy Harris <guy@alum.mit.edu>
13 files changed:
capinfos.c
captype.c
dftest.c
editcap.c
mergecap.c
randpkt.c
reordercap.c
tfshark.c
tshark.c
ui/gtk/main.c
wireshark-qt.cpp
wsutil/plugins.c
wsutil/plugins.h