From: epirat07@gmail.com To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] videotoolbox increases min target to macOS 12 Date: Tue, 09 Jul 2024 22:04:32 +0200 Message-ID: <6AC8897B-224C-4DC6-BEA9-92920BD65726@gmail.com> (raw) In-Reply-To: <40e630f5-6d03-4fe3-a77c-37298db3de1a@evermeet.cx> On 9 Jul 2024, at 21:44, Helmut K. C. Tessarek wrote: > Thanks for the reply. > > On 2024-07-09 02:16, Gnattu OC via ffmpeg-devel wrote: >> Well the code introduced is to fix certain HDR related bugs and it does not "works perfectly” before, it was just broken. > > I was rather talking about being able to compile it. I can compile ffmpeg without videotoolbox for older deployment targets without any issues. > > It is great to fix videotoolbox, but is it required to use functions/methods that are only available in newer OS? All the other libraries and ffmpeg itself can fix bugs without using functions that are not available on "older" systems. > > If you say it isn't possible, then all is good. I am not asking anyone to make the impossible possible. > > I am just trying to understaand why videotoolbox is raising the minimum deploymewnt target all the time, while this is not necessary for anything else. Don't get me wrong, I am compiling ffmpeg with around 50 3rd party libraries. None of them requires me to raise the deployment target. Videotoolbox should not have raised the deployment target and I did not notice any change recently that would have done it other than mine accidentally. If you encounter other issues with it, once my fix is merged, do not hesitate to report them here. > >> so that it should at least compile on older OS targets. >> But the end result is that the colorspace is as wrong as before, an older version cannot receive the fix to set the correct colorspace. >> >> For this use case I could see that using the (now deprecated) `CVBufferGetAttachments` instead on older OS, but I cannot really test that because I don’t have device running that old version. > > FYI. I am also compiling on the most recent macOS release but I set the deployment target via env var: > > export MACOSX_DEPLOYMENT_TARGET=10.13 > > > -- > 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. > */ > _______________________________________________ > 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".
next prev parent reply other threads:[~2024-07-09 20:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-09 5:47 Helmut K. C. Tessarek 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 [this message] 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=6AC8897B-224C-4DC6-BEA9-92920BD65726@gmail.com \ --to=epirat07@gmail.com \ --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