Stdafx.obj must be linked when using precompiled header

[bdbaddog]

This issue was originally created at: 2009-01-08 07:58:58.
This issue was reported by: csiki.

csiki said at 2009-01-08 07:58:58

Using precompiled header under msvc, you need to link the precompiled header's object as well. If you don't link in (mostly stdafx.obj), then the only forward declared classes in the precompiled header won't be able to see in the debugger. Now you need to do this (as a workaround):

Program(target="test", source=["test.cpp", "stdafx.obj"])

or

Library(target="test", source=["test.cpp", "stdafx.obj"])

gregnoel said at 2009-01-23 01:32:08

Bug party triage. There's no programmatic solution to this problem, so explain in the documentation what to do. Brandon to sync up with Steven and write the necessary prose.

gregnoel said this issue blocks #2292 at 2009-01-23 01:53:34.

[mwichmann]

It says, "There's no programmatic solution", but at the moment mslink actually does force the object file to be linked:

    pch_node = get_pch_node(env, target, source)                               
    if version_num >= 11.0 and pch_node:                                       
        # MSVC 11 and above need the PCH object file to be added to the link line,
        # otherwise you get link error LNK2011.                                
        pchobj = SCons.Util.splitext(str(pch_node))[0] + '.obj'   

(I might argue that maybe should have used $OBJSUFFIX instead of hardcoding .obj even though .obj obviously is correct, but that's a separate question).

So, I wonder if this issue still has unresolved components? That change was added in 9508091 in 2015, which postdates the bug report by over six years, so perhaps Microsoft addressed the same problem by making it mandatory, and we responded by adding this?