As a quick & dirty test, I made the following change to Makefile.nmake, and SVN32737 compiled just fine.
Index: Makefile.nmake
===================================================================
--- Makefile.nmake (revision 32737)
+++ Makefile.nmake (working copy)
@@ -626,7 +626,8 @@
if not exist $(ZLIB_DIR) mkdir $(ZLIB_DIR)
if not exist $(ZLIB_DIR)\lib mkdir $(ZLIB_DIR)\lib
if not exist $(ZLIB_DIR)\include mkdir $(ZLIB_DIR)\include
-!IFDEF MANIFEST_INFO_REQUIRED
+!IFDEF 0
+#MANIFEST_INFO_REQUIRED
mt.exe -nologo -manifest "zlib1.dll.manifest" -outputresource:zlib1.dll;2
!ENDIF
copy zlib1.dll $(ZLIB_DIR)
Unfortunately, I'm still seeing the same problem as Joan reported earlier with tshark:
C:\wireshark\vs2008ee>wireshark-gtk2\tshark.exe -i 3
Capturing on Intel(R) 82567LM Gigabit Network Connection (Microsoft's Packet Scheduler)
tshark: The capture session could not be initiated ().
Please check that "\Device\NPF_{7798FBA2-0E70-403F-BFD4-76F44AFB62FD}" is the proper interface.
Help can be found at:
http://wiki.wireshark.org/WinPcap
http://wiki.wireshark.org/CaptureSetup
0 packets captured
C:\wireshark\vs2008ee>
The same problem occurs when running Wireshark, so the problem isn't limited to tshark. At Gerald's suggestion, I rolled back to r32697, did a distclean and complete rebuild, but the above problem still persists. I even tried uninstalling/reinstalling WinPcap-1.1.1, but it also had no effect.
- Chris
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Maynard, Chris
Sent: Monday, May 10, 2010 4:08 PM
To: 'Developer support list for Wireshark'
Subject: Re: [Wireshark-dev] tshark (Windows) not working
Hi Bill,
No, I didn't update the compiler, only the SDK. Within the Overview section of
the SDK page, it mentions the following:
"This SDK is compatible with Visual Studio® 2008, including Visual Studio
Express Editions, ..."
See: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c17ba869-9671-4330-a63e-1fd44e0e2505
But again, the problem seems to be related to this missing
zlib1.dll.manifest file. Searching for all manifests following a distclean
reveals only the following:
cmaynard@HQCMAYNARD2 /cygdrive/c/wireshark-win32-libs
$ find . -name \*.manifest
./gtk2/bin/gtk-update-icon-cache.exe.manifest
cmaynard@HQCMAYNARD2 /cygdrive/c/wireshark/vs2008ee
$ find . -name \*.manifest
./packaging/u3/win32/u3util.exe.manifest
./plugins/agentx/agentx.dll.manifest
./plugins/artnet/artnet.dll.manifest
./plugins/ciscosm/ciscosm.dll.manifest
./plugins/enttec/enttec.dll.manifest
./plugins/infiniband/infiniband.dll.manifest
./plugins/lwres/lwres.dll.manifest
./plugins/opsi/opsi.dll.manifest
./plugins/pcli/pcli.dll.manifest
./plugins/rlm/rlm.dll.manifest
./plugins/rtnet/rtnet.dll.manifest
./plugins/rudp/rudp.dll.manifest
./plugins/sbus/sbus.dll.manifest
./plugins/v5ua/v5ua.dll.manifest
- Chris
Meier, Bill wrote:
>Note: A while back I found that VS2010 (VC10) no longer generates
>manifest files as a default. (search for previous -dev EMails on using
>VC10).
>
>Did updating the SDK update the compilier ??
>
> From your link above ...
>
>The Windows SDK for Windows 7 and .NET Framework 3.5 SP1 provides the
>documentation, samples, header files, libraries, and tools (including
>C++ compilers) ....
>
>
>Bill
[snip]
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.
