From: Gnattu OC via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Gnattu OC <gnattuoc@me.com> Subject: Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_videotoolbox: Fix build with older SDKs Date: Mon, 22 Jul 2024 06:48:50 +0800 Message-ID: <9411EBF1-04ED-4B7C-8B67-EAA518B2BCBC@me.com> (raw) In-Reply-To: <CAEB8E61-10E6-42DB-8A3C-A567FAE0149E@me.com> > On Jul 22, 2024, at 06:45, Gnattu OC via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote: > > > >> On Jul 22, 2024, at 06:04, Sean McGovern <gseanmcg@gmail.com> wrote: >> >> Hi Marvin, >> >> >> On Tue, Jul 9, 2024, 10:47 Marvin Scholz <epirat07@gmail.com> wrote: >> >>> I've accidentally used API not available on the checked version. >>> Additionally check for the SDK to be new enough to even have the >>> CVImageBufferCreateColorSpaceFromAttachments API to not fail >>> the build. >>> --- >>> libavutil/hwcontext_videotoolbox.c | 15 ++++++++++++++- >>> 1 file changed, 14 insertions(+), 1 deletion(-) >>> >>> diff --git a/libavutil/hwcontext_videotoolbox.c >>> b/libavutil/hwcontext_videotoolbox.c >>> index 953155ce32..ab7556936d 100644 >>> --- a/libavutil/hwcontext_videotoolbox.c >>> +++ b/libavutil/hwcontext_videotoolbox.c >>> @@ -588,13 +588,26 @@ static int vt_pixbuf_set_colorspace(void *log_ctx, >>> } else >>> CVBufferRemoveAttachment(pixbuf, kCVImageBufferGammaLevelKey); >>> >>> +#if (TARGET_OS_OSX && __MAC_OS_X_VERSION_MAX_ALLOWED >= 100800) || \ >>> + (TARGET_OS_IOS && __IPHONE_OS_VERSION_MAX_ALLOWED >= 100000) >>> if (__builtin_available(macOS 10.8, iOS 10, *)) { >>> - CFDictionaryRef attachments = CVBufferCopyAttachments(pixbuf, >>> kCVAttachmentMode_ShouldPropagate); >>> + CFDictionaryRef attachments = NULL; >>> + 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); >>> + } >>> +#endif >>> if (attachments) { >>> colorspace = >>> CVImageBufferCreateColorSpaceFromAttachments(attachments); >>> CFRelease(attachments); >>> } >>> } >>> +#endif >>> >>> if (colorspace) { >>> CVBufferSetAttachment(pixbuf, kCVImageBufferCGColorSpaceKey, >>> >>> base-commit: 9fb8d13d56f20728141fd7070d8a325720727d57 >>> -- >>> 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". >>> >> >> Should this have fixed the Apple M1 FATE node [1]? It seems to be still >> failing. >> >> -- Sean McGovern >> >> [1] https://fate.ffmpeg.org/history.cgi?slot=aarch64-osx-clang-1200.0.32.29 > > I sent another patch that does the availability check at configure time which should fix the fate CI: > https://ffmpeg.org//pipermail/ffmpeg-devel/2024-July/331496.html > Sorry, should be this one: https://ffmpeg.org//pipermail/ffmpeg-devel/2024-July/331499.html >> >>> >> _______________________________________________ >> ffmpeg-devel mailing list >> ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org> >> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel >> >> To unsubscribe, visit link above, or email >> ffmpeg-devel-request@ffmpeg.org <mailto:ffmpeg-devel-request@ffmpeg.org> with subject "unsubscribe". > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org> > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org <mailto: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".
next prev parent reply other threads:[~2024-07-21 22:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-09 14:46 Marvin Scholz 2024-07-16 12:11 ` Zhao Zhili 2024-07-21 22:04 ` Sean McGovern 2024-07-21 22:45 ` Gnattu OC via ffmpeg-devel 2024-07-21 22:48 ` Gnattu OC via ffmpeg-devel [this message] 2024-07-23 9:10 Marvin Scholz
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=9411EBF1-04ED-4B7C-8B67-EAA518B2BCBC@me.com \ --to=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