Lines Matching +full:cmake +full:- +full:windows

1 Building tcpdump on Windows with Visual Studio
4 Unlike the UN*Xes on which libpcap can capture network traffic, Windows
15 ---------------------
26 such as a requirement to support versions of Windows earlier than
27 Windows Vista, which is the earliest version supported by Npcap.
31 `C:\npcap-sdk`, and put the contents of the ZIP archive into that folder.
39 --------------------
44 Building tcpdump on Windows requires Visual Studio 2015 or later.  The
49 Windows with which those tools, and other tools, can be installed; it
52 It is a command-line tool; a GUI tool, Chocolatey GUI, is provided as a
59 For convenience, the `choco install` command can be run with the `-y`
64 choco install -y chocolateygui
69 ### CMake ###  subsection
74 It does provide files for CMake, which is a cross-platform tool that
75 runs on UN\*Xes and on Windows and that can generate project files for
79 Visual Studio 2015 does not provide CMake; an installer can be
80 downloaded from [here](https://cmake.org/download/).
82 When you run the installer, you should choose to add CMake to the system
85 CMake can also be installed as the Chocolatey package `cmake`:
88 choco install -y cmake
91 Visual Studio 2017 and later provide CMake, so you will not need to
92 install CMake if you have installed Visual Studio 2017 or later.  They
93 include built-in support for CMake-based projects as described
94 [here](https://devblogs.microsoft.com/cppblog/cmake-support-in-visual-studio/).
96 For Visual Studio 2017, make sure "Visual C++ tools for CMake" is
97 installed; for Visual Studio 2019, make sure "C++ CMake tools for
98 Windows" is installed.
101 ---
105 provided as an optional installation component, "Git for Windows", with
109 -----------------------------------
114 Visual Studio will run CMake; however, you will need to indicate where
117 To do this, go to Project > "Change CMake Settings" > tcpdump and:
125 -DPCAP_ROOT={path-to-sdk}
128 where `{path-to-sdk}` is the path of the directory containing the Npcap or
133 with Control-S.
135 Visual Studio will then re-run CMake.  If that completes without errors,
136 you can build with CMake > "Build All".
141 Visual Studio will run CMake; however, you will need to indicate where
144 To do this, go to Project > "CMake Settings for tcpdump" and:
149 Scroll down to "Cmake variables and cache", scroll through the list
155 with Control-S.
157 Visual Studio will then re-run CMake.  If that completes without errors,
161 ------------------------------
174 cmake "-DPCAP_ROOT={path-to-sdk}" -G {generator} {path-to-tcpdump-source}
177 `{path-to-sdk}` is the path of the directory containing the Npcap or
180 `{generator}` is the string "Visual Studio 15 2017" to build a 32-bit
182 a 64-bit version of tcpdump.
184 `{path-to-tcpdump-source}` is the pathname of the top-level source
206 cmake "-DPCAP_ROOT={path-to-sdk}" -G "Visual Studio 16 2019" {platform} {path-to-tcpdump-source}
209 `{path-to-sdk}` is the path of the directory containing the Npcap or
212 `{platform}` is `-A Win32` to build a 32-bit version of tcpdump or `-A
213 x64` to build a 64-bit version of tcpdump.
215 `{path-to-tcpdump-source}` is the pathname of the top-level source
227 -------------------
229 (XXX - this should be added)