Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Matthieu Bouron <matthieu.bouron@gmail.com>
To: Zhao Zhili <quinkblack@foxmail.com>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Bump minimum required version of Android to 5.0
Date: Fri, 12 Apr 2024 15:47:36 +0200
Message-ID: <CAOmVQXEbonSpRBrukR1br+F99TUr5F5Rdr9SPrM2U0q_bTqqVg@mail.gmail.com> (raw)
In-Reply-To: <tencent_69AEBE255F7301284113FAF36C35C5C90C05@qq.com>

On Thu, Apr 11, 2024 at 2:17 PM Zhao Zhili <quinkblack@foxmail.com> wrote:
>
> We don’t have a minimum required version of Android in FFmpeg.
> libavdevice/android_camera requires Android 7, Java MediaCodec
> requires Android 4.1, and NDK MediaCodec requires Android 5.0.
>
> Without an explicit version, it’s unclear for development and test.
>
> Android 5.0 is released in 2014, is it OK to bump the minimum required
> version to Android 5.0, or any other version you prefer?

I'm OK with bumping the requirements to 5.0, especially if that helps
with maintenance (I dont have nor work with devices < 8.1).
_______________________________________________
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".

      parent reply	other threads:[~2024-04-12 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 12:16 Zhao Zhili
2024-04-11 13:17 ` Tomas Härdin
2024-04-11 13:57   ` Zhao Zhili
2024-04-11 15:00     ` Zhao Zhili
2024-04-12 10:50     ` Tomas Härdin
2024-04-12 10:51       ` Nicolas George
2024-04-12 11:23       ` Zhao Zhili
2024-04-12 11:39         ` Tomas Härdin
2024-04-12 13:47 ` Matthieu Bouron [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=CAOmVQXEbonSpRBrukR1br+F99TUr5F5Rdr9SPrM2U0q_bTqqVg@mail.gmail.com \
    --to=matthieu.bouron@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=quinkblack@foxmail.com \
    /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