From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com>
Subject: Re: [FFmpeg-devel] [PATCH] configure: Ignore nullability-completeness apple clang warnings
Date: Fri, 6 Jun 2025 00:28:19 +0300 (EEST)
Message-ID: <b4f6a655-b4c2-d099-c61-2ec3b845cd42@martin.st> (raw)
In-Reply-To: <DBAP193MB0956C69E9A767C1C1BD751858D6FA@DBAP193MB0956.EURP193.PROD.OUTLOOK.COM>
On Thu, 5 Jun 2025, Dmitriy Kovalenko wrote:
> 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(+)
I don't remember ever seeing such a warning; is this something that only
appears in some specific build configuration? Can you elaborate on what
build configuration that is, and give an example of such a warning? (Such
data would be quite relevant to include in the commit message.)
// Martin
_______________________________________________
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".
prev parent reply other threads:[~2025-06-05 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 21:06 Dmitriy Kovalenko
2025-06-05 21:14 ` Marvin Scholz
2025-06-05 21:28 ` Martin Storsjö [this message]
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=b4f6a655-b4c2-d099-c61-2ec3b845cd42@martin.st \
--to=martin@martin.st \
--cc=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