> > With the latest makefile.nmake I get heaps of link errors due to the
> > /NODEFAULTLIB:libcmt entries at the end of the linker command line. Can
> > anyone tell me why the're there?
>
> The new WinPcap library is multi-threaded. Follow this e-mail thread:
>
> http://ethereal.zing.org/lists/ethereal-dev/200004/msg00007.html
>
> Guy added /MD for the C compiler flags, but then had problems
> with multiple symbol definitions in the C libraries:
The latest config.nmake has /MT for the compile flags as detailed in the
thread, and this is what I would expect to have to use to link with WinPcap
if it's flags include /MT or /MD. Using /MT means that the executable has
to link with libcmt, rendering the /NODEFAULTLIBS option incorrect.
> http://ethereal.zing.org/lists/ethereal-dev/200004/msg00046.html
This message is related to the Gryphon plug-in which I can't, unfortunately,
test at all, although it does build a DLL on my system. It would appear,
for the 0.8.9 release, that the Gryphon DLL is built with the same compile
flags as all the other modules. For a DLL I would expect to use /MD instead
of /MT. Maybe this was the source of Guy's problems?
> That's why he put in the /NODEFAULTLIB:libcmt flag for the linker.
> When I compile the win32 binaries, though, I don't use the Makefiles,
> but a different build system, so I haven't checked their veracity lately.
Interesting. What is your build environment?
> > Also I have a patch for makefile.nmake to improve the
> dependencies but it
> > doesn't appear to be in CVS so I can't diff against the latest. Am I
> > missing something?
>
> The file Makefile.nmake (note the case) is indeed in CVS.
Too much Win32 on my part I think, keep forgetting about case.
GB