Open Bug 1371439 Opened 7 years ago Updated 2 years ago

aom: update windows config to vs15

Categories

(Core :: Audio/Video: Playback, enhancement, P3)

Product:
Core
Component:
Audio/Video: Playback
Type:
enhancement

Tracking

()

People

(Reporter: rillian, Unassigned)

References

Details

When we transition to building with Visual Studio 2017, we should bump the aom (and libvpx?) configure targets to vs15. Note we may have to add such targets upstream.
Depends on: vs2017
I just want to make sure I understand the depends/blocks relationship correctly.

Is this a thing that has to happen before we can flip the switch to VS2017? Or an opportunistic thing that would become possible by switching to VS2017 (e.g. better codegen or something)?
Flags: needinfo?(giles)
It is opportunistic. The old one seems to work fine, but if upstream offers a more tailored config it seems prudent to use it.
Flags: needinfo?(giles)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.