From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] openh264 (2.3.1)
Date: Mon, 6 Feb 2023 21:22:25 +0900 [thread overview]
Message-ID: <20230206212225.7b6f1362d9be54125bdfc14c@nifty.ne.jp> (raw)
In-Reply-To: <ca1c645f-e3a7-1584-38a7-5b7d8fded5c7@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
On Sun, 5 Feb 2023 16:36:21 +0000
Jon Turney wrote:
> 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.
As Yaakov mentioned, it seems that binary libopenh264 package
cannot be distributed as a cygwin package, so I re-package
it so that it includes only the header files.
Please check attached cygport file.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
[-- Attachment #2: openh264.cygport --]
[-- Type: text/plain, Size: 1624 bytes --]
NAME="openh264"
VERSION=2.3.1
RELEASE=1
CATEGORY="Video"
SUMMARY="H.264 codec library (headers only)"
DESCRIPTION="OpenH264 is a codec library which supports H.264 encoding and decoding. It is suitable for use in real time applications such as WebRTC. This package has only headers. If you need library binary itself, you can download it from https://github.com/cisco/openh264/."
HOMEPAGE="https://www.openh264.org/"
LICENSE="BSD-2-Clause"
ARCH="noarch" # This is noarch because it's just header files.
SRC_URI="${NAME}-headers-${VERSION}.tar.xz"
# Make dummy source file for prep if the cleaned one is not exist.
if [ ! -f ${SRC_URI} ]
then
mkdir ${NAME}-${VERSION}
touch ${NAME}-${VERSION}/dummy
tar acf ${SRC_URI} ${NAME}-${VERSION}
rm -rf ${NAME}-${VERSION}
fi
CYGPORT_USE_UNSTABLE_API=1
src_unpack_hook() {
if [ $(tar tvf ../../../${SRC_URI} | wc -l) -eq 2 ] # Source file is dummy
then
NV=${NAME}-${VERSION}
pushd ..
rm -rf ${NV} # Remove dummy source file.
# Download original source file.
wget https://github.com/cisco/openh264/archive/refs/tags/v${VERSION}.tar.gz
tar xf v${VERSION}.tar.gz
rm -f v${VERSION}.tar.gz
# Make source file which has only necessary header files.
tar acf ../../${NAME}-headers-${VERSION}.tar.xz ${NV}/codec/api/wels/*.h
# Update source directory.
rm -rf ${NV}
tar xf ../../${NAME}-headers-${VERSION}.tar.xz
popd
fi
}
PKG_NAMES="libopenh264-headers"
libopenh264_headers_CATEGORY="Video Devel"
libopenh264_headers_CONTENTS="usr/include"
src_compile() {
:
}
src_install() {
mkdir -p ${D}/usr/include
ln -fs ${S}/codec/api/wels ${D}/usr/include/.
}
next prev parent reply other threads:[~2023-02-06 12:22 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 [this message]
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=20230206212225.7b6f1362d9be54125bdfc14c@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-apps@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).