From: Marton Balint <cus@passwd.hu> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v6] libx264: Set min build version to 158 Date: Thu, 9 Jun 2022 20:44:26 +0200 (CEST) Message-ID: <18b8e22c-1d10-879b-bee2-1b128f176f3d@passwd.hu> (raw) In-Reply-To: <DM8P223MB036557045B405622CE545300BAA49@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> On Wed, 8 Jun 2022, Soft Works wrote: >>> - { require libx264 "stdint.h x264.h" >> x264_encoder_encode "-lx264 $pthreads_extralibs $libm_extralibs" && >>> - warn "using libx264 without pkg-config"; >> } } && >> >> x264 without pkg-config feature got removed. If this is intentonal, >> then maybe you should mention this in the commit message? > > I cannot honestly say that I would be sure about this part. Matt had > this removed in his original patch and objections were made about the version > requirement, but none about the removal of the "non-pkg-config" condition. > > Would there be any reasons to keep it? Probably not. Removing it is fine by me, but the removal should be stated in the commit message. > >> >>> - require_cpp_condition libx264 x264.h >> "X264_BUILD >= 118" && >>> - check_cpp_condition libx262 x264.h >> "X264_MPEG2" >> >> Why is the x262 check got silently removed? This does not seem to belong >> to this commit.` > > Matt had removed it and there was a comment about it saying that it > would by dysfunctional for a long time already. > > By a funny coincidence, Gyan has submitted a patch for complete removal > of this: > > https://patchwork.ffmpeg.org/project/ffmpeg/patch/20220527082922.994-1-ffmpeg@gyani.pro/ > > Whether it belongs into this patch or not could be seen from two sides: > > On one side, you could say that THIS patch is about updating and adapting > the x264 conditions to the state of time, but you could also say that > it must rather be in Gyan's patch (which it is anyway). > > Just let me know when you think I should change it. I'd rather keep the X262 cpp check for now. Thanks, Marton _______________________________________________ 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-06-09 18:44 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-20 23:11 [FFmpeg-devel] [PATCH] " Matt Oliver 2022-05-25 9:31 ` [FFmpeg-devel] [PATCH v2] " softworkz 2022-05-25 9:34 ` [FFmpeg-devel] [PATCH v3] " Matt Oliver 2022-05-25 9:38 ` Andreas Rheinhardt 2022-05-25 9:53 ` Soft Works 2022-05-25 11:05 ` [FFmpeg-devel] [PATCH v4] " Matt Oliver 2022-05-25 15:15 ` Michael Niedermayer 2022-05-25 22:53 ` Andreas Rheinhardt 2022-05-26 7:26 ` Soft Works 2022-05-26 7:28 ` [FFmpeg-devel] [PATCH v5] " Matt Oliver 2022-05-26 10:50 ` Michael Niedermayer 2022-05-26 11:20 ` Soft Works 2022-05-26 12:29 ` [FFmpeg-devel] [PATCH v6] " Matt Oliver 2022-06-08 20:22 ` Marton Balint 2022-06-08 22:50 ` Soft Works 2022-06-09 18:44 ` Marton Balint [this message] 2022-06-09 19:19 ` Soft Works 2022-06-09 23:27 ` [FFmpeg-devel] [PATCH v7] " Matt Oliver 2022-06-11 12:20 ` Marton Balint
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=18b8e22c-1d10-879b-bee2-1b128f176f3d@passwd.hu \ --to=cus@passwd.hu \ --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