Wireshark-dev: [Wireshark-dev] problem on "Prepare cmd.exe"
From: "Joshua (Shiwei) Zhao" <swzhao@xxxxxxxxx>
Date: Fri, 31 Oct 2008 17:20:51 -0700
Hi,
I just lost my development setup so I has to rebuild it following the
develop guide for windows OS.
I remember there was 4 steps to prepare cmd.exe, but now there is only
3 steps. I remember that I had to call another file before calling
cvars32.bat.  Anyone knows what's changed?

The following is what's in the current guide:
2.2.6. Prepare cmd.exe
Prepare cmd.exe - set environment and current dir.
1. start cmd.exe
2. call C:\Program Files\Microsoft Visual Studio
9.0\VC\bin\vcvars32.bat to set environment variables of Visual C++
2008 Express Edition 1,2
3. cd C:\wireshark to jump into the source directory
Note1: Compiler dependent: This step depends on the compiler variant
used, for other variants than the recommended Visual C++ 2008 Express
Edition see the table at Section 4.4, "Microsoft compiler toolchain
(Win32 native)"!
Note2: International 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!

I guess the missing step is the reason why I'm seeing the following error:
C:\wireshark-1.0.4>nmake -f Makefile.nmake verify_tools
Microsoft (R) Program Maintenance Utility Version 9.00.30729.01
Copyright (C) Microsoft Corporation.  All rights reserved.

tools/win32-setup.sh: line 4: $'\r': command not found
tools/win32-setup.sh: line 11: $'\r': command not found
tools/win32-setup.sh: line 14: $'\r': command not found
tools/win32-setup.sh: line 15: syntax error near unexpected token `$'{\r''
'ools/win32-setup.sh: line 15: `err_exit () {
NMAKE : fatal error U1077: 'd:\downloads\cygwin\bin\bash.EXE' : return code '0x2
'
Stop.


Many thanks,
Joshua