November 7th, 2001
Wednesday
----- Original Message -----
From: "Brian Hook" <bri...@py...>
> Thanks to everyone for their suggestions. I did a DUMPBIN /ALL on some
> of the problematic OBJ files to find out that they were STILL linking to
> MSVCRTD.LIB (!). Grrr. As it turns out, you can specify the linkage
> PER FILE (not just per project). So even if all your projects are set
> to, say, Multithreaded Debug, a file within a project might be set to
> Multithreaded Debug DLL (which is what happened in this case). Once
> that was found and I fixed the two files that were set this way (no idea
> how they got that way), all problems went away.
I guess if you do incremental builds, and you changed
the build setting from single-threaded to
multi-threaded, then the only files to experience
the new settings would be files built after
the settings change. If none of the files upon
which a source file depends is modified, and
you rarely do a clean build, the stale object
file could stick around!
Maybe changing the setting regarding which
version of the C run-time library to use
should bring up a dialog box that warns
you that a clean rebuild is necessary,
and offers to delete all object files
immediately! :-)
--- Colin
|