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...
Anyway, I took the liberty and added same versioning to CUDA API as that for Video Codec SDK API. I picked CUDA API v. 11.4 for no particular reason, simply because nvcodec-headers doesn't use latest features and minimal required driver (530+) supports that CUDA version. Please LMK if there's another approach to CUDA API versioning I must follow. чт, 14 сент. 2023 г. в 13:00, Timo Rothenpieler <t...@rothenpieler.org>: > This will either need updates to the ffnvcodec version checks in > configure, to ensure the new symbol always exists, or some kind of more > selective check to only build those parts of the code if the new > function is present. > > As it is now, this would fail all current builds. > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". > -- -- С уважением, Роман Арзуманян. Главный разработчик по направлению видео аналитики.
0001-libavutil-hwcontext_cuda-option-added-to-use-context.patch
Description: Binary data
0001-Add-cuCtxGetCurrent-function.patch
Description: Binary data
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
