WME uses custom names for its FFmpeg binaries to differentiate them in telemetry. We need to support both the default FFmpeg binary names and WME's custom FFmpeg binary names in the Media Player sample projects.
What changed?
Updated the Media Player sample projects to support both default and custom FFmpeg binary names
We use wildcards to support customizing the FFmpeg binary names, however, wildcards are not supported in project items for .vcxproj files. To workaround this limitation wildcard items are moved to a target body. See .vcxproj files and wildcards | Microsoft Learn for more info.
Removed the /LTCG linker option for FFmpeg builds since it had no effect
How was the change tested?
I built the FFmpeg binaries with the default names and WME's custom names and verified that Ogg playback in the Media Player samples works successfully in both cases.
Why is this change being made?
WME uses custom names for its FFmpeg binaries to differentiate them in telemetry. We need to support both the default FFmpeg binary names and WME's custom FFmpeg binary names in the Media Player sample projects.
What changed?
How was the change tested?
I built the FFmpeg binaries with the default names and WME's custom names and verified that Ogg playback in the Media Player samples works successfully in both cases.