> I can unpack ethereal-0.8.18 and build it sucessfully on my NT box,
> but I can not do the same from the source tree.
>
> I pulled the source tree out of CVS (actually 2-3 days ago) and ran
> autogen.sh on a Solaris box to generate all the various config stuff.
If you have an NT box with all the tools mentioned in the "README.win32"
file, you should just be able to
modify the "config.nmake" file to point to the places where
GTK+, GLib, WinPcap, Perl, Python, Flex, and Berkeley YACC or
Bison are located;
build with "nmake -f makefile.nmake";
without bothering with "autogen.sh" - i.e., autogen.sh isn't necessary in
that case.
If you have an NT box that *doesn't* have those tools, autogen.sh isn't
*sufficient* - you'd also have to do the build on Solaris so as to
generate all the ".c" files that are generated from other files.
> I can't find the reference now, but I thought I had read that if you
> didn't have automake etc. that configuring on a UNIX box was the work
> around.
Automake etc. apply, currently, only on UNIX; you might find that you
can build with a more UNIXy platform, such as Cygwin, using the
Makefiles generated from automake and autoconf, but, as README.win32
says:
Instructions for Cygwin
-----------------------
No one has ever compiled Ethereal entirely with Cygwin. It should not
be difficult, however. This spot is reserved for your instructions on
how to compile Ethereal with Cygwin.
To build with MSVC++, you don't need automake or autoconf, as none of
that stuff is used.
However, you *do* need Perl, Python, Flex, Berkeley YACC or Bison, and
some other tools; if you don't have them on your Windows box, you'd need
to run them on a UNIX box, and running them isn't part of *configuring*,
it's part of *compiling*, so you have to *compile* on UNIX if you don't
have those tools. (*I* do Windows compiles on a box that has all the
tools....)
