public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] nv-codec-headers (11.1.5.2)
Date: Thu, 9 Feb 2023 20:58:42 +0900	[thread overview]
Message-ID: <20230209205842.1dc4c97f6e2853bde162a12b@nifty.ne.jp> (raw)
In-Reply-To: <20230205173811.04ea62ef88b45d6c4716aa14@nifty.ne.jp>

[-- Attachment #1: Type: text/plain, Size: 491 bytes --]

On Sun, 5 Feb 2023 17:38:11 +0900
Takashi Yano wrote:
> I would like to propose new package nv-codec-haeders, which is
> codec-headers for nvidia GPUs. 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/noarch/release/nv-codec-headers/

cygport file is updated as attached. (just add comment)

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

[-- Attachment #2: nv-codec-headers.cygport --]
[-- Type: text/plain, Size: 574 bytes --]

NAME="nv-codec-headers"
VERSION=11.1.5.2
RELEASE=1
LICENSE="MIT"
CATEGORY="Devel"
SUMMARY="FFmpeg version of Nvidia Codec SDK headers"
DESCRIPTION="FFmpeg version of headers required to interface with Nvidias codec APIs."
HOMEPAGE="https://github.com/FFmpeg/nv-codec-headers"
ARCH="noarch" # This is noarch because it's just header files.
SRC_URI="https://github.com/FFmpeg/nv-codec-headers/archive/refs/tags/n${VERSION}.tar.gz"

SRC_DIR="${NAME}-n${VERSION}"
src_compile() {
	cd ${B}
	ln -sf ${S}/Makefile .
	ln -sf ${S}/ffnvcodec.pc.in .
	ln -sf ${S}/include .
	cygmake
}

      reply	other threads:[~2023-02-09 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05  8:38 Takashi Yano
2023-02-09 11:58 ` Takashi Yano [this message]

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=20230209205842.1dc4c97f6e2853bde162a12b@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).