Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Helmut K. C. Tessarek" <tessarek@evermeet.cx>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] videotoolbox increases min target to macOS 12
Date: Tue, 9 Jul 2024 01:47:16 -0400
Message-ID: <7d20c843-7be7-49b5-88ce-04c9587a0b13@evermeet.cx> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 2543 bytes --]

I'm very sorry to bother the dev list with this, but this is the 2nd 
time in less than a year that the min version of macOS was changed in 
videotoolbox.

2023-09-22: macOS 10.13
now: macOS 12

Will ffmpeg soon only compile on the current release of macOS (with 
videtoolbox support)? While I understand that too old OS versions are 
not necessarily the best idea, a lot of people still use older versions. 
Especially when it comes to Intel based static binaries.

I just want to ask what the devs think of this situation.
I'm not saying that this has to be fixed. (I just removed the 
videotoolbox support from my binaries.)

I'd asked in a forum, but there is none, nor is there another way to ask 
the devs a question. And it is a question to the devs:

Is it feasible that this code raises the minimum depolyment target that 
often, while the rest of ffmpeg just works perfectly fine with lower 
deployment targets?

Cheers,
   K. C.

Here  is the error message when compiling ffmpeg for reference:

libavutil/hwcontext_videotoolbox.c:592:39: error: 
'CVBufferCopyAttachments' is only available on macOS 12.0 or newer 
[-Werror,-Wunguarded-availability-new]
         CFDictionaryRef attachments = CVBufferCopyAttachments(pixbuf, 
kCVAttachmentMode_ShouldPropagate);
                                       ^~~~~~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreVideo.framework/Headers/CVBuffer.h:160:59: 
note: 'CVBufferCopyAttachments' has been marked as being introduced in 
macOS 12.0 here, but the deployment target is macOS 10.13.0
CV_EXPORT CFDictionaryRef CF_RETURNS_RETAINED CV_NULLABLE 
CVBufferCopyAttachments( CVBufferRef CV_NONNULL buffer, CVAttachmentMode 
attachmentMode ) API_AVAILABLE(macos(12.0), ios(15.0), tvos(15.0), 
watchos(8.0));
                                                           ^
libavutil/hwcontext_videotoolbox.c:592:39: note: enclose 
'CVBufferCopyAttachments' in a __builtin_available check to silence this 
warning
         CFDictionaryRef attachments = CVBufferCopyAttachments(pixbuf, 
kCVAttachmentMode_ShouldPropagate);
                                       ^~~~~~~~~~~~~~~~~~~~~~~
1 error generated.


-- 
regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
    Thou shalt not follow the NULL pointer for chaos and madness
    await thee at its end.
*/

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2024-07-09  5:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09  5:47 Helmut K. C. Tessarek [this message]
2024-07-09  6:16 ` Gnattu OC via ffmpeg-devel
2024-07-09  8:41   ` epirat07
2024-07-09 19:44   ` Helmut K. C. Tessarek
2024-07-09 20:04     ` epirat07
2024-07-09 20:15       ` Helmut K. C. Tessarek

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=7d20c843-7be7-49b5-88ce-04c9587a0b13@evermeet.cx \
    --to=tessarek@evermeet.cx \
    --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