Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: Roman Arzumanyan <r.arzumanyan@visionlabs.ai>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] libavutil/hwcontect_cuda: add option to use current CUDA context
Date: Thu, 14 Sep 2023 15:32:45 +0200
Message-ID: <85533a04-015d-484a-a69d-300506ef680e@rothenpieler.org> (raw)
In-Reply-To: <CAJZRZV=kar3ox1qcXHs+wKNRgJrhage5JL9jUmASjHT+jtDo_g@mail.gmail.com>

On 14/09/2023 15:29, Roman Arzumanyan wrote:
> Thanks for the swift reply Timo, you're right about versioning.
> However, I didn't find any existing CUDA API versioning macro unlike 
> that for Video Codec SDK API.
> So I basically did the same thing as that in previous commit to 
> nvcodec-headers which barely adds new function pointer...

The usual approach is to rely on the ffnvcodec version.
Whenever you need a function from a specific version, bump the versions 
in configure to the current version from git master and all the 
respective old branches, since that will be the version of the next release.
_______________________________________________
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".

  reply	other threads:[~2023-09-14 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14  7:26 Roman Arzumanyan
2023-09-14 10:00 ` Timo Rothenpieler
2023-09-14 13:29   ` Roman Arzumanyan
2023-09-14 13:32     ` Timo Rothenpieler [this message]
2023-09-14 14:03 ` Anton Khirnov
     [not found]   ` <CAJZRZVm1yM0n5ri-X7FZq1A+X2E1GmpsdDu6hQN5t3wpjbY6=A@mail.gmail.com>
     [not found]     ` <7984201b-83b4-4d51-9d5b-d70e958bf399@rothenpieler.org>
2023-09-14 16:52       ` Roman Arzumanyan
2023-09-14 16:54         ` Timo Rothenpieler
2023-09-19  8:18         ` Roman Arzumanyan
2023-09-19 12:25           ` Timo Rothenpieler
2023-09-28 17:27         ` 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=85533a04-015d-484a-a69d-300506ef680e@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=r.arzumanyan@visionlabs.ai \
    /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