Wireshark · Ethereal-dev: Re: [Ethereal-dev] Win32 generation toolchain (perl, python, bash, ...) and config.nmake

[Andrew Hood <ajhood@xxxxxxxxx>]

Graham Bloice wrote:
> > You can build for "native WinXX" (without cygwin linkage)
> > with GCC, but you then need to use one of the GCC compiler
> > flags (I think it's -mno-cygwin), and maybe you'll have to
> > use libraries that are not in a.out format but in .obj or
> > .dll format) or use mingw instead.
>
>
> IMHO it would be a retrograde step to make the default Win32 build use
> Cygwin.  While I use cygwin a lot, native tools (python, perl, etc) are much
> faster, as is MSVC.

I have non-cygwin tools to do the whole build process.

> As long as there is a clear "HOWTO" describing the build process on win32,
> and availability of the required libraries and DLL's from the ethereal site
> then I'm not particularly convinced of the need for ethereal to support a
> cygwin distribution.
>
> To that end should we think about creating a win32 "dev" install that does
> all the work ?  I could help out with this.

But is it going to work with VC7?

Or can someone explain how to tell VC7 to not use MSVCRT70.DLL

Until I get a solution to that I get a working tethereal but don't get a 
working ethereal.

--
There's no point in being grown up if you can't be childish sometimes.
                -- Dr. Who