On 8/27/07, Greg Bell <[EMAIL PROTECTED]> wrote: > > Thanks for that reply. I'm glad someone confirmed it works using VC > 2005EE. What about the Platform SDK, did you use Server 2003 R2? >
Yes, I also have VS80sp1-KB926748-X86-INTL.exe installed for the reason I forgot. Regarding your mods, > 2. We're referring to C:\wireshark-0.99.6\tools\win32-setup.sh right? > Yes. 3. Do you replace all occurences of xcopy (in if statements only) with "c:/WINNT/system32/xcopy"? > For example, > if exist wireshark.pdb xcopy wireshark.pdb $(INSTALL1_DIR) /d > Becomes: > if exist wireshark.pdb "c:/WINNT/system32/xcopy" wireshark.pdb$(INSTALL1_DIR) > /d > Yes. I tried changing my build environment to VC6 and it now works on Windows > 2000. I may just end up sticking with this build setup, as it resolves my > issue and seems less problamatic than using VC2005EE. I think the "Win32: > Step-by-Step Guide" should state at the top that if you have VC6, use it > instead of 2005EE. > > Thanks and regards, > Greg > > *yin sun <[EMAIL PROTECTED]>* wrote: > > I did the clean build again on HP/compaq nc8000 with 0.99.6 source > I unzip the source under c:\wireshark-0.99.6 > Here are some modifications I did. > 1. config.nmake MSVC_VARIANT=MSVC2005EE > 2. dos2unix win32-setup.sh win32-setup.shc (my cygwin use unix line > convention) > 3. Use full path such as "c:/WINNT/system32/xcopy" to replace xcopy in if > statement of Makefile.nmake > > Then the build, > nmake -f Makefile.nmake verify_tools > nmake -f Makefile.nmake setup to update the c:\wireshark-win32-libs > nmake -f Makefile.nmake distclean > nmake -f Makefile.nmake all > > During the build there is only one annoying thing. The nmake failed > sometime, complaining "xxx is not a reconized ...". Then what I need to do > is run the "nmake -f Makefile.nmake all" again. > > Hope this will help. I didn't have the problem you had. One thing I > noticed is I have > verion .762 of Program Maintenance Utility, but you have .42 > > nmake -f Makefile.nmake verify_tools > > Microsoft (R) Program Maintenance Utility Version 8.00.50727.762 > Copyright (C) Microsoft Corporation. All rights reserved. > > Checking for required applications: > cl: /cygdrive/c/Program Files/Microsoft Visual Studio 8/VC/BIN/cl > link: /cygdrive/c/Program Files/Microsoft Visual Studio > 8/VC/BIN/link > nmake: /cygdrive/c/Program Files/Microsoft Visual Studio > 8/VC/BIN/nmake > > Thanks, > /Yin > > > On 8/24/07, Greg Bell <[EMAIL PROTECTED]> wrote: > > > > I'm assuming when I do the verify_tools step, it confirms that I'm using > > nmake/cl/link from VS8 based on the output: > > > > C:\wireshark>nmake -f Makefile.nmake verify_tools > > Microsoft (R) Program Maintenance Utility Version 8.00.50727.42 > > Copyright (C) Microsoft Corporation. All rights reserved. > > Checking for required applications: > > cl: /cygdrive/c/Program Files/Microsoft Visual Studio > > 8/VC/BIN/cl > > link: /cygdrive/c/Program Files/Microsoft Visual Studio > > 8/VC/BIN/link > > nmake: /cygdrive/c/Program Files/Microsoft Visual Studio > > 8/VC/BIN/nmake > > bash: /usr/bin/bash > > ............ > > > > *yin sun <[EMAIL PROTECTED]> *wrote: > > > > the wiki page suggest you ONLY use nmake/cl/link from VS8 (true name of > > Visual C++ 2005 Express Edition), > > but make sure NOT use nmake/cl/link from 2003 server SDK R2 under > > windows 2000. > > > > Hope this will help. > > > > /Yin > > > > On 8/22/07, Graham Bloice <[EMAIL PROTECTED]> wrote: > > > > > > Greg Bell wrote: > > > > I guess if I used VS 6.0, I wouldn't need Platform SDK 2003 as its > > > > already integrated in the 6.0 compiler package. To use 6.0, I would > > > > need to prepare cmd.exe by calling > > > > "C:\Program Files\Microsoft Visual Studio\VC98\Bin\vcvars32.bat" > > > > instead of > > > > "C:\Program Files\Microsoft Visual Studio 8\VC\bin\vcvars32.bat" > > > > correct? > > > Yes. You also need to make changes to config.nmake to indicate the > > > use > > > of VC6. > > > > > > > > This would still not resolve the issue with VC 2005 EE and Platform > > > > SDK 2003 R3. I'm surprised this is not a common problem among other > > > > Wireshark developers; do people just not use (or test on) Windows > > > 2000 > > > > anymore? > > > > > > > I guess folks are: > > > > > > a) Using a combination of EE and SDK that works on W2K > > > b) Not testing/using on W2K > > > c) Using VS2005 Pro or better with a different SDK. > > > > > > We have had several threads in the past few months with this issue, > > > but > > > no-one who has had the issue has stayed the course until we resolved > > > it. > > > > > > You may want to buck the trend! > > > > > > -- > > > Regards, > > > > > > Graham Bloice > > > > > > _______________________________________________ > > > Wireshark-dev mailing list > > > Wireshark-dev@wireshark.org > > > http://www.wireshark.org/mailman/listinfo/wireshark-dev > > > > > > > _______________________________________________ > > Wireshark-dev mailing list > > Wireshark-dev@wireshark.org > > http://www.wireshark.org/mailman/listinfo/wireshark-dev > > > > > > ------------------------------ > > Shape Yahoo! in your own image. Join our Network Research Panel > > today!<http://us.rd.yahoo.com/evt=48517/*http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7> > > > > _______________________________________________ > > Wireshark-dev mailing list > > Wireshark-dev@wireshark.org > > http://www.wireshark.org/mailman/listinfo/wireshark-dev > > > > > _______________________________________________ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-dev > > > ------------------------------ > Yahoo! oneSearch: Finally, mobile search that gives > answers<http://us.rd.yahoo.com/evt=48252/*http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC>, > not web links. > > > _______________________________________________ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-dev > >
_______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
