Re: Understanding noopenh264 in Fedora

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Sat, May 25 2024 at 12:55:05 PM +00:00:00, Byoungchan Lee via devel 
> <devel(a)lists.fedoraproject.org&gt; wrote:

>Yes!

Thanks for the confirmation, Michael!

> No. That's an example of what you no longer need to do now that 
> noopenh264 is available in Fedora. Previously, dlopen() was required 
> since you cannot build depend on the real openh264. Now, you can build 
> depend on noopenh264 instead.

I see.

To clarify, Chromium and WebRTC use source-embedded OpenH264, which is
located in the third_party/openh264 directory. While this is okay
for Google, as they likely have a license agreement with other patent
holders, Fedora needs to use the Cisco's OpenH264 binary package.

>From what I understand, even with noopenh264, Chromium and WebRTC's
codebase will still need modification to use Fedora's OpenH264 or
noopenh264 package.

What do you think?
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux