From: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com> To: ffmpeg-devel@ffmpeg.org Cc: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com> Subject: [FFmpeg-devel] [PATCH] configure: Ignore nullability-completeness apple clang warnings Date: Thu, 5 Jun 2025 23:06:48 +0200 Message-ID: <DBAP193MB0956C69E9A767C1C1BD751858D6FA@DBAP193MB0956.EURP193.PROD.OUTLOOK.COM> (raw) Some of the versions of Apple Clang produces a ton of the warnings related to the missing nullablity specifiers on the existing codebase of ffmpeg which significantly slows down the compilation becuase of the produced output size (especially on CI as a part of external build systems because they usually analyze every single line of the produced stdout). This patch turns them off when compiling for darwing targets. And because apple's nullablity specifiers obviously are not used in the codebase having this warning turn of just makes sense. --- configure | 3 +++ 1 file changed, 3 insertions(+) diff --git a/configure b/configure index 89a766b403..54dd54360f 100755 --- a/configure +++ b/configure @@ -5860,6 +5860,9 @@ case $target_os in test ${clang_version%%.*} -eq 11 && add_cflags -fno-stack-check fi + # Apple Clang has by default enabled nullability warnings that + # create a ton of output noise and significantly slows + add_cflags -Wnullability-completeness # Xcode Clang doesn't default to -fno-common while upstream llvm.org # Clang (and GCC) do. This avoids linker warnings on Xcode 16.3 about # "reducing alignment of section __DATA,__common from 0x8000 to 0x4000 -- 2.49.0 _______________________________________________ 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 reply other threads:[~2025-06-05 21:07 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-05 21:06 Dmitriy Kovalenko [this message] 2025-06-05 21:14 ` Marvin Scholz 2025-06-05 21:28 ` Martin Storsjö
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=DBAP193MB0956C69E9A767C1C1BD751858D6FA@DBAP193MB0956.EURP193.PROD.OUTLOOK.COM \ --to=dmtr.kovalenko@outlook.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