Sources not recognised when debugging in VS Code on Windows about xash3d-fwgs HOT 5 CLOSED

Can you try to recompile engine completely by passing -j1 to Waf? There is a bug, which causes PDB file race condition to multicore systems.

from xash3d-fwgs.

Wow, that actually did solve it. Thank you!

Is there anything that could be done regarding the /MDd switch and the other similar ones? I don't know very much about how the MS compile tools work or what options are appropriate for GoldSrc compatibility, but I do remember some of them existing specifically to allow multiple concurrent writes to PDB files.

from xash3d-fwgs.

pdb files does not work for me. Maybe it is broken?

from xash3d-fwgs.

Ideally, we don't need /MDd or /MTd option by default in current debug build type, as it supposed to behave similar to release builds. MDd/MTd links to debug version of MSVCRT and there may be difference.

And yeah, complete fix of this issue is passing a /Fd key to compiler and set pdb path to linker. To achieve that, a taskgen method must be implemented somewhere in our main wscript as suggested by Waf author.

This happens because we have multiple targets and when waf is linking one target and beggining to compile another, the same vcxxx.pdb file is being accessed. I don't know how to reproduce this, as it's a race condition and may happen or may not.

from xash3d-fwgs.

Should be fixed with b1406e8. Re-open if the problem appears again.

from xash3d-fwgs.