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

[Ulf Lamping <ulf.lamping@xxxxxx>]

Hi List!

Playing a bit with the settings in config.nmake to have a solution for 
the pod2html problem:

POD2MAN=$(PERL) pod2man
POD2HTML=$(PERL) pod2html

doesn't work with cygwin, as the scripts cannot be found by the perl 
interpreter.


Now I'm questioning about the general guideline of the tools needed to 
generate the win32 build!

The tools needed to build ethereal and such:

bash, perl, python, flex and bison

Readme.win32 says:
------------------------------------------------------------------------------
Most of those tools are available for Win32 systems as part of the
Cygwin package:

   http://sources.redhat.com/cygwin/

After installing them, you will probably have to modify the config.nmake
file to specify where the Cygwin binaries are installed.

Python for Win32 is available from

   http://www.python.org/
------------------------------------------------------------------------------

In the meantime, a cygwin port of python is also available, which is 
doing fine,
so all required tools are available using cygwin.


To make the first time generation on win32 *as easy as possible*, I 
would tend to do the following:

a.) in "Readme.win32", suggest the user to install all required tools 
from cygwin
b.) set config.nmake to work with the cygwin tools by default

The corresponding settings in config.nmake would look like:
------------------------------------------------------------------------------
PATH=c:\cygwin\bin;$(PATH)

SH=bash
PERL=perl
POD2MAN=$(SH) pod2man
POD2HTML=$(SH) pod2html
PYTHON=env python
LEX=flex
YACC=bison
------------------------------------------------------------------------------

This will not exclude users from using different tools if they are 
installed on their system.

But it makes the default ok, to get a first time build up and running 
without too much confusion.

Regards, ULFL