/usr/share/doc/wireshark-doc/wsdg_html_chunked/ChToolsMSChain.html is in wireshark-doc 1.10.6-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>4.4. Microsoft compiler toolchain (Win32 native)</title><link rel="stylesheet" type="text/css" href="ws.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Wireshark Developer's Guide"><link rel="up" href="ChapterTools.html" title="Chapter 4. Tool Reference"><link rel="prev" href="ChToolsGNUChain.html" title="4.3. GNU compiler toolchain (UNIX or Win32 Cygwin)"><link rel="next" href="ChToolsBash.html" title="4.5. bash"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4.4. Microsoft compiler toolchain (Win32 native)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ChToolsGNUChain.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Tool Reference</th><td width="20%" align="right"> <a accesskey="n" href="ChToolsBash.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ChToolsMSChain"></a>4.4. Microsoft compiler toolchain (Win32 native)</h2></div></div></div><p>To compile Wireshark on Windows using the Microsoft C/C++
compiler, you'll need:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>C compiler (<code class="filename">cl.exe</code>)</p></li><li class="listitem"><p>Assembler (<code class="filename">ml.exe</code> for 32-bit targets
and <code class="filename">ml64.exe</code> for 64-bit targets)</p></li><li class="listitem"><p>Linker (<code class="filename">link.exe</code>)</p></li><li class="listitem"><p>Make (<code class="filename">nmake.exe</code>)</p></li><li class="listitem"><p>C runtime headers and libraries (e.g. <code class="filename">stdio.h,
msvcrt.lib</code>)</p></li><li class="listitem"><p>Windows platform headers and libraries (e.g.
<code class="filename">windows.h, WSock32.lib</code>)</p></li><li class="listitem"><p>HTML help headers and libraries (<code class="filename">htmlhelp.h,
htmlhelp.lib</code>)</p></li></ol></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp22036452"></a>4.4.1. Toolchain Package Alternatives</h3></div></div></div><p>
The official Wireshark 1.8.x releases are compiled using
Microsoft Visual C++ 2010 SP1.
The official 1.2, 1.4, and 1.6 releases are and were compiled using
Microsoft Visual C++ 2008 SP1.
Other past releases, including the 1.0 branch,
were compiled using Microsoft Visual C++ 6.0. Using the release
compilers is recommended for Wireshark development work. "Express
Edition" compilers such as Visual C++ 2010 Express Edition SP1 can be
used but any PortableApps or U3 packages you create with them
will require the installation of a separate Visual C++
Redistributable package on any machine on which the PortableApps
or U3 package is to be used. See
<span class="quote">“<span class="quote"><a class="link" href="ChToolsMSChain.html#msvc-runtime-redistributable" title='4.4.6. C-Runtime "Redistributable" Files'>C-Runtime "Redistributable" Files</a></span>”</span>
below for more details.
</p><p>
However, you might already have a different Microsoft C++ compiler
installed. It should be possible to use any of the following with the considerations listed:
</p><div class="informaltable"><table border="1"><colgroup><col class="compiler_package"><col class="ide_debugger"><col class="publicly_available"><col class="sdk_required"><col class="msvc_variant"><col class="bitwidth"><col class="vcvars_bat"><col class="remarks"></colgroup><tbody><tr><td>
<p>Compiler Package</p>
</td><td>
<p>IDE / Debugger?</p>
</td><td>
<p>Publicly available?</p>
</td><td>
<p>SDK required?</p>
</td><td>
<p>config.nmake:</p>
<p>MSVC_VARIANT</p>
</td><td>
<p>32-bit/64-bit</p>
</td><td>
<p>set compiler PATH and alike settings
with:</p>
</td><td>
<p>Remarks</p>
</td></tr><tr><td>
<p>Visual Studio 2005</p>
</td><td>
<p>Yes</p>
</td><td>
<p>Commercial
<sup>1</sup></p>
</td><td>
<p>No
<sup>2</sup></p>
</td><td>
<p>MSVC2005</p>
</td><td>
<p>32-bit only</p>
</td><td>
<p>Microsoft Visual Studio
8\VC\bin\vcvars32.bat</p>
</td><td>
<p>-</p>
</td></tr><tr><td>
<p>Visual C++ 2005 Express Edition</p>
</td><td>
<p>Yes</p>
</td><td>
<p>
Free Download (link disappeared)
</p>
</td><td>
<p>
Free Download (link disappeared)
</p>
</td><td>
<p>MSVC2005EE</p>
</td><td>
<p>32-bit only</p>
</td><td>
<p>Microsoft Visual Studio
8\VC\bin\vcvars32.bat</p>
</td><td>
<p>
<code class="filename">vcredist_x86.exe</code>
<sup>4</sup>
</p>
</td></tr><tr><td>
<p>Visual Studio 2008</p>
</td><td>
<p>Yes</p>
</td><td>
<p>Commercial</p>
</td><td>
<p>No
<sup>2</sup></p>
</td><td>
<p>MSVC2008</p>
</td><td>
<p>32-bit only?</p>
</td><td>
<p>Microsoft Visual Studio
9.0\VC\bin\vcvars32.bat</p>
</td><td>
<p>-</p>
</td></tr><tr><td>
<p>Visual C++ 2008 Express Edition SP1</p>
</td><td>
<p>Yes</p>
</td><td>
<p>
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=14597" target="_top">
Free Download</a></p>
</td><td>
<p>No
<sup>2</sup></p>
</td><td>
<p>MSVC2008EE</p>
</td><td>
<p>32-bit only?</p>
</td><td>
<p>Microsoft Visual Studio
9.0\VC\bin\vcvars32.bat</p>
</td><td>
<p>
<code class="filename">vcredist_x86.exe</code>
<sup>4</sup>
</p>
</td></tr><tr><td rowspan="2" valign="middle">
<p>Visual Studio 2010</p>
</td><td rowspan="2" valign="middle">
<p>Yes</p>
</td><td rowspan="2" valign="middle">
<p>Commercial</p>
</td><td rowspan="2" valign="middle">
<p>No
<sup>2</sup></p>
</td><td rowspan="2" valign="middle">
<p>MSVC2010</p>
</td><td>
<p>32-bit</p>
</td><td>
<p>Microsoft Visual Studio
10.0\VC\vcvarsall.bat x86</p>
</td><td rowspan="2" valign="middle">
<p>-</p>
</td></tr><tr><td>
<p>64-bit</p>
</td><td>
<p>Microsoft Visual Studio
10.0\VC\vcvarsall.bat x64</p>
</td></tr><tr><td rowspan="2" valign="middle">
<p>Visual C++ 2010 Express Edition</p>
<p>(recommended)</p>
</td><td rowspan="2" valign="middle">
<p>Yes</p>
</td><td rowspan="2" valign="middle">
<p>
<a class="ulink" href="http://www.microsoft.com/express/Downloads/#Visual_Studio_2010_Express_Downloads" target="_top">
Free Download</a></p>
</td><td>
<p>No
<sup>2</sup></p>
</td><td rowspan="2" valign="middle">
<p>MSVC2010EE</p>
</td><td>
<p>32-bit</p>
</td><td>
<p>Microsoft Visual Studio
10.0\VC\vcvarsall.bat x86</p>
</td><td>
<p>
<code class="filename">vcredist_x86.exe</code>
<sup>4</sup>
</p>
</td></tr><tr><td>
<p>Yes
<sup>3</sup></p>
</td><td>
<p>64-bit</p>
</td><td>
<p>Microsoft Visual Studio
10.0\VC\vcvarsall.bat x64</p>
</td><td>
<p>
<code class="filename">vcredist_x64.exe</code>
<sup>4</sup>
</p>
</td></tr><tr><td>
<p>.NET Framework 2.0 SDK
<sup>5</sup></p>
</td><td>
<p>No</p>
</td><td>
<p>
Free Download (link disappeared)
</p>
</td><td>
<p>
Free Download (link disappeared)
</p>
</td><td>
<p>DOTNET20</p>
</td><td>
<p>32-bit only?</p>
</td><td>
<p>Microsoft.NET\SDK\v2.0\Bin\sdkvars.bat</p>
</td><td>
<p>
<code class="filename">vcredist_x86.exe</code>
<sup>4</sup>
</p>
</td></tr></tbody></table></div><p>
<sup>1</sup>no longer officially available,
might still be available through the MSDN
subscriptions
</p><p>
<sup>2</sup>as the SDK is already
integrated in the package, you obviously don't need to
install it and don't even need to call a separate environment
setting batch file for the SDK!
</p><p>
<sup>3</sup>the Express Edition does not include
compilers or assemblers that can generate 64-bit code; those are
only included in the SDK
</p><p>
<sup>4</sup><code class="filename">vcredist_x86.exe</code>
(3MB free download) is required to build
<code class="filename">Wireshark-win32-1.10.x.exe</code>,
and <code class="filename">vcredist_x64.exe</code> is required to build
<code class="filename">Wireshark-win64-1.10.x.exe</code>,
The version of <code class="filename">vcredist_x86.exe</code> or
<code class="filename">vcredist_x64.exe</code> <span class="emphasis"><em>must</em></span>
match the version for your compiler, including any service packs
installed for the compiler.
</p><p>
<sup>5</sup>MSDN remarks that the
corresponding .NET runtime is required. It's currently
unclear if the runtime needs to be installed for the C
compiler to work - or is this only needed to compile / run
.NET programs?!?
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp22084932"></a>4.4.2. Legal issues with MSVC > V6?</h3></div></div></div><p>Please note: The following is not legal advice - ask
your preferred lawyer instead! It's the authors view, but
this view might be wrong!</p><p>The myriad of
<a class="ulink" href="http://anonsvn.wireshark.org/wireshark-win32-libs/tags/" target="_top">
Win32 support lib</a> port projects all seem to believe
there are legal issues involved in using newer versions of
Visual Studio. This FUD essentially stems from two
misconceptions:</p><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Unfortunately, it is believed by many that the
Microsoft Visual Studio 2003 EULA explicitly forbids
linking with GPL'ed programs. This belief is probably due
to an improper interpretation of the
<a class="ulink" href="http://msdn.microsoft.com/visualc/vctoolkit2003/eula.aspx" target="_top">
Visual Studio 2003 Toolkit EULA</a>, which places
redistribution restrictions only on SOURCE CODE SAMPLES
which accompany the toolkit.</p></li><li class="listitem"><p>Other maintainers believe that the GPL itself
forbids using Visual Studio 2003, since one of the
required support libraries (MSVCR71.DLL) does not ship
with the Windows operating system. This is also a
wrongful interpretation, and the
<a class="ulink" href="http://www.gnu.org/licenses/gpl-faq.html#WindowsRuntimeAndGPL" target="_top">
GPL FAQ</a> explicitly addresses this issue.</p></li></ol></div><p>Similar applies to Visual Studio 2005 and
alike.</p><p>So in effect it should be perfectly legal to compile
Wireshark and distribute / run it if it was compiled with any
MSVC version > V6!</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp22089772"></a>4.4.3. cl.exe (C Compiler)</h3></div></div></div><p>The following table gives an overview of the possible
Microsoft toolchain variants and their specific C compiler
versions "ordered by release date":</p><div class="informaltable"><table border="1"><colgroup><col class="c1"><col class="c2"><col class="c3"><col class="c4"></colgroup><tbody><tr><td>
<p>Compiler Package</p>
</td><td>
<p>cl.exe</p>
</td><td>
<p>_MSC_VER</p>
</td><td>
<p>CRT DLL</p>
</td></tr><tr><td>
<p>Visual Studio 2005</p>
</td><td rowspan="4" align="center" valign="middle">
<p>8.0</p>
</td><td rowspan="4" align="center" valign="middle">
<p>1400</p>
</td><td rowspan="4" align="center" valign="middle">
<p>msvcr80.dll</p>
</td></tr><tr><td>
<p>Visual C++ 2005 Express Edition</p>
</td></tr><tr><td>
<p>.NET Framework 2.0 SDK</p>
</td></tr><tr><td>
<p>Windows SDK for Windows Vista and
.NET Framework 3.0 Runtime Components</p>
</td></tr><tr><td>
<p>Visual Studio 2008</p>
</td><td rowspan="2" align="center" valign="middle">
<p>9.0</p>
</td><td rowspan="2" align="center" valign="middle">
<p>1500</p>
</td><td rowspan="2" align="center" valign="middle">
<p>msvcr90.dll</p>
</td></tr><tr><td>
<p>Visual Studio 2008 Express Edition</p>
</td></tr><tr><td>
<p>Visual Studio 2010</p>
</td><td rowspan="2" align="center" valign="middle">
<p>10.0</p>
</td><td rowspan="2" align="center" valign="middle">
<p>1600</p>
</td><td rowspan="2" align="center" valign="middle">
<p>msvcr100.dll</p>
</td></tr><tr><td>
<p>Visual Studio 2010 Express Edition</p>
</td></tr></tbody></table></div><p>After correct installation of the toolchain, typing
at the command line prompt (cmd.exe):</p><p>
<code class="prompt">></code>
<strong class="userinput"><code>cl</code></strong>
</p><p>should result in something like:
</p><pre class="programlisting">
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86
Copyright (C) Microsoft Corp. All rights reserved.
usage: cl [ option... ] filename... [ /link linkoption...
</pre><p>However, the version string may vary.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChToolsNMake"></a>4.4.4. nmake.exe (Make)</h3></div></div></div><p>nmake is part of the toolchain packages described
above.</p><p>Instead of using the workspace (.dsw) and projects
(.dsp) files, the traditional nmake makefiles are used. This
has one main reason: it makes it much easier to maintain
changes simultaneously with the GCC toolchain makefile.am files
as both file formats are similar. However, as no Visual
Studio workspace/project files are available, this makes it
hard to use the Visual Studio IDE e.g. for using the
integrated debugging feature.</p><p>After correct installation, typing at the command
line prompt (cmd.exe):</p><p>
<code class="prompt">></code>
<strong class="userinput"><code>nmake</code></strong>
</p><p>should result in something like:
</p><pre class="programlisting">
Microsoft (R) Program Maintenance Utility Version 6.00.9782.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
NMAKE : fatal error U1064: MAKEFILE not found and no target specified
Stop.
</pre><p>However, the version string may vary.</p><p>Documentation on nmake can be found at
<a class="ulink" href="http://msdn2.microsoft.com/library/dd9y37ha(VS.71).aspx" target="_top">
Microsoft MSDN</a></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp22111876"></a>4.4.5. link.exe (Linker)</h3></div></div></div><p>XXX - add info here</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="msvc-runtime-redistributable"></a>4.4.6. C-Runtime "Redistributable" Files</h3></div></div></div><p>Please note: The following is not legal advice - ask
your preferred lawyer instead! It's the authors view, but
this view might be wrong!</p><p>Depending on the Microsoft compiler version you use,
some binary files coming from Microsoft might
be required to be installed on Windows machine to run
Wireshark. On a developer machine, the compiler setup
installs these files so they are available - but they might
not be available on a user machine!</p><p>This is especially true for the C runtime DLL
(msvcr*.dll), which contains the implementation of ANSI and
alike functions, e.g.: fopen(), malloc(). The DLL is named
like: msvcr<version>.dll, an abbreviation for
"MicroSoft Visual C Runtime". For Wireshark to work, this DLL
must be available on the users machine.</p><p>Starting with MSVC7, it is necessary to ship the C
runtime DLL (msvcr<version>.dll) together with the
application installer somehow, as that DLL is possibly not
available on the target system.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Note!"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="wsdg_graphics/note.png"></td><th align="left">Note!</th></tr><tr><td align="left" valign="top"><p>The files to redistribute must be mentioned in the
redist.txt file of the compiler package - otherwise it
can't be legally redistributed by third parties like
us!</p></td></tr></table></div><p>The following MSDN links are recommended for the
interested reader:</p><p>
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
<a class="ulink" href="http://msdn2.microsoft.com/library/ms235299(VS.80).aspx" target="_top">
"Redistributing Visual C++ Files"</a>
</p></li><li class="listitem"><p>
<a class="ulink" href="http://msdn2.microsoft.com/library/ms235291(VS.80).aspx" target="_top">
"How to: Deploy using XCopy"</a>
</p></li><li class="listitem"><p>
<a class="ulink" href="http://support.microsoft.com/?scid=kb%3Ben-us%3B326922&x=10&y=13" target="_top">
"Redistribution of the shared C runtime component
in Visual C++ 2005 and in Visual C++ .NET"</a>
</p></li></ul></div><p>
</p><p>
In all cases where <code class="filename">vcredist_x86.exe</code> or
<code class="filename">vcredist_x64.exe</code> is downloaded, it should
be downloaded to the directory into which the support libraries
for Wireshark have been downloaded and installed. This directory
is specified by the WIRESHARK_LIB_DIR setting in the
<code class="filename">config.nmake</code> file; by default it is
<code class="filename">C:\wireshark-win32-libs</code>. It need not, and
should not, be run after being downloaded.
</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp22120868"></a>4.4.6.1. msvcr80.dll / vcredist_x86.exe - Version 8.0
(2005)</h4></div></div></div><p>There are three redistribution methods that MSDN
mentions for MSVC 8 (see:
"<a class="ulink" href="http://msdn.microsoft.com/library/ms235316(VS.80).aspx" target="_top">Choosing a Deployment Method</a>"):
</p><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>"Using Visual C++ Redistributable Merge Modules"
(kind of loadable modules for building msi installers -
not suitable for Wireshark's NSIS based installer)</p></li><li class="listitem"><p>"Using Visual C++ Redistributable Package", wherein
the Microsoft libraries are installed by copying
<code class="filename">vcredist_x86.exe</code>,
<code class="filename">vcredist_x64.exe</code>, or
<code class="filename">vcredist_ia64.exe</code> to the target
machine and executing it on that machine (MSDN recommends
this for applications built with Visual Studio 2005
Express Edition)
</p></li><li class="listitem"><p>"Install a particular Visual C++ assembly as a
private assembly for the application", wherein the
Microsoft libraries are installed by copying the folder
content of <code class="filename">Microsoft.VC80.CRT</code> to
the target directory (e.g. <code class="filename">C:\Program
Files\Wireshark</code>)</p></li></ol></div><p>
</p><p>
To save installer size, and to make a "portable"
version of Wireshark (which must be completely self-contained,
on a medium such as a flash drive, and not require that an
installer be run to install anything on the target machine)
possible, when building 32-bit Wireshark with MSVC2005, method
3 (copying the content of <code class="filename">Microsoft.VC80.CRT</code>)
is used (this produces the smallest package).
</p><p>
As MSVC2005EE and DOTNET20 don't provide the folder
<code class="filename">Microsoft.VC80.CRT</code>, when 32-bit Wireshark
is built with either of them method 2 is used.
You'll have to download the appropriate version of
<code class="filename">vcredist_x86.exe</code> from Microsoft for your
compiler version.
</p><p>
A portable version of 64-bit Wireshark is not built, so method
3 is used for all 64-bit builds. You'll have to download the
appropriate version of <code class="filename">vcredist_x64.exe</code>
or <code class="filename">vcredist_ia64.exe</code> from Microsoft
for your target processor and compiler version.
</p><p>
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
For 32-bit builds using Microsoft Visual C++ 2005
Express Edition without Service Pack 1, you need
<span class="command"><strong>8.0.50608.0</strong></span>,
from: "Microsoft Visual C++ 2005 Redistributable Package (x86)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=3387" target="_top">http://www.microsoft.com/download/details.aspx?id=3387</a>.
</p></li><li class="listitem"><p>
For 64-bit x86 (x64) builds using Microsoft Visual C++
2005, any edition, without Service Pack 1, you need
<span class="command"><strong>{fill this in}</strong></span>,
from: "Microsoft Visual C++ 2005 Redistributable Package (x64)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=21254" target="_top">http://www.microsoft.com/download/details.aspx?id=21254</a>.
</p></li><li class="listitem"><p>
For IA-64 builds using Microsoft Visual C++ 2005, any
edition, without Service Pack 1, you need
<span class="command"><strong>{fill this in}</strong></span>,
from: "Microsoft Visual C++ 2005 Redistributable Package (IA64)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=16326" target="_top">http://www.microsoft.com/download/details.aspx?id=16326</a>.
</p></li><li class="listitem"><p>
For 32-bit builds using Microsoft Visual C++ 2005
Express Edition with Service Pack 1, you need
<span class="command"><strong>8.0.50727.762</strong></span>, from: "Microsoft
Visual C++ 2005 SP1 Redistributable Package (x86)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=5638" target="_top">http://www.microsoft.com/download/details.aspx?id=5638</a>.
</p></li><li class="listitem"><p>
For 64-bit x86 builds using Microsoft Visual C++ 2005,
any edition, with Service Pack 1, you need
<span class="command"><strong>{fill this in}</strong></span>, from: "Microsoft
Visual C++ 2005 SP1 Redistributable Package (x64)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=18471" target="_top">http://www.microsoft.com/download/details.aspx?id=18471</a>.
</p></li></ul></div><p>
</p><p>
Please report to the developer mailing list, if you
find a different version number!
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp22134956"></a>4.4.6.2. msvcr90.dll / vcredist_x86.exe / vcredist_x64.exe - Version 9.0 (2008)</h4></div></div></div><p>There are three redistribution methods that MSDN
mentions for MSVC 9 (see:
"<a class="ulink" href="http://msdn.microsoft.com/en-US/library/ms235316(v=vs.90).aspx" target="_top">Choosing a Deployment Method</a>"):
</p><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>"Using Visual C++ Redistributable Merge Modules"
(kind of loadable modules for building msi installers -
not suitable for Wireshark's NSIS based installer)</p></li><li class="listitem"><p>"Using Visual C++ Redistributable Package", wherein
the Microsoft libraries are installed by copying
<code class="filename">vcredist_x86.exe</code> or
<code class="filename">vcredist_x64.exe</code> to the target
machine and executing it on that machine (MSDN recommends
this for applications built with Visual Studio 2008
Express Edition)
</p></li><li class="listitem"><p>"Install a particular Visual C++ assembly as a
private assembly for the application", wherein the
Microsoft libraries are installed by copying the folder
content of <code class="filename">Microsoft.VC90.CRT</code> to
the target directory (e.g. <code class="filename">C:\Program
Files\Wireshark</code>)</p></li></ol></div><p>
</p><p>
To save installer size, and to make a "portable"
version of Wireshark (which must be completely self-contained,
on a medium such as a flash drive, and not require that an
installer be run to install anything on the target machine)
possible, when building 32-bit Wireshark with MSVC2008, method
3 (copying the content of <code class="filename">Microsoft.VC90.CRT</code>)
is used (this produces the smallest package).
</p><p>
As MSVC2008EE doesn't provide the folder
<code class="filename">Microsoft.VC90.CRT</code>,
when 32-bit Wireshark is built with it method 2 is used.
You'll have to download the appropriate version of
<code class="filename">vcredist_x86.exe</code> from Microsoft for your
compiler version.
</p><p>
A portable version of 64-bit Wireshark is not built, so method
2 is used for all 64-bit builds. You'll have to download the
appropriate version of <code class="filename">vcredist_x64.exe</code>
from Microsoft for your compiler version.
</p><p>
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
For 32-bit builds using Microsoft Visual C++ 2008
Express Edition without Service Pack 1, you need
<span class="command"><strong>9.0.21022.8</strong></span>, from:
"Microsoft Visual C++ 2008 Redistributable Package (x86)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=29" target="_top">http://www.microsoft.com/download/details.aspx?id=29</a>.
</p></li><li class="listitem"><p>
For 64-bit builds using Microsoft Visual C++ 2008,
any edition, without Service Pack 1, you need
<span class="command"><strong>9.0.21022.8</strong></span>, from:
"Microsoft Visual C++ 2008 Redistributable Package (x64)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=15336" target="_top">http://www.microsoft.com/download/details.aspx?id=15336</a>.
</p></li><li class="listitem"><p>
For 32-bit builds with Microsoft Visual C++ 2008
Express Edition with Service Pack 1, you need
<span class="command"><strong>9.0.30729.17</strong></span>, from:
"Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=5582" target="_top">http://www.microsoft.com/download/details.aspx?id=5582</a>.
</p></li><li class="listitem"><p>
For 64-bit builds with Microsoft Visual C++ 2008,
any edition, with Service Pack 1, you need
<span class="command"><strong>9.0.30729.17</strong></span>, from:
"Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=2092" target="_top">http://www.microsoft.com/download/details.aspx?id=2092</a>.
</p></li></ul></div><p>
</p><p>
Please report to the developer mailing list, if you
find a different version number!
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp22147316"></a>4.4.6.3. msvcr100.dll / vcredist_x86.exe / vcredist_x64.exe - Version 10.0 (2010)</h4></div></div></div><p>There are three redistribution methods that MSDN
mentions for MSVC 10 (see:
"<a class="ulink" href="http://msdn.microsoft.com/en-US/library/ms235316(v=vs.100).aspx" target="_top">Choosing a Deployment Method</a>"):
</p><p>
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>"Using Visual C++ Redistributable Package", wherein
the Microsoft libraries are installed by copying
<code class="filename">vcredist_x86.exe</code> or
<code class="filename">vcredist_x64.exe</code> to the target
machine and executing it on that machine (MSDN recommends
this for applications built with Visual Studio 2010,
both Express Edition and non-Express editions)
</p></li><li class="listitem"><p>"Using Visual C++ Redistributable Merge Modules"
(kind of loadable modules for building msi installers -
not suitable for Wireshark's NSIS based installer)</p></li><li class="listitem"><p>"Install a particular Visual C++ assembly as a
private assembly for the application", wherein the
Microsoft libraries are installed by copying the folder
content of <code class="filename">Microsoft.VC100.CRT</code> to
the target directory (e.g. <code class="filename">C:\Program
Files\Wireshark</code>)</p></li></ol></div><p>
</p><p>
To save installer size, and to make a "portable"
version of Wireshark (which must be completely self-contained,
on a medium such as a flash drive, and not require that an
installer be run to install anything on the target machine)
possible, when building 32-bit Wireshark with MSVC2010, method
3 (copying the content of <code class="filename">Microsoft.VC100.CRT</code>)
is used (this produces the smallest package).
</p><p>
As MSVC20010EE doesn't provide the folder
<code class="filename">Microsoft.VC100.CRT</code>,
when 32-bit Wireshark is built with it method 1 is used.
You'll have to download the appropriate version of
<code class="filename">vcredist_x86.exe</code> from Microsoft that
corresponds to your compiler version.
</p><p>
A portable version of 64-bit Wireshark is not built, so method
1 is used for all 64-bit builds. You'll have to download the
appropriate version of <code class="filename">vcredist_x64.exe</code>
from Microsoft for your compiler version.
</p><p>
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
For 32-bit builds using Microsoft Visual C++ 2010
Express Edition without Service Pack 1, you need
<span class="command"><strong>10.0.30319.1</strong></span>, from: "Microsoft Visual
C++ 2010 Redistributable Package (x86)":
<a class="ulink" href="http://www.microsoft.com/download/en/details.aspx?id=5555" target="_top">http://www.microsoft.com/download/en/details.aspx?id=5555</a>.
</p></li><li class="listitem"><p>
For 64-bit builds using Microsoft Visual C++ 2010,
any edition, without Service Pack 1, you need
<span class="command"><strong>10.0.30319.1</strong></span>, from: "Microsoft Visual
C++ 2010 Redistributable Package (x64)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=14632" target="_top">http://www.microsoft.com/download/details.aspx?id=14632</a>.
</p></li><li class="listitem"><p>
For 32-bit builds using Microsoft Visual C++ 2010
Express Edition with Service Pack 1, you need
<span class="command"><strong>10.0.40219.1</strong></span>, from: "Microsoft Visual
C++ 2010 SP1 Redistributable Package (x86)":
<a class="ulink" href="http://www.microsoft.com/download/en/details.aspx?id=8328" target="_top">http://www.microsoft.com/download/en/details.aspx?id=8328</a>.
</p></li><li class="listitem"><p>
For 64-bit builds using Microsoft Visual C++ 2010,
any edition, with Service Pack 1, you need
<span class="command"><strong>10.0.40219.1</strong></span>, from: "Microsoft Visual
C++ 2010 SP1 Redistributable Package (x64)":
<a class="ulink" href="http://www.microsoft.com/download/details.aspx?id=13523" target="_top">http://www.microsoft.com/download/details.aspx?id=13523</a>.
</p></li></ul></div><p>
</p><p>
Please report to the developer mailing list, if you
find a different version number!
</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp22159836"></a>4.4.7. Windows (Platform) SDK</h3></div></div></div><p>The Windows Platform SDK (PSDK) or Windows SDK is a free
(as in beer) download and contains platform specific headers and
libraries (e.g. windows.h, WSock32.lib, ...). As new Windows
features evolve in time, updated SDK's become available that
include new and updated API's.</p><p>When you purchase a commercial Visual Studio, it will
include an SDK. The free (as in beer) downloadable C compiler
versions (VC++ 2005 Express, .NET Framework, ...) do not
contain an SDK - you'll need to download a PSDK in order to
have the required C header files and libraries.</p><p>Older versions of the SDK should also work. However, the
command to set the environment settings will be different, try
search for SetEnv.* in the SDK directory.</p><p>Prior to Windows Vista, the name "Platform SDK" was used;
starting with Vista, the name was changed just to "Windows
Software Development Kit" or "Windows SDK". The full names of the
SDKs can be misleading; for example, the SDK for Vista was called
the "Microsoft Windows Software Development Kit for Windows Vista
and .NET Framework 3.0 Runtime Components", which really means the
Windows SDK for Windows Vista and Platforms (like WinXP) that have
the .NET 3.0 runtime installed.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp22162348"></a>4.4.8. HTML Help</h3></div></div></div><p>The HTML Help is used to create the User's and
Developer's Guide in .chm format and to show the User's Guide
as the Wireshark "Online Help".</p><p>Both features are currently optional, but might be
mandatory in future versions.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp22163308"></a>4.4.8.1. HTML Help Compiler (hhc.exe)</h4></div></div></div><p>This compiler is used to generate a .chm file
from a bunch of HTML files - in our case to generate
the User's and Developer's Guide in .chm format.</p><p>The compiler is only available as the free (as in
beer) "HTML Help Workshop" download. If you want to compile
the guides yourself, you need to download and install this.
If you don't install it into the default directory, you may
also have a look at the HHC_DIR setting in the file
docbook/Makefile.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp22164628"></a>4.4.8.2. HTML Help Build Files (htmlhelp.c /
htmlhelp.lib)</h4></div></div></div><p>The files htmlhelp.c and htmlhelp.lib are required to
be able to open .chm files from Wireshark - to show the
"online help".</p><p>Both files are part of the SDK (standalone (P)SDK or MSVC
since 2002). If you still use MSVC 6, you can get them from the
"HTML Help Workshop" mentioned above.</p><p>The related settings in config.nmake depend on the
MSVC variant you use:</p><p>
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>MSVC 6: if the "HTML Help Workshop" is
installed, set HHC_DIR to its directory</p></li><li class="listitem"><p>> MSVC 6: set HHC_DIR to use it (the actual
value doesn't matter in this case)</p></li></ul></div><p>
</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChToolsDebugger"></a>4.4.9. Debugger</h3></div></div></div><p>Well, using a good debugger can save you a lot of
development time.</p><p>The debugger you use must match the C compiler
Wireshark was compiled with, otherwise the debugger will
simply fail or you will only see a lot of garbage.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="ChToolsMSVCDebugger"></a>4.4.9.1. Visual Studio integrated debugger</h4></div></div></div><p>You can use the integrated debugger of Visual Studio
- only available in some of the toolchain packages.</p><p>However, setting up the environment is a bit tricky,
as the Win32 build process is using makefiles instead of
the .dsp/.dsw files usually used.</p><p>XXX - add instructions how to do it.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="ChToolsMSDebuggingTools"></a>4.4.9.2. Debugging Tools for Windows</h4></div></div></div><p>You could also use the Microsoft Debugging Tools for Windows toolkit,
which is a standalone GUI debugger. Although it's not that
comfortable compared to debugging with the Visual Studio
integrated debugger, it can be helpful if you have to debug
on a machine where an integrated debugger is not
available.</p><p>You can get it free of charge at:
<a class="ulink" href="http://www.microsoft.com/whdc/devtools/debugging/default.mspx" target="_top">http://www.microsoft.com/whdc/devtools/debugging/default.mspx</a> (as
links to Microsoft pages change from time to time, search
for "Debugging Tools" at their page if this link should be
outdated).</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ChToolsGNUChain.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ChapterTools.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ChToolsBash.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.3. GNU compiler toolchain (UNIX or Win32 Cygwin) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.5. bash</td></tr></table></div></body></html>
|