Ulf Lamping wrote:
Graham Bloice wrote:
CANDIA, Fabrice wrote:
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows
Server 2003 R2\Bin and not the directory mentioned in the developper's
guide (Visual studio dir). Is it normal ?
The paths shown in the dev guide
] WIN32 Compilation failed : tshark is not a
validwin32 application
Graham Bloice wrote:
CANDIA, Fabrice wrote:
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows Server
2003 R2\Bin and not the directory mentioned in the developper's guide
(Visual studio dir). Is it normal
@wireshark.org
Objet : [Wireshark-dev] WIN32 Compilation failed : tshark is not a
validwin32 application
Hi all,
I try to build Wireshark 0.99.5 (I followed the developper's guide, installed
Visual C++ 2005 Express platform SDK, cygwin, python 2.5) but I get the
following error :
wireshark
CANDIA, Fabrice wrote:
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows Server
2003 R2\Bin and not the directory mentioned in the developper's guide (Visual
studio dir). Is it normal ?
The paths shown in the dev guide are for information only and refer to a
VC 6.0
: [Wireshark-dev] WIN32 Compilation failed : tshark is not a
validwin32 application
CANDIA, Fabrice wrote:
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows Server
2003 R2\Bin and not the directory mentioned in the developper's guide (Visual
studio dir). Is it normal
CANDIA, Fabrice wrote:
So someone has already built Wireshark 0.99.5 under Windows 2000 ?
Why tshark and other bin do not work ?
I think you're confusing the version of VC and the OS. I build it using
VC 6.0 on XP, the same as the buildbot and have previously built on W2K,
but not for a
Graham Bloice wrote:
CANDIA, Fabrice wrote:
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows Server
2003 R2\Bin and not the directory mentioned in the developper's guide
(Visual studio dir). Is it normal ?
The paths shown in the dev guide are for information
