Wireshark mailing list archives
Why is building with libpcap optional?
From: Joerg Mayer <jmayer () loplof de>
Date: Mon, 17 Oct 2016 16:18:55 +0200
Hello, I tried to recall why building with libpcap is optional and failed. libpcap usage is deeply embedded into Wireshark and the resulting #ifdef/#ifndef HAVE_LIBPCAP shows: grep -r -E '#\s*if.*HAVE_LIBPCAP' . | wc -l 288 I'd really like to get rid of that and the "simplest" solution would be to require libpcap to be installed. I have some fallback ideas but would really like to use as simple a solution as possible. Thanks! Jörg -- Joerg Mayer <jmayer () loplof de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Why is building with libpcap optional? Joerg Mayer (Oct 17)
- Re: Why is building with libpcap optional? Guy Harris (Oct 17)