Wireshark-dev: Re: [Wireshark-dev] 0.99.6 build problems on Windows
Date: Mon, 8 Oct 2007 13:47:27 -0500
For what it's worth? I just finished building Wireshark from 99.6 after
performing the following (per Developers Guide):

1. MSVC v6 was installed with default setup. Installed a couple years
ago.

Performed today!!!

2. Install CYGWIN (just the tools specified in Dev Guide.)
3. Unzip 99.6 tarball to wireshark-0.99.6 directory (path contained in
archive)
	- modified config.nmake so that wireshark_libs = o:\, instead of
c:\
4. Create DOS window with clean environment (created via batch file),
minimizes environment issues.
5. performed dist_clean (nmake -f Makefile.nmake dist_clean)
6. performed setup (nmake -f Makefile.nmake setup)
7. perform make (nmake -f Makefile.nmake) SUCCESS!!!






> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of 
> Graham Bloice
> Sent: Monday, October 08, 2007 11:46 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] 0.99.6 build problems on Windows
> 
> Michael Lum wrote:
> > I updated my cygwin installation but that didn't help.
> >
> > I followed the link for the MS Platform SDK but it states VC 6.0 is 
> > not
> > supported:
> >
> > Development Tools. To build the C/C++ samples, you must 
> have a C/C++ 
> > compiler. If you are using Microsoft Visual C/C++(r), run 
> it at least 
> > once before installing the SDK. This will ensure that the 
> environment 
> > variables are correctly configured. To build the Visual 
> Basic samples, 
> > you must have Microsoft Visual Basic(r). This SDK does not support 
> > working with Microsoft Visual C/C++(r), 6.0 as support for 
> VC 6.0 has 
> > ended. The last SDK that will work with VC 6.0 is the February 2003 
> > Edition, you can order a CD on the fulfillment site. Side by side 
> > installations are not supported.
> >
> > So unfortunately I'm still stuck.
> > I have tried, clean, distclean, setup, all, again but to no avail.
> >
> >   
> OK, so we really need some more clues about the compilation 
> errors.  You can try getting the output from the preprocessor 
> to see if that gives any more clues.  Be aware the output is 
> massive, consisting mostly of blank lines, but might help you out.
> 
> 1.  cd into the epan dir and compile filesystem.c on its own 
> with "nmake makefile.nmake filesystem.obj"
> 2.  Copy the compiler invocation emitted by nmake and paste 
> it back into your command prompt, but tack a "-P" on the end 
> 3.  This should produce a filesystem.i for your perusal.  Good luck.
> 
> --
> Regards,
> 
> Graham Bloice
> 
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>