> > The directions for compiling Ethereal from the command-line are spot on
> > and, in my experience, work as advertised. To my knowledge, there is
> > not an official Developer Studio project file for Ethereal. I imagine
> > part of the reason for it not being in the tree is that it would be
> > difficult to keep the UNIX build scripts in sync with the Win32 project
> > file.
>
> Yes, that'd require manual updates to the project file, as not everybody
> adding source files to Ethereal has MSVC++. It is possible to manually
> update project files - I've done that for tcpdump and libpcap when
> adding files (the current CVS version includes stuff from WinDump and
> WinPcap) - but it's probably more error-prone.
>
> I also don't know how well MSVC++ handles generating .c and .h files
> from other files, as we do for some source files.
>
In the distant past I did generate a project file and workspace for
Ethereal. It also included project files to rebuild all the ancillary
libraries (gtk et al) as well with debug info. I didn't send it back to the
list as project files must have absolute paths in them, and so it was OK for
my oddball setup, but not very general purpose. The project used custom
build rules to generate all the required files.
If we agreed a standard layout for a windows dev environment, probably based
on the C: drive, then I could look into it again. Unfortunately my original
efforts have hit the bit bucket.
Graham Bloice
