fix build instructions for windows

This issue was migrated from bug 10076 in our old bug tracker.

Original bug information:

Reporter: Edwin Groothuis
Status: RESOLVED FIXED
Product: Wireshark
Component: Documentation
OS: Windows 7
Platform: x86
Version: Git

Edwin Groothuis said:

Build Information:

Paste the COMPLETE build information from "Help->About Wireshark", "wireshark -v", or "tshark -v".

http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html says:

======= 8< ========
If your version of the compiler does not have SetEnv.Cmd you may need to use vcvarsall.bat or vcvars32.bat which do much the same thing as SetEnv.cmd. For example, on some 64-bit installations, one would build a 32-bit version by invoking

> "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat  

and one would build a 64-bit version using the command

> "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\Vcvarsall.bat" amd64  

Consult your compiler’s documentation to learn which version applies to your installation.
======= 8< ========

In the latest version of Visual Studio 2010EE (as suggested by the instructions), vcvars32.bat doesn't exist anymore, it is now all vcvarsall.bat and the expected argument is x86.



The same page says:

======= 8< ========
2.2.2. Install Cygwin

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, if the package has a "Skip" item in the "New" column, click on the "Skip" item so it shows a version number for:

    Archive/unzip
    Base/dos2unix
    Devel/bison
    Devel/flex
    Devel/git (recommended - see discussion about using Git below)
    Interpreters/perl
    Utils/patch (optional)
    Web/wget
======= 8< ========

base/dos2unix is in utils, while you need to add interpreters/m4 to the list to get ascend.y converted by bison into ascend.c.



The same page has conflicting path names. Generally it talks about c:\development\wireshark, but in the Build Wireshark section and in the Create Wireshark Installer section it still refers to c:\wireshark:

 Run C:\wireshark\wireshark-gtk2\wireshark.exe and make sure it starts. s
 Run > C:\wireshark\packaging\nsis\wireshark-win32-wireshark-major-minor-version:[].x-myprotocol123.exe to test your new installer.




Further as a general statement please add that if the Visual C++ installation or the SDK or the Service Pack upgrades constantly fail, that

added docs oswindows versiondev labels

Edwin Groothuis said:

Further as a general statement please add that if the Visual C++ installation or the SDK or the Service Pack upgrades constantly fail, that running it a virgin VM environment will resolve that drama.

Graham Bloice said:

I think this is all done now, re-open or raise a new entry if further changes are required.

closed