The Boost regression tests require separate compilation and link steps. For Win32 Intel 7.0 with VC++ 7.0, the following switch combination worked fine:
For Win32 Intel 7.1 with VC++ 7.1, the same setup results in unresolved externals on standard library components. If the compile /MDd switch is removed, the unresolved externals go away, and the resulting .exe runs fine.
What is the correct workaround? I assume removing the /MDd switch is only glossing over the problem, not fixing it?
7.1 on Win32 compile/link switch clash
The Boost regression tests require separate compilation and link steps. For Win32 Intel 7.0 with VC++ 7.0, the following switch combination worked fine:
icl -c /Z7 /MDd ...
xilink /DEBUG /subsystem:console ...
For Win32 Intel 7.1 with VC++ 7.1, the same setup results in unresolved externals on standard library components. If the compile /MDd switch is removed, the unresolved externals go away, and the resulting .exe runs fine.
What is the correct workaround? I assume removing the /MDd switch is only glossing over the problem, not fixing it?
--Beman Dawes