From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] openh264 (2.3.1)
Date: Sun, 5 Feb 2023 16:36:21 +0000 [thread overview]
Message-ID: <ca1c645f-e3a7-1584-38a7-5b7d8fded5c7@dronecode.org.uk> (raw)
In-Reply-To: <20230205173745.cf6aa7153ce8eae1dfd52c4c@nifty.ne.jp>
On 05/02/2023 08:37, 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/
libopenh264 contains a libopenh264.dll file. This doesn't match the
naming convention for cygwin DLLs. This might need patching in the make
machinery somewhere.
next prev parent reply other threads:[~2023-02-05 16:36 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 [this message]
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
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=ca1c645f-e3a7-1584-38a7-5b7d8fded5c7@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).