All the tools required are usually installed on a UNIX developer machine. If a tool is not already installed on your system, you will typically use the installation package from your distribution (by your favourite package manager: aptitude, yum, synaptics, ...). If an install package is not available, or you have a reason not to use it (maybe because it's simply too old), you can install that tool from source code. The following sections will provide you with the webpage addresses where you can get these sources.

A quick setup guide for Win32 with recommended configuration. Unless you know exactly what you are doing, you should strictly follow the recommendations!

You need to install, in exactly this order: C compiler: Download and install "Microsoft Visual C++ 2010 Express Edition." (This is a very large download.) Windows SDK for Windows 7, if you want to build 64-bit binaries for Windows 7: Download and install "Microsoft Windows SDK for Windows 7." C compiler service pack: Download and install "Microsoft Visual Studio 2010 Service Pack 1." (This is a very large download.) Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1, if you want to build 64-bit binaries for Windows 7: Download and install "Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1." If you will be building 64-bit binaries, those items must be installed in that order, as installing the Microsoft Visual Studio 2010 Service Pack 1 can, if you've installed the Microsoft Windows SDK for Windows 7, remove the 64-bit compilers, as per the Microsoft Knowledge Base article "FIX: Visual C++ compilers are removed when you upgrade Visual Studio 2010 Professional or Visual Studio 2010 Express to Visual Studio 2010 SP1 if Windows SDK v7.1 is installed". The release notes for the Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1 say that, to ensure that your system has a supported configuration, you must install the items in the order specified above. If you have Microsoft Update installed, so that the Windows update process will update software other than components of Windows, and thus will update Visual Studio, you may need to disable it until after all of the above are installed, to make sure it doesn't install Visual Studio 2010 SP1 out of order. Install MSVC the usual way. Don't forget to install vcvars32.bat or call it manually before building Wireshark. vcvars32.bat will set some required environment (e.g. the PATH) settings. It's possible to compile Wireshark with a wide range of Microsoft C compiler variants. For details see ! Using Cygwin's gcc is not recommended and will certainly not work (at least without a lot of advanced tweaking). For further details on this topic, see . XXX - mention the compiler and PSDK web installers - which significantly reduce download size - and find out the required components Wireshark development depends on several environment variables, particularly PATH. You can use a batch script to fill these in, for example Why is this recommended? While this is a huge download, the 2010 Express Edition is the only free (as in beer) version that includes the Visual Studio integrated debugger. Visual C++ 2010 is also used to create official Wireshark builds, so it will likely have fewer development-related problems.

Download the Cygwin installer and start it. At the "Select Packages" page, you'll need to select some additional packages, which are not installed by default. Navigate to the required Category/Package row and click on the "Skip" item in the "New" column so it shows a version number for: Archive/unzip Archive/zip (only needed if you intend to build the U3 package) Base/rebase Devel/bison Devel/flex Interpreters/perl Utils/patch Web/wget After clicking the Next button several times, the setup will then download and install the selected packages (this may take a while). Why this is recommended: Cygwin's bash version is required, as no native Win32 version is available. As additional packages can easily be added, the perl and alike packages are also used.

Get the Python 2.7 installer from: and install Python into the default location (C:\Python27). Why this is recommended: Cygwin's Python package doesn't work on some machines, so the Win32 native package is recommended.

Please note that the following is not required to build Wireshark, but can be quite helpful when working with the sources. Why this is recommended: updating a personal source tree is significantly easier to do with Subversion than downloading a zip file and merging new sources into a personal source tree "by hand".

If you want to work with the Wireshark Subversion source repositories (which is highly recommended, see ), it's recommended to install Subversion. This makes the first time setup easy and enables the Wireshark build process to determine your current source code revision. You can download the setup from and simply install it.

If you want to work with the Wireshark Subversion source repositories (which is highly recommended, see ), it's recommended to use TortoiseSVN for your everyday work. You can download the setup from and simply install it.

It's a good idea to successfully compile and run Wireshark at least once before you start hacking the Wireshark sources for your own project! Download sources : Download Wireshark sources into: C:\wireshark using TortoiseSVN right click on the C:\ drive in Windows Explorer in the upcoming context menu select "SVN checkout..." and then set: URL of repository: " http://anonsvn.wireshark.org/wireshark/trunk/" Checkout directory: C:\wireshark TortoiseSVN might ask you to create this directory - say yes TortoiseSVN starts downloading the sources if the download fails you may be behind a restrictive firewall, see for alternative download methods Edit config.nmake: edit the settings in C:\wireshark\config.nmake, especially: VERSION_EXTRA : Give Wireshark your "private" version info, e.g.: -myprotocol123 - to distinguish it from an official release! PROGRAM_FILES : Where your programs reside, usually just keep the default: C:\Program Files 2 MSVC_VARIANT : Make sure the variant for your compiler is uncommented, and that all others are commented out. For example, if you're using Visual C++ 2010 Express Edition, find the line and remove the comment character (#) from the beginning of the line. Then, find the line and comment it out, by prefixing a hash (#). 1 1Compiler dependent: This step depends on the compiler you are using. For compilers other than Visual C++ 2010, see the table at . 2International Windows might use different values here, e.g. a German version uses C:\Programme - take this also in account where C:\Program Files appears elsewhere.

Prepare cmd.exe - set environment and current dir. start cmd.exe call C:\Program Files\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat to set environment variables of Visual C++ 2010 Express Edition. 1,2 cd C:\wireshark to jump into the source directory 1Compiler dependent: This step depends on the compiler variant used, for other variants than the recommended Visual C++ 2010 Express Edition see the table at ! 2International Windows might use different values here, e.g. a German version uses C:\Programme - take this also in account where C:\Program Files appears elsewhere. Note: You need to repeat steps 1 - 4 each time you open a new cmd.exe!

After you've installed the Wireshark sources (see ), you can check the correct installation of all tools by using the verify_tools target of the Makefile.nmake from the source package. You will need the Wireshark sources and some tools (nmake, bash) installed, before this verification is able to work. Enter at the command line (cmd.exe, not Cygwin's bash!): > nmake -f Makefile.nmake verify_tools This will check for the various tools needed to build Wireshark: If you have problems with all the first three items (cl, link, nmake), check if you called vcvars32/SetEnv as mentioned in (which will "fix" your PATH settings). However, the exact text will be slightly different depending on the MSVC version used. Unfortunately, the link command is defined both in Cygwin and in MSVC each with completely different functionality; you'll need the MSVC link. If your link command looks something like: /usr/bin/link, the link command of Cygwin takes precedence over the MSVC one. To fix this, you can change your PATH environment setting or simply rename the link.exe in Cygwin. If you rename it, make sure to remember that a Cygwin update may provide a new version of it.

If you've closed cmd.exe in the meantime, prepare cmd.exe again. nmake -f Makefile.nmake setup downloads libraries using wget and installs them - this may take a while ... If the download fails you may be behind a restrictive firewall, see the proxy comment in .

The released Wireshark sources contain files that are prepared for a UNIX build (e.g. config.h). You must distclean your sources before building the first time! If you've closed cmd.exe in the meantime, prepare cmd.exe again nmake -f Makefile.nmake distclean to cleanup the Wireshark sources

Now it's time to build Wireshark ... If you've closed cmd.exe in the meantime, prepare cmd.exe again nmake -f Makefile.nmake all to build Wireshark wait for Wireshark to compile - this may take a while! run C:\wireshark\wireshark-gtk2\wireshark.exe and check if it starts check Help/About if it shows your "private" program version, e.g.: Version &WiresharkCurrentVersion;.x-myprotocol123 - you might run a release version previously installed! Tip: If compilation fails for suspicious reasons after you changed some source files try to "distclean" the sources and make "all" again

XXX - debug needs to be written, e.g. an idea is the create a simple MSVC workspace/project(s) to ease Visual Studio debugging

Detailed information to build these guides can be found in the file docbook/README.txt in the Wireshark sources.

Note: You should have successfully built Wireshark before doing the following! If you want to build your own wireshark-win32-&WiresharkCurrentVersion;.x-myprotocol123.exe, you'll need NSIS. NSIS: Download and install NSIS You may check the MAKENSIS setting in the file config.nmake of the Wireshark sources. vcredist_x86.exe : Download the C-Runtime redistributable for Visual C++ 2010 Express Edition SP1 (vcredist_x86.exe) and copy it into C:\wireshark-win32-libs 1 If you've closed cmd.exe in the meantime, prepare cmd.exe again nmake -f Makefile.nmake packaging build Wireshark installer run C:\wireshark\packaging\nsis\wireshark-win32-&WiresharkCurrentVersion;.x-myprotocol123.exe and test it - it's a good idea to test also on a different machine than the developer machine. 1Compiler dependent: This step depends on the compiler variant used; for other variants than the recommended Visual C++ 2010 Express Edition SP1 see the table at !