After you've installed the Ethereal sources (see Section 4.4, “Obtain the Ethereal sources”), you can check the correct installation of
all tools by using the verify_tools target of the
Makefile.nmake
from the source package.
![]() | Warning! |
---|---|
You will need the Ethereal sources and some tools (nmake, bash) installed, before this verification is able to work. |
Enter at the command line:
>
nmake -f Makefile.nmake verify_tools
This will check for the various tools needed to build Ethereal:
Checking for required applications: cl: /cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin/cl link: /cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin/link nmake: /cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin/nmake bash: /usr/bin/bash bison: /usr/bin/bison flex: /usr/bin/flex env: /usr/bin/env grep: /usr/bin/grep find: /usr/bin/find perl: /usr/bin/perl env: /usr/bin/env python: /usr/bin/python sed: /usr/bin/sed unzip: /usr/bin/unzip wget: /usr/bin/wget
If you have problems with all the first three ones, check if you called ...\Microsoft Visual Studio\VC98\Bin\vcvars32.bat before (which will "fix" your PATH settings).
Unfortunately, the link command is defined both from cygwin and from MSVC with completely different purpose, 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 renaming the link.exe in cygwin. If you rename it, make sure to remember that a cygwin update may provide a new version of it.