Thanks
I found (from microsoft.public.vc.debug) that "msdev ethereal.exe" also
works to get things started with vc++ 6.
adns.dll & etc from the adns-1.0-win32-01.zip file from the ethereal
website linked fine for me; (makefile.nmake just uses the adns_dll.lib to
link against; no compile needed)
A very quick test to read a sniffer .cap file does seem to the indicate
that the ethereal.exe I've created is OK.
I'm now working my way thru the code to understand the overall structure of
the program and where to put the breakpoints I need; I'm going to see why
certain sniffer files don't seem to quite read in properly. I'm also going
to look at some X-Windows protocol decode problems I've encountered using
Windows Ethereal.
Bill Meier
>To compile, you generally just need to make a makefile project.
>
>If you go to Project->Settings, you can setup the debugging options. By
>default, it wants the executable to be in the Debug folder. You have to
>make sure that either all the DLL's are in your path (either just
>copying them all to one place like the debug folder or modifying your
>path). The normal things to go wrong are, it can't find the executable,
>or it can't find a DLL. Everything else should work by default with the
>makefile.nmake provided...
>
>P.S.
>Did you get ethereal to run? Did you get the adns dll to compile? A
>blind use of the project inside the adns source provided by ethereal
>didn't work for me...
> I've successfully compiled and linked ethereal-0.9.13 using vc++ 6.
>
> (Interesting experience: obtain/install vc++ 6; DL/install/setup
> cygwin/flex/bison/python; dl ethereal_src; edit config.nmake, etc, etc).
>
> I'm just learning my way around vc++ 6 so I would very much appreciate a
> hint as to how get the debugger (msdev.exe ??) to work with the ethereal
> .exe/.pdb generated by nmake.
>
> TIA
>
> Bill Meier
>