From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Cc: Yaakov Selkowitz <yselkowitz@cygwin.com>
Subject: Re: [ITP] openh264 (2.3.1)
Date: Sun, 5 Feb 2023 22:11:09 -0700 [thread overview]
Message-ID: <c05a426e-d4ed-f16d-9113-6fc4788e39e4@Shaw.ca> (raw)
In-Reply-To: <e73235bda50edbfc9b5f51516fe816c14e17c8d0.camel@cygwin.com>
On 2023-02-05 19:44, Yaakov Selkowitz via Cygwin-apps wrote:
> On Sun, 2023-02-05 at 17:37 +0900, Takashi Yano via Cygwin-apps wrote:
>> I would like to propose new package openh264, which is
>> a H264 video codec library. This is needed by ffmpeg
>> package I had proposed, and also provided for ffmpeg-free
>> package in fedora.
>>
>> I already prepared the package at the following location.
>>
>> https://tyan0.yr32.net/cygwin/x86_64/release/openh264/
> Unfortunately, this cannot be included in the Cygwin distribution. Cisco's
> patent license only covers binaries they distribute. Fedora has a special
> arrangement with Cisco where they build their RPMs on Fedora infrastructure,
> but the packages are hosted by Cisco in a separate repository.
http://www.openh264.org/
"Cisco has taken their H.264 implementation, and open sourced it under BSD
license terms. Development and maintenance will be overseen by a board from
industry and the open source community. Furthermore, we have provided a binary
form suitable for inclusion in applications across a number of different
operating systems, and make this binary module available for download from the
Internet. We will not pass on our MPEG-LA licensing costs for this module, and
based on the current licensing environment, this will effectively make H.264
free for use on supported platforms."
http://blogs.cisco.com/collaboration/open-source-h-264-removes-barriers-webrtc
http://blogs.cisco.com/collaboration/open-source-h-264-removes-barriers-webrtc
https://github.com/cisco/openh264
"For Windows Builds
"make" must be installed. It is recommended to install the Cygwin and "make"
must be selected to be included in the installation. After the installation,
please add the Cygwin bin path to your PATH.
License
BSD, see LICENSE file for details."
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-02-06 5:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 8:37 Takashi Yano
2023-02-05 16:36 ` Jon Turney
2023-02-06 12:22 ` Takashi Yano
2023-02-06 2:44 ` Yaakov Selkowitz
2023-02-06 5:11 ` Brian Inglis [this message]
2023-02-06 5:16 ` Yaakov Selkowitz
2023-02-06 5:25 ` Takashi Yano
2023-02-09 12:02 ` Takashi Yano
2023-02-10 4:35 ` Yaakov Selkowitz
2023-02-10 5:05 ` Takashi Yano
2023-02-10 5:18 ` Takashi Yano
2023-02-10 5:25 ` Takashi Yano
2023-02-13 18:30 ` Jon Turney
2023-02-13 19:03 ` Brian Inglis
2023-02-14 9:11 ` Takashi Yano
2023-02-14 11:02 ` ASSI
2023-02-14 12:28 ` Takashi Yano
2023-02-14 16:41 ` ASSI
2023-02-14 21:21 ` Takashi Yano
2023-02-16 19:24 ` Jon Turney
2023-02-17 8:49 ` Takashi Yano
2023-02-19 15:37 ` Jon Turney
2023-02-20 8:55 ` Takashi Yano
2023-02-21 14:11 ` Jon Turney
2023-02-22 3:33 ` Takashi Yano
2023-02-23 12:54 ` Jon Turney
2023-02-24 9:16 ` Takashi Yano
2023-02-06 22:40 ` Lee
2023-02-07 5:19 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c05a426e-d4ed-f16d-9113-6fc4788e39e4@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-apps@cygwin.com \
--cc=yselkowitz@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).