From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_cuda: check that the SDK defines cuCtxGetCurrent()
Date: Fri, 6 Oct 2023 15:07:41 +0200
Message-ID: <331c777a-9800-43f0-a301-667dded6b005@rothenpieler.org> (raw)
In-Reply-To: <CA+anqdy5+kxNE5i7BN4Gif88+qKPCDj-nQvy2MHVr-LEDonejQ@mail.gmail.com>
On 06/10/2023 14:29, Hendrik Leppkes wrote:
> On Sun, Oct 1, 2023 at 1:39 PM Timo Rothenpieler <timo@rothenpieler.org> wrote:
>>
>> On 01.10.2023 04:06, James Almer wrote:
>>> Fixes compilation after 05f8b2ca0f7e28775837a572c65ce9218f534ee2
>>
>> It's expected behaviour to break compilation with random inter-release
>> versions of ffnvcodec.
>> It's only reliable exactly on release versions.
>>
>
> But isn't the point that there is no release version of ffnvcodec that
> I can use to build this?
> And that it has no check to limit building it, and will always fail
> with release versions?
I don't understand what you mean.
Right now, it only works with nv-codec-headers master.
I will make a new release there very soon.
_______________________________________________
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:[~2023-10-06 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 2:06 James Almer
2023-10-01 2:24 ` James Almer
2023-10-01 11:39 ` Timo Rothenpieler
2023-10-06 12:29 ` Hendrik Leppkes
2023-10-06 13:07 ` Timo Rothenpieler [this message]
2023-10-06 13:31 ` Hendrik Leppkes
2023-10-06 13:47 ` Timo Rothenpieler
2023-10-06 16:43 ` Hendrik Leppkes
2023-10-07 10:34 ` 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=331c777a-9800-43f0-a301-667dded6b005@rothenpieler.org \
--to=timo@rothenpieler.org \
--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