From: Kacper Michajlow <kasper93@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Request for --disable-deprecated configure option
Date: Thu, 3 Apr 2025 11:02:01 +0200
Message-ID: <CABPLAST8WawWJFMNubxBKu37sLowY5gFOsDOGb_fmH_6X9ktbg@mail.gmail.com> (raw)
Hello,
It would be nice to have configure time ability to disable all
`FF_API_*` for testing purposes.
As we know not all code can be marked to emit Wdeprecated.
Specifically #defines doesn't emit any warning and it's easy to miss
such depreciation before it's actually removed.
The breakage of course is not big, but the main issue is that the
current release version of a ffmpeg user won't be compatible with
ffmpeg after API bump, without any period for transition.
--disable-deprecated could be used for testing and ensuring that
(next) API bump goes smoothly. For both ffmpeg and its users.
We have seen breakage in mpv and libplacebo (only when built as
vf_libpalcebo) recently, which would be prevented if we had better
tools to monitor this. For example mpv builds with ffmpeg master on CI
with Werror and Wdeprecated enabled and yet it's not enough.
Thanks,
Kacper
_______________________________________________
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-04-03 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 9:02 Kacper Michajlow [this message]
2025-04-03 9:39 ` Martin Storsjö
2025-04-03 13:14 ` Kacper Michajlow
2025-04-04 18:53 ` Michael Niedermayer
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=CABPLAST8WawWJFMNubxBKu37sLowY5gFOsDOGb_fmH_6X9ktbg@mail.gmail.com \
--to=kasper93@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