From: epirat07@gmail.com To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: gnattu <gnattuoc@me.com> Subject: Re: [FFmpeg-devel] [PATCH v2] avutil/hwcontext_videotoolbox: Check CVBufferCopyAttachments during configure Date: Mon, 22 Jul 2024 10:55:48 +0200 Message-ID: <5347F855-9775-4BD6-82B1-52B4A53B3DFD@gmail.com> (raw) In-Reply-To: <20240721224755.19964-1-gnattuoc@me.com> On 22 Jul 2024, at 0:47, gnattu via ffmpeg-devel wrote: > The __builtin_available function does not do compile time check > for the availablity of the CVBufferCopyAttachments function > which will fail the build. Check the availability during configure. > > Signed-off-by: Gnattu OC <gnattuoc@me.com> > --- > configure | 2 ++ > libavutil/hwcontext_videotoolbox.c | 12 +++++------- > 2 files changed, 7 insertions(+), 7 deletions(-) > > diff --git a/configure b/configure > index f6f5c29fea..54171dd4e5 100755 > --- a/configure > +++ b/configure > @@ -2366,6 +2366,7 @@ SYSTEM_FUNCS=" > clock_gettime > closesocket > CommandLineToArgvW > + CVBufferCopyAttachments > fcntl > getaddrinfo > getauxval > @@ -6684,6 +6685,7 @@ enabled videotoolbox && { > check_func_headers CoreVideo/CVImageBuffer.h kCVImageBufferColorPrimaries_ITU_R_2020 "-framework CoreVideo" > check_func_headers CoreVideo/CVImageBuffer.h kCVImageBufferTransferFunction_ITU_R_2020 "-framework CoreVideo" > check_func_headers CoreVideo/CVImageBuffer.h kCVImageBufferTransferFunction_SMPTE_ST_428_1 "-framework CoreVideo" > + check_func_headers CoreVideo/CVBuffer.h CVBufferCopyAttachments "-framework CoreVideo" > } > Thanks for the fix and sorry for breaking this. I am not too keen on adding a configure check just for that, as if we do that for all partially available function it will make configure even slower than it already is. I have a fix for this ready testing for the right SDK conditionals (I only did not catch it before because the way the SDK annotations work nowadays do not seem to properly honor when I set my own __MAC_OS_X_VERSION_MAX_ALLOWED define…) so I will need to actually test this on an old enough SDK just to be sure, this time… Then again, if others prefer doing it with configure tests, I am ok with that as well. > enabled metal && test_cmd $metalcc -v || disable metal > diff --git a/libavutil/hwcontext_videotoolbox.c b/libavutil/hwcontext_videotoolbox.c > index ab7556936d..c55d478004 100644 > --- a/libavutil/hwcontext_videotoolbox.c > +++ b/libavutil/hwcontext_videotoolbox.c > @@ -592,15 +592,13 @@ static int vt_pixbuf_set_colorspace(void *log_ctx, > (TARGET_OS_IOS && __IPHONE_OS_VERSION_MAX_ALLOWED >= 100000) > if (__builtin_available(macOS 10.8, iOS 10, *)) { > CFDictionaryRef attachments = NULL; > +#if HAVE_CVBUFFERCOPYATTACHMENTS > if (__builtin_available(macOS 12.0, iOS 15.0, *)) > attachments = CVBufferCopyAttachments(pixbuf, kCVAttachmentMode_ShouldPropagate); > -#if (TARGET_OS_OSX && __MAC_OS_X_VERSION_MIN_REQUIRED <= 120000) || \ > - (TARGET_OS_IOS && __IPHONE_OS_VERSION_MIN_REQUIRED <= 150000) > - else { > - CFDictionaryRef tmp = CVBufferGetAttachments(pixbuf, kCVAttachmentMode_ShouldPropagate); > - if (tmp) > - attachments = CFDictionaryCreateCopy(NULL, tmp); > - } > +#else > + CFDictionaryRef tmp = CVBufferGetAttachments(pixbuf, kCVAttachmentMode_ShouldPropagate); > + if (tmp) > + attachments = CFDictionaryCreateCopy(NULL, tmp); > #endif > if (attachments) { > colorspace = CVImageBufferCreateColorSpaceFromAttachments(attachments); > -- > 2.39.3 (Apple Git-146) > > _______________________________________________ > 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". _______________________________________________ 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:[~2024-07-22 8:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-21 22:47 gnattu via ffmpeg-devel 2024-07-22 8:55 ` epirat07 [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=5347F855-9775-4BD6-82B1-52B4A53B3DFD@gmail.com \ --to=epirat07@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=gnattuoc@me.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