/
README.win32
262 lines (178 loc) · 9.49 KB
/
README.win32
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
Information, Recommendations and Build Instructions for Windows
***************************************************************
_____________________________ IMPORTANT _______________________________
The execution of the currently shipped msvcbuild.bat batch script will
causes ANY subsequent none-MSVC build to fail. It has been wrongly set
up to copy several MSVC-specific header files from <libnet-root>/win32/
to <libnet-root>/include/ and <libnet-root>/include/libnet/ during the
build process. This is a high priority issue and will be taken care of
ASAP. If you ever have to make use of this file, consider compiling all
other builds from a separate tarball.
_______________________________________________________________________
This file list additional steps and suggestions for Windows users.
Please see INSTALL for a more general overview and doc/PORTED for
other platforms.
Unless you know what you are doing, you should follow the recommendations
below. Notice that there are plenty of other (sometimes better) ways
to build libnet, but these steps and suggestions are known to work.
If the build breaks, please re-read this guide carefully.
Contents
========
1. Introduction
1.1 Microsoft Visual C++ and GCC/MinGW
1.2 WinPcap/Npcap
1.3 Supported Operating Systems
2. MinGW Compiler
2.1 Native
2.2 Cross-Compiling
3. Microsoft Visual C++
1. Introduction
===============
1.1 Microsoft Visual C++ and GCC/MinGW
--------------------------------------
The Microsoft Visual C++ compiler (aka MSVC) and the GCC Windows port
(aka MinGW) are unfortunately not fully compatible. Although MSVC is a
great compiler, libnet has been developed with the GNU toolchain in mind.
So building libnet with the Visual C++ Build Tools will always have its
flaws, even while it might work in some points.
Most of libnet’s development is therefore done with GCC and its MinGW
Windows port.
In other words, if this this all new to you, I recommended you to use
MinGW for building libnet on Windows.
On the other hand, the two can work well together:
If you for instance build libnet with MinGW, and you want to use it
with MSVC too (or vice versa), you can use the DLL and the supplied
`libnet*.def` file located in <libnet-root>/win32/ (this file is always
rebuild at the end of every successful build on windows) to create an
MSVC compatible import library that you can use to link your projects
with without the need of rebuilding libnet again.
To produce a MinGW compatible import library from any libnet DLL:
dlltool -D path/to/libnet*.dll -d path/to/libnet*.def -l libnet.dll.a
To produce a MSVC compatible import library from any libnet DLL:
lib /machine:X64 /def:example.def
or
lib /machine:X86 /def:example.def
Note 1: If you have removed any or all symbol information from the DLL
(aka "stripped" it), during build, by for example running
configure with `--enable-fast`, then this obviously won't work.
1.2 WinPcap/Npcap
-----------------
Currently, the supported method of sending packets under Windows is with
WinPcap <http://www.winpcap.org>. However, libnet's support for Npcap
<http://www.npcap.org>, an update of WinPcap sponsored by the Nmap
Project, is being seriously considered.
> Windows users should know that with the switch to Npcap, WinPcap
> compatibility is expected to be deprecated.
Please be sure to install the WinPcap/Npcap driver/DLL and make sure
that the content of the Wpdpack's/Npcap SDK's Include and Lib directories
are somewhat reachable by your compiler.
Note 2: Remember that you cannot use MSVC-generated .lib files to create
shared libraries with MinGW, you have to use the lib*.a files.
WinPcap development came to a standstill before the Developer's
Pack ever provided x64 compatible lib*.a files for use with
MinGW/Cygwin. And since libnet depends on WinPcap, you would
have to compile 64-bit lib*.a libraries yourself if you want to
be able to produce 64-bit compatible libnet builds with
MinGW/Cygwin.
1.3 Supported Operating Systems
-------------------------------
At the latest with the switch to Npcap, libnet support for Windows XP,
Windows Server 2003 and earlier will be dropped.
I can think of too many better things to do than to continuously deal with
error handling and backwards compatibility (msvcrt vs crtdll) for EOL systems.
Remnants in the source suggests that building libnet with Cygwin must have
been possible at some point. This may or may not be the case these days.
If it still works or you get it to work (again), let us know.
2. MinGW Compiler
=================
Both native and cross compilation are possible, and there are quite a
few possibilities and options to choose from. If you just want to get
over with it, follow these steps:
Known traps are:
- Setting the wrong (or no) prefix. (important when running `make install`)
- Using incompatible WinPcap libraries for x64 (see Note 2)
- Not having said WinPcap libraries and header files in your compiler's path
Note 3: If you're building with MinGW, and want to install libnet to
your compiler's lib and include directories, you almost always
want to set the prefix manually. If you don't know what that
means, run `gcc -v`, look for `--prefix=/some/path` -- use that.
Note 4: If you're using a multilib MinGW-w64 GCC compiler, make sure to
add the `-m32` or `-m64` to `CFLAGS` to instruct the compiler to
build for your desired architecture.
2.1 Native
----------
The recommended MinGW distribution for building libnet is Msys2.
First, follow the installation instructions for Msys2 available at
<https://msys2.github.io>.
Second, install Wpdpack/Npcap SDK, as mentioned above.
Then, depending on your desired target architecture, open a mingw32 or
mingw64 shell, navigate to the source directory, and execute the
following commands:
If you want to produce 32 bit binaries:
CFLAGS="-Ipath/to/wpdpack/Include" LDFLAGS="-Lpath/to/wpdpack/Lib/" ./configure --prefix=/mingw64
If you want to produce 64 bit binaries:
CFLAGS="-Ipath/to/wpdpack/Include" LDFLAGS="-Lpath/to/wpdpack/Lib/x64" ./configure --prefix=/mingw64
Followed by:
make
sudo make install
2.2 Cross-Compiling
-------------------
During sample building, you may see a warning similar this:
Could not determine the host path corresponding to
... a path ...
Continuing, but uninstalled executables may not work.
This, among other things, means that the samples will depend on a shared
version of libgcc (aka `libgcc_s_sjlj-1.dll`). If no shared version of
libgcc was built when the compiler was configured, you most likely won't
be able to execute them.
In that case, your best bet is to link with the static version
of libgcc by disabling shared libraries altogether
./configure --disable-shared
In general, you should know what you're doing and what your host, target
and compiler are all about beforehand.
Remember, you still need the Wpdpack/Npcap `Lib` and `Include` files, as
mentioned above.
These steps have been successfully tested on Ubuntu and the default
mingw32-w32 toolchain (GCC 4.8). The recommended steps to build libnet
therefore are:
If you're targeting x86:
CFLAGS="-Ipath/to/wpdpack/Include" LDFLAGS="-Lpath/to/wpdpack/Lib" ./configure --host=i686-w64-mingw32 --prefix=/usr/i686-w64-mingw32
If you're targeting x64:
CFLAGS="-Ipath/to/wpdpack/Include" LDFLAGS="-Lpath/to/wpdpack/Lib/x64" ./configure --host=x86_64-w64-mingw32 --prefix=/usr/x86_64-w64-mingw32
Followed by:
make
sudo make install
Notice that the --host option is usually all you need for cross-compiling.
Note 5: Although the steps should be very similar, if you're using any
other distribution of MinGW (cross or native), you're pretty
much on your own. Suggestions, bug reports/fixes, and pull
requests, see: https://github.com/libnet/libnet/issues
3. Microsoft Visual C++
=======================
Known traps are:
- Not using the correct (x86 or x64) version of the Visual Studio command prompt
- Using incompatible WinPcap libraries for x64 (see Note 2)
- Not having said WinPcap libraries and header files in your compiler's path
Until the issue described at the top of this document is completely
resolved, MSVC support should be considered a work in progress and unsafe.
And that’s why I won't even go into it, and instead leave you with these
old but still perfectly fine instructions:
Run msvcbuild.bat to build for Win32 with MSVC
----------------------------------------------
The batch file takes arguments and sets the appropriate path and environment
variables for the desired built by running either vsvars32.bat (for x86),
vcvars64.bat (for x64) or vcvarsall.bat (for Cross development).
Type `msvcbuild.bat help` for a description of all available options.
If no argument is specified, x86 is assumed.
The batch file copies pre-prepared headers out of win32/, avoiding the
requirement for a gnu (Cygwin or MinGW) build environment.
The batch file hard-codes the location of the WinPcap developer's tools.
You may have to modify it for your environment, or install the developer's
pack in the expected location.
Although not required, it is advisable to execute the batch file from a
VS2015 Developer Command Prompt.
For Visual Studio 2015, the shell can be found at:
Program Files (x86) >> Microsoft Visual Studio 14.0 >> Common7 >> Tools >> VsDevCmd.bat
After building, libnet libraries and `.obj` files are found in newly created
`<libnet-root>\libnet\src\[Win32|Win64]\` `<libnet-root>\libnet\lib\[x86|x64]\`
respectively.