Package.dll and WPCAP.dll when using vcpkg

[Steve Chester]

Hello,

I've been researching using the PCAP++ library as a means to send and receive Ethernet frames within a windows application.  I have been using vcpkg as my package manager and was able to get everything up and running quite quickly following the tutorials.  However I ran into a hurdle where I could not discover any of my interface devices and after a bit of digging it appears to be from a mismatch in the packet.dll and wpcap.dll.  I had npcap and wireshark installed with this same dlls installed in my System32 directory.  If I deleted the ones in the output directory of my test project (the ones that came with vcpkg), then everything worked correctly.

Is there some configuration I can use to prevent the dlls from being included  and to use the system ones instead?  Is there some configuration I should be specifying that would make those dlls compatible?  My current solution to the problem is to have a post build script that deletes them, but I suspect there is a better way.

Cheers.

[Steve Chester]

Looks like this may be a known issue already:

https://github.com/seladb/PcapPlusPlus/issues/1176