From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: add compile time check for outputRecoveryPointSEI for HEVC
Date: Tue, 4 Feb 2025 10:57:29 -0300
Message-ID: <00b43a0a-75d1-4102-9e1b-1bd54e441b57@gmail.com> (raw)
In-Reply-To: <c4b9bdb4-8425-e315-7e7b-d26c54151fa1@martin.st>
[-- Attachment #1.1.1: Type: text/plain, Size: 969 bytes --]
On 2/4/2025 10:52 AM, Martin Storsjö wrote:
> On Tue, 4 Feb 2025, James Almer wrote:
>
>>> Thanks, this does indeed seem to fix compilation in my setup.
>>
>> Applied.
>>
>> Why don't don't just update the headers? Is it a system package
>> provided by your distro?
>
> I guess I could, but as long as I don't have a pressing need to, just
> staying with the current version is easiest. Do the headers major
> version need to match the installed drivers/proprietary nvidia libs? (In
> my setup, the drivers/nvidia libs are distributed entirely separately -
> touching that bit is a lot of effort.)
No, they don't need to match afaik. The headers are meant to be ABI
backwards compatible (hence all the reserved fields).
I was just wondering if the headers were provided by your distro or not
(Given they are compile time deps and not runtime), and looking now at
the package lists in some, i see they are, so disregard my question.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-02-04 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 13:31 James Almer
2025-02-04 13:38 ` Martin Storsjö
2025-02-04 13:41 ` James Almer
2025-02-04 13:52 ` Martin Storsjö
2025-02-04 13:57 ` James Almer [this message]
2025-02-04 14:00 ` Martin Storsjö
2025-02-04 14:58 ` Zhao Zhili
2025-02-04 15:36 ` Timo Rothenpieler
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=00b43a0a-75d1-4102-9e1b-1bd54e441b57@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git