Skip to content

Update internal engine toolchain to VS 2019 #48831

@stuartmorgan-g

Description

@stuartmorgan-g

Currently the bots are pulling VS 2017 via gclient to build the Windows engine. This means that errors building with VS 2019, which is what most people would now install, go undetected; currently there are at least some type conversion issues in ANGLE that are causing build errors with 2019 but not 2017.

We should switch to pulling 2019. That change should be straightforward, but we need to fix the build errors first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listengineflutter/engine related. See also e: labels.platform-windowsBuilding on or for Windows specificallyteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions