On Feb 12, 2013, at 5:47 AM, Clemens Gruber <[email protected]> wrote:
> (If pcap_dump_fopen had worked, I would have opened the handle myself
> with fsopen before giving it to WinPcap, but pcap_dump_fopen is not
> exported by the library.)
If you want pcap_dump_fopen() to work on Windows, you'll have to yell at
Microsoft, and get them to make the ABI of the C library invariant between
compiler releases, so that, for example, even if a given program is built with
one version of Visual C and WinPcap is built with another version, the format
of the "FILE" structure is the same in the program and in WinPcap.
> Also, would be
> nice if you could create a Github repository for the community. There we
> could simplify the process of sending in patches via pull requests and
> the issue tracker.
WinPcap is a port of libpcap, so the code in the libpcap source directory isn't
maintained independently; there's a GitHub repository for libpcap:
https://github.com/mcr/libpcap
Confusingly, it has an issue tracker, but there's also a SourceForge issue
tracker for it. I'll ask Michael Richardson whether we should move to using
the GitHub tracker or disable that tracker and send people to SourceForge.
Changes to libpcap won't necessarily immediately show up in a WinPcap release
(or even a libpcap release). I need to do some infrastructural work to libpcap
to make it easier to maintain WinPcap.
_______________________________________________
Winpcap-users mailing list
[email protected]
https://www.winpcap.org/mailman/listinfo/winpcap-users
