["Graham Bloice" <graham.bloice@xxxxxxxxxxxxx>]

> > But this doesn't explain why executable shouldn't be linked
> with libcmt.  As
> > makefile.nmake sets the compiler flag /MT this implies that the
> executable
> > should be linked with libcmt.
>
> Hmm, you're right. I have fought linker errors related to this
> for a week a couple of months ago. It is really frustrating.
>
> What kind of linker errors do you get?

Unresolved symbols for all the C runtime functions.  AFAIK /MT means link
with libcmt, I can't see any reason for doing anything differently.  There
may be scope for putting different libraries in a /NODEFAULTLIB option, but
I suppose that would only be to prevent inadvertent linking with the wrong
function.  Without the NODEFAULTLIB option everything links and runs fine on
both Win98 and NT 4.0.

GB