(In reply to Paul Adenot (:padenot) from comment #12) > Seems plausible yeah. https://searchfox.org/mozilla-central/source/third_party/libwebrtc/modules/video_coding/codecs/interface/libvpx_interface.h#18-21 should be `<>` not `""`. The VPX headers in [libwebrtc](https://searchfox.org/mozilla-central/source/third_party/libwebrtc/) should be redirected to the headers under [third_party/libvpx/vpx](https://searchfox.org/mozilla-central/source/third_party/libwebrtc/third_party/libvpx/vpx). To follow the libwebrtc merge procedure, the vpx headers are silently replaced with "trampoline" headers, which do nothing but include real VPX headers. This makes the libwebrtc-merge process easier without worrying headers' paths.
Bug 1875201 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Paul Adenot (:padenot) from comment #12) > Seems plausible yeah. https://searchfox.org/mozilla-central/source/third_party/libwebrtc/modules/video_coding/codecs/interface/libvpx_interface.h#18-21 should be `<>` not `""`. The VPX headers in [libwebrtc](https://searchfox.org/mozilla-central/source/third_party/libwebrtc/) should be redirected to the headers under [third_party/libvpx/vpx](https://searchfox.org/mozilla-central/source/third_party/libwebrtc/third_party/libvpx/vpx). To follow the libwebrtc merge procedure, the vpx headers are silently replaced with ["trampoline" headers](https://searchfox.org/mozilla-central/rev/961556b584938a694d7df6e7bf25d70253c37060/third_party/libwebrtc/third_party/libvpx/vpx/vpx_encoder.h#19), which do nothing but include real VPX headers. This makes the libwebrtc-merge process easier without worrying headers' paths.