12
atheist
2y

Visual Studio 2022 compiles our internal c++ cmake project as a mix of x86 and x86_64 binaries, then fails to link.

VS 2019 correctly compiles everything as x86_64.

No idea why. And, obviously, it's not a documented problem.

Comments
  • 7
    @jespersh LOL the first moron answer is just what you'd expect in an MS forum. Quite a miracle that it wasn't as dumb as "reboot, reinstall Windows".
  • 2
    Weird/odd quirks with VS2022. Not sure what patch did it, but developing in Blazor WASM is getting painful. VS hits 4GB of memory usage and I'm not really doing anything.
  • 2
    @Fast-Nop > "the first moron answer "

    Microsoft must hand out MSFT's like pez candy.

    He (or she?) didn't even read the question.
  • 0
    @jespersh isn't that the reverse problem? That it should be doing x86 and sometimes doing x86_64? So... That one ain't me. I didn't bother trying to fix anything, documented the madness and fixed the problems with GCC.
Add Comment