Ah yes, thanks Pascal. It’s been a really long since
I’ve worked with the 1.0 branch and forgot.
If I comment out HHC_DIR in config.nmake, it compiles
successfully with VS6.0; otherwise
the following error occurs:
Microsoft (R) Program Maintenance Utility Version
6.00.9782.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
cl -DWIN32 -DNULL=0
-D_MT -D_DLL -WX -DHAVE_CONFIG_H /I.. /I../wiretap /
IC:\wireshark-libs-1.0\glib\include\glib-2.0
/IC:\wireshark-libs-1.0\glib\lib\g
lib-2.0\include /IC:\wireshark-libs-1.0\gtk+\include
/IC:\wireshark-libs-1.0\gtk
+\include\gdk
/IC:\wireshark-libs-1.0\gtk+\lib\gtk+\include /IC:\wireshark-libs
-1.0\gnutls-2.8.5-2\include /DNOCRYPT
/IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIB
PCAP /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP\bpf
/IC:\wireshark-libs-1.0\
WPdpack\WPCAP\LIBPCAP\lbl
/IC:\wireshark-libs-1.0\WPdpack\include /Zm800 -D_U
_="" -D_NEED_VAR_IMPORT_ /Zi /W3 /MD
/DMSC_VER_REQUIRED=1200 /IC:\wireshark-lib
s-1.0\portaudio_v19\include
/IC:\wireshark-libs-1.0\portaudio_v19\src\common /I
"C:/Program Files/HTML Help Workshop\include"
-DHHC_DIR -Fd.\ -c help_dlg.c
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version
12.00.8804 for 80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
help_dlg.c
help_dlg.c(49) : fatal error C1083: Cannot open include file:
'htmlhelp.h': No s
uch file or directory
NMAKE : fatal error U1077: 'cl' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~4\VC98\BIN\NMAKE.EXE'
: return co
de '0x2'
Stop.
- Chris
From:
wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Pascal Quantin
Sent: Wednesday, May 19, 2010 10:47 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] trunk-1.0 fails to compile on Windows with
VS2008EE
Hi
2010/5/19 Maynard, Chris <Christopher.Maynard@xxxxxxxxx>
As the subject line indicates, trunk-1.0 fails to
compile on Windows with VS2008EE.
The error log is attached.
VS2008EE compilation was added
in wireshark 1.2. That's why. If really needed, you can try to backport the
patchs attached (or check the comments for the corresponding svn revisions) to
bugs 2719, 2075, 2940. But you will probably face other issues.
Regards,
Pascal