tcpdump mailing list archives

Re: [tcpdump] Keep win32/prj/WinDump.dsp ?


From: Francois-Xavier Le Bail via tcpdump-workers <tcpdump-workers () lists tcpdump org>
Date: Mon, 8 Jun 2020 21:24:34 +0200

--- Begin Message --- From: Francois-Xavier Le Bail <devel.fx.lebail () orange fr>
Date: Mon, 8 Jun 2020 21:24:34 +0200
On 25/05/2020 00:22, Guy Harris wrote:
On May 24, 2020, at 4:37 AM, Francois-Xavier Le Bail via tcpdump-workers <tcpdump-workers () lists tcpdump org> wrote:

15 printers are missing in win32/prj/WinDump.dsp.
Does anyone use it? Any reason to keep it ?

Note that the *supported* way to build tcpdump (and libpcap) on Windows is with CMake (which can more easily be kept 
up-to-date by UN*X users adding a new dissector than can Windows project files, and which are tested by the 
Travis/AppVeyor CI builds).  CMake can generate project files for several versions of Visual Studio, as well as build 
files for various other build systems.

See

      https://github.com/the-tcpdump-group/tcpdump/blob/master/doc/README.Win32.md

for information on building tcpdump on Windows with Visual Studio (and

      https://github.com/the-tcpdump-group/libpcap/blob/master/doc/README.Win32.md

for information on building libpcap on Windows with Visual Studio).

OK.

Thus all the files in win32/prj/ could be removed?
(WinDump.dsp  WinDump.dsw  WinDump.sln  WinDump.vcproj)

--- End Message ---
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Current thread: