From: Soft Works <softworkz@hotmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] QSV: Introduce min Compile-SDK Version and check for Runtime-Versions instead Date: Tue, 3 May 2022 22:13:52 +0000 Message-ID: <DM8P223MB0365EBF8BFC2BE132EE693BBBAC09@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <DM8P223MB0365C08FC310774E59FB819CBA529@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Soft > Works > Sent: Wednesday, January 12, 2022 4:37 AM > To: FFmpeg development discussions and patches <ffmpeg- > devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [RFC] QSV: Introduce min Compile-SDK > Version and check for Runtime-Versions instead [..] > > > Question > > > > > > Having both - run-time and compile-time checks all over the code > is adding > > > a lot of complexity and makes it difficult to maintain and work > with. > > > > > > Hence, I'm wondering whether we couldn't/shouldn't introduce a > minimum > > > MSDK compile-time version, for example 1.22, or even later? > > > > > > This would allow simplification of the QSV code in many places > where run- > > time > > > version checks are actually needed instead. > > > > > > Over time, there have been better and worse MSDK versions, and > there > > > should still be enough room for choosing, but I don't think > there's any > > > reason why somebody would still want to compile against some > really old > > > (e.g. < 1.22) MSDK version. > > > > > > Please share your thoughts on this subject.. > > > > I agree we may add a requirement for the minimal compiling version > in > > configure, > > version 1.28 was released 3 years ago, how about using this version > as the > > minimal compiling version ? > > I'm fine with 1.28! Are there any objections towards setting 1.28 as a minimum requirement for the MSDK (QSV) compile-time version? sw _______________________________________________ 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:[~2022-05-03 22:14 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-03 21:53 Soft Works 2022-01-12 2:53 ` Xiang, Haihao 2022-01-12 3:37 ` Soft Works 2022-05-03 22:13 ` Soft Works [this message] 2022-05-22 12:24 ` Xiang, Haihao 2022-05-22 16:28 ` Soft Works
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=DM8P223MB0365EBF8BFC2BE132EE693BBBAC09@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz@hotmail.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