> 2. The problem is not editing the Makefile.nmake , but to create a new
> Makefile.in from the Makefile.am . That procedure don't happening in
> windows.
"Makefile.in" exists solely so that the "configure" script can generate
a Makefile from it. "Makefile.in" is generated from "Makefile.am" by
"automake", but I don't know whether Cygwin comes with automake or
whether there are ports of automake to Windows.
In addition, as Andreas said, there's a script missing from the Windows
GLib and GTK+ that the "configure" script requires in order to work.
Furthermore, I don't know whether that "configure" script would, if run
with "--without-gcc", set up the Makefile to use Microsoft Visual C++;
nobody's succeeded in building Ethereal with GCC on Windows (or, if they
have, they haven't told us about it), so I don't know whether that would
work.
As such, you should probably look at using Microsoft Visual C++ to build
Ethereal on Windows; it comes with an "nmake" utility that *directly*
uses the "Makefile.nmake" files (obviating the need to create a new
"Makefile.in"), and the fancy IDE stuff in Visual C++ can also be told
that Ethereal is a "Makefile" project, meaning it'll just use the
"Makefile.nmake" file to tell it what to do, rather than requiring all
the project files, blah blah blah.
