Bugzilla

From cpearce

> I'm working on getting Encrypted Media Extensions (EME) running in Firefox on Windows on ARM64. EME is the mechanism that sites like Netflix and Hulu use to play DRM protected video on the web platform.
>
> The video is decrypted by a Content Decryption Module (CDM) plugin, which in this case is the Widevine CDM DLL provided by Google, which is loaded by and runs in a sandboxed child process inside the plugin-container.exe binary.
>
> We think the shortest path to making Netflix work in Firefox on Windows on ARM is to run the x86 Widevine DLL inside an x86 plugin-container.exe as a child process of an aarch64 Firefox parent process. I have gotten this working in a local build, playing Netflix even.
>
> To make this work, among other things, I had to build Firefox twice; once in aarch64, and a second time for x86, and copy the relevant x86 binaries into a subdirectory of the aarch64 build. This is where your team comes in. I don't know how to make the build system do this by itself. Can someone on your team help us?
>
> Given that we expect/hope this solution to be temporary, Anthony suggested that the easiest and quickest path forward may be to just download the x86 binaries (and a couple of other needed files) which matches the version of mozilla-central being built for aarch64 via the artifact build mechanism at build time, thereby avoiding building *everything* for a second time altogether. This isn't entirely satisfying, but since we hope that this is a temporary solution, and we'd like to ship ASAP, this might be acceptable. You or the people on your team may be able to find a better way.

Timeframe is FF 68

----
We discussed in our team meeting today

Difficult to build both as part of the build
Taskcluster delay if you depend on x86 build for aarch64
First approach would be to to build as a host program.
If this doesn't work, build w/o x86 plugin container, combine plugin container at a later time in build, need releng support for that
Do we need to test on m-c? Or not? (My understanding that testing for aarch64 builds was still under development)