Github messages for voidlinux
 help / color / mirror / Atom feed
From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nv-codec-header: update to 12.0.16.0.
Date: Sun, 02 Jul 2023 10:56:25 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44781@inbox.vuxu.org> (raw)

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

There is a new pull request by dataCobra against master on the void-packages repository

https://github.com/dataCobra/void-packages nv-codec-headers
https://github.com/void-linux/void-packages/pull/44781

nv-codec-header: update to 12.0.16.0.
#### Testing the changes
- I tested the changes in this PR: **YES**

I've build ffmpeg successfully with this version and also tested streaming with the codec via obs studio with me Nvidia Geforce RTX 2080 Super.

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - x86_64-musl
  - aarch64-musl (crossbuild)
  - armv7l (crossbuild)
  - armv6l-musl (crossbuild)

I'm not sure if I need to set packages to a new revision to make sure it's build with the new headers. I hope somebody can tell me that.

Packages using nv-codec-headers:
 * ffmpeg
 * gnome-remote-desktop
 * handbrake
 * nvidia-vaapi-driver

A patch file from https://github.com/void-linux/void-packages/pull/44781.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nv-codec-headers-44781.patch --]
[-- Type: text/x-diff, Size: 1203 bytes --]

From d02795a9a65691cfed0fd2cc119f566d9807320a Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Sun, 2 Jul 2023 10:49:49 +0200
Subject: [PATCH] nv-codec-header: update to 12.0.16.0.

---
 srcpkgs/nv-codec-headers/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/nv-codec-headers/template b/srcpkgs/nv-codec-headers/template
index 3d422a61e489..251e057f826f 100644
--- a/srcpkgs/nv-codec-headers/template
+++ b/srcpkgs/nv-codec-headers/template
@@ -1,6 +1,6 @@
 # Template file for 'nv-codec-headers'
 pkgname=nv-codec-headers
-version=11.1.5.1
+version=12.0.16.0
 revision=1
 build_style=gnu-makefile
 short_desc="FFmpeg version of headers required to interface with Nvidias codec APIs"
@@ -8,7 +8,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="http://git.videolan.org/?p=ffmpeg/nv-codec-headers.git"
 distfiles="https://github.com/FFmpeg/nv-codec-headers/archive/n${version}.tar.gz"
-checksum=d095fbd56aa93772471a323be0ebe65504a0f43f06c76a30b6d25da77b06ae9c
+checksum=2a1533b65f55f9da52956faf0627ed3b74868ac0c7f269990edd21369113b48f
 
 post_install() {
 	sed -n '4,25p' include/ffnvcodec/nvEncodeAPI.h > LICENSE

             reply	other threads:[~2023-07-02  8:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02  8:56 dataCobra [this message]
2023-07-05 14:32 ` [PR PATCH] [Updated] " void-linux
2023-07-10  7:49 ` dataCobra
2023-07-10 18:04 ` dataCobra
2023-07-10 18:11 ` dataCobra
2023-07-15  8:37 ` dataCobra
2023-07-16  9:16 ` dataCobra
2023-07-21  5:15 ` dataCobra
2023-07-24  6:36 ` dataCobra
2023-10-05 15:42 ` dataCobra
2023-10-17  0:07 ` tm512
2023-10-17 12:00 ` dataCobra
2023-10-17 12:08 ` [PR PATCH] [Updated] " dataCobra
2023-10-17 20:55 ` nv-codec-header: update to 12.1.14.0 tm512
2023-11-08 14:15 ` [PR PATCH] [Updated] " dataCobra
2023-11-08 14:18 ` [PR PATCH] [Updated] nv-codec-header: update to 12.0.16.1 dataCobra
2024-02-07  1:44 ` github-actions
2024-02-07 14:09 ` [PR PATCH] [Updated] " dataCobra
2024-05-09  1:46 ` github-actions

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44781@inbox.vuxu.org \
    --to=datacobra@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).