Force HAVE_REMOTE to be defined when including pcap.h with remote support.

WinPcap made the mistake of having stuff in its public header fines
depend on a configuration #define, HAVE_REMOTE; this means that we need
to forcibly define it when building with remote capture support.

The tip of the libpcap master branch does not have that botch; hopefully
future versions of libpcap-for-Windows will be based on that libpcap and
thus lack that botch as well.

Defining HAVE_REMOTE in config.h is not the right fix, as it makes it
look like a *Wireshark* configuration option that code in Wireshark
should test, rather than a *WinPcap* configuration option that the
pcap.h that ships with the WinPcap SDK should have been changed, as part
of the build process, to correctly define or not, so that users of
WinPcap don't have to define it themselves.

Change-Id: I62d1eca6d3c900d0dcc9fbc011db77f595a86313
Reviewed-on: https://code.wireshark.org/review/21593
Reviewed-by: Guy Harris <guy@alum.mit.edu>

1 files changed, 12 insertions, 0 deletions

diff --git a/extcap/androiddump.c b/extcap/androiddump.c
index d5a267e954..00cc0e03fb 100644
--- a/extcap/androiddump.c
+++ b/extcap/androiddump.c
@@ -65,6 +65,18 @@
 #define PCAP_RECORD_HEADER_LENGTH              16
 
 #ifdef ANDROIDDUMP_USE_LIBPCAP
+    #ifdef HAVE_PCAP_REMOTE
+    /*
+     * Force the WinPcap header files to define things required for remote
+     * capture.  (Yes, this is q WinPcap bug; if your project has a public
+     * header file that checks or otherwise uses a #define that's defined
+     * by your project's configuration process, and don't ensure that
+     * it's always defined appropriately when that header file is included,
+     * before its first use, you have made a mistake.)
+     */
+    #define HAVE_REMOTE
+    #endif
+
     #include <pcap.h>
     #include <pcap-bpf.h>
     #include <pcap/bluetooth.h>