From: Timo Rothenpieler <timo@rothenpieler.org>
To: Zhao Zhili <quinkblack@foxmail.com>,
FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: add compile time check for outputRecoveryPointSEI for HEVC
Date: Tue, 4 Feb 2025 16:36:29 +0100
Message-ID: <9cb357e0-9cef-4d5a-96b1-e5e4dac8a3f0@rothenpieler.org> (raw)
In-Reply-To: <tencent_05AFB63985C095B6586BB603FD68427DBA0A@qq.com>
On 04/02/2025 15:58, Zhao Zhili wrote:
>
>> On Feb 4, 2025, at 22:00, Martin Storsjö <martin@martin.st> wrote:
>>
>> On Tue, 4 Feb 2025, James Almer wrote:
>>
>>> No, they don't need to match afaik. The headers are meant to be ABI backwards compatible (hence all the reserved fields).
>>
>> Right, then there's probably less concern about updating them.
>>
>>> 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.
>>
>> In my case I actually don't use distro provided headers, I use a manually installed set, but I don't really touch it unless I need to.
>
> How about put a copy of nv-codec-headers inside ffmpeg source tree?
> So it can always up to date and easy to handle the dependency (I encountered some trouble on Unix path vs Window path with ffnvcodec.pc in msys environment).
> What are the disadvantages of this method?
That's how it's been in the past, and I have no plans to go back to that.
It forces everyone to use bleeding edge drivers whenever we bump the
headers, which in some distros is outright impossible.
Outsourcing the headers enabled us to build modern FFmpeg with support
for old drivers, just sacrificing modern features.
_______________________________________________
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".
prev parent reply other threads:[~2025-02-04 15:36 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
2025-02-04 14:00 ` Martin Storsjö
2025-02-04 14:58 ` Zhao Zhili
2025-02-04 15:36 ` Timo Rothenpieler [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=9cb357e0-9cef-4d5a-96b1-e5e4dac8a3f0@rothenpieler.org \
--to=timo@rothenpieler.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=quinkblack@foxmail.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
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