Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Request for --disable-deprecated configure option
Date: Wed, 16 Apr 2025 11:22:25 +0200
Message-ID: <GV1P250MB07379F1F42E1978F390278B38FBD2@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CABPLASTNnXR6q4jXdBHgYyuvmhKOBf+RH1tZT5uFM2TYwVJOjw@mail.gmail.com>

Kacper Michajlow:
> On Thu, 3 Apr 2025 at 11:39, Martin Storsjö <martin@martin.st> wrote:
>>
>> On Thu, 3 Apr 2025, Kacper Michajlow wrote:
>>
>>> 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.
>>
>> So essentially to configure a build to use the next major API version
>> before doing the actual bump?
>>
>> I've actually mentioned that we should do that (and that we should have a
>> FATE instance that continuously tests this, so that we know beforehand
>> that our planned next form of the APIs actually works), and I did try
>> making a PoC of it at some point, but unfortunately, I think I concluded
>> that it was a bit more messy than I had wanted, so I didn't continue
>> on it.
>>
>> See https://github.com/mstorsjo/ffmpeg/commit/next-abi for my PoC.
> 
> Yes, making the API version configurable would work. But as you
> noticed it gets a bit messy with all the conditionals.
> 
> I didn't think about it long, I wanted to discuss this first, but was
> thinking about a simple DISABLE_DEPRECATED which would be defined by
> configure and all `FF_API_*` would depend on that.
> 
> #define DISABLE_DEPRECATED 0
> #define FOO(c) (c) && !DISABLE_DEPRECATED
> 
> #define LIBAVUTIL_VERSION_MAJOR  60
> #define FF_API_MOD_UINTP2               FOO(LIBAVUTIL_VERSION_MAJOR < 61)
> #define FF_API_RISCV_FD_ZBA             FOO(LIBAVUTIL_VERSION_MAJOR < 61)
> ...
> 
> Also if someone wants to go fancy, the deprecated feature could be
> disabled individually, but I don't really see much use for that,
> except niche cases where you might still use deprecated things, but
> not all... but then just don't disable them.
> 

This was already possible until db932241ee16868475fe9ab4c958fcffd1829ecf.

- Andreas

_______________________________________________
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".

  reply	other threads:[~2025-04-16  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03  9:02 Kacper Michajlow
2025-04-03  9:39 ` Martin Storsjö
2025-04-03 13:14   ` Kacper Michajlow
2025-04-16  9:22     ` Andreas Rheinhardt [this message]
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=GV1P250MB07379F1F42E1978F390278B38FBD2@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@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