Skip to content

Investigate and clarify better /Z7 necessity for MSVC 2010 and higher when using PCH #21

@m-7761

Description

@m-7761

I think the new note on the /Z7 flag gives the impression that this is solution aimed at supporting 2010 (at the expense of newer editions) whereas it's really a problem that begins with 2010 and so far (at least) has no end. I.e. it applies equally to likely the most recent version of Visual Studio, whatever it is.

I spent a lot of time trying to put the PDB file in a different location, and link to it. But from what I can recall, the XML files that the compiler uses to save project information has inconsistent escaping both in Visual Studio and in CMake also. So it seemed like an intractable problem, which just magically goes away with /Z7. Even when I would make ground on the problems, and new one would always emerge. Until I think I was left with nowhere to go but to think outside the box.

EDITED: I seem to recall a problem with sharing PDB files between build-targets also. Which went beyond their early deletion. I think that the deletion is so draconian BTW because it's a foregone conclusion that sharing, and therefore referencing an external PDB is not even a possibility. Unfortunately, I cannot remember a lot of the details. I did speak on some of these things in the Kitware issue-tracker at the time, but only inadvertently.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions