From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Cc: Yaakov Selkowitz <yselkowitz@cygwin.com>
Subject: Re: [ITP] openh264 (2.3.1)
Date: Thu, 9 Feb 2023 21:02:26 +0900 [thread overview]
Message-ID: <20230209210226.1f2027bd7ca62ecee1782e6c@nifty.ne.jp> (raw)
In-Reply-To: <20230206142523.23a3b4b02cf8a8c5ef54b9f0@nifty.ne.jp>
Hi Yaakov,
On Mon, 6 Feb 2023 14:25:23 +0900
Takashi Yano wrote:
> On Mon, 06 Feb 2023 00:16:45 -0500
> Yaakov Selkowitz via Cygwin-apps <cygwin-apps@cygwin.com> wrote:
> > On Sun, 2023-02-05 at 22:11 -0700, Brian Inglis wrote:
> > > On 2023-02-05 19:44, Yaakov Selkowitz via Cygwin-apps wrote:
> > > > 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."
> >
> > This is exactly the point. Cisco paid for a license, but that license is
> > limited to binaries they distribute. Unfortunately, I doubt that Cisco will
> > do the same for Cygwin.
>
> OK. How about distributing only headers as cygwin package
> for building ffmpeg?
Ping?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2023-02-09 12:02 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
2023-02-06 5:16 ` Yaakov Selkowitz
2023-02-06 5:25 ` Takashi Yano
2023-02-09 12:02 ` Takashi Yano [this message]
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=20230209210226.1f2027bd7ca62ecee1782e6c@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).